Amplitude Reviews

My main use case for Amplitude, which relates to my main job role, is analyzing data. That involves creating dashboards, connecting click-level data sources to Amplitude, and then consuming reports and creating analyses for stakeholder-facing reports, which would be consumed by company leadership, the analytics team, product managers, and others.

A specific example of a dashboard we built with Amplitude is a click-level report that I created recently when I was with TurboTax. We made it to study the clicks on every page. Essentially, what we visualized was a Sankey chart of how people are moving through pages. Since we changed the entire product stack, it was important for us to verify where the drop-offs were. Eventually, we moved the idea of a Sankey chart to a drop-off chart where we studied the bounce rate for each page, and we had a bar graph showing the number of people on one page and throughout their journey, where people dropped off. That drop-off report was a big project, and I think that helped the team recognize what the bottlenecks were and what the problem areas were in the product.

The reaction from our team and stakeholders to the findings from the drop-off report was that it had already been discussed with the major stakeholder product managers, so it was a requirement we mutually discussed and came to. Since Amplitude has incredibly easy functionality for accessing the past year of data, it became a tool that even the PMs could play around with, allowing us to leave them to self-serve. That acted as a big positive for us in the analytics team because the more our stakeholders use self-serve reports, the less work it is on our shoulders. That was especially great from the PMs because we could reconcile our Amplitude data with other data sources, such as the Databricks data lake, in a short span of time. Changes were made right from UX level changes on the pages to broader decisions on whether we need to clamp down on the entire tax filing experience.

I think the best feature Amplitude offers is its data visualization capabilities. As a subject matter expert who has been working on it for seven to eight years, I consider Amplitude to be the closest any application software gets, and it just makes life easy for developers as well as people with less developer experience. Even for product managers who do not have data visualization development experience, they can navigate very easily, and so is the case for any other stakeholder. That is the best feature.

What stands out about Amplitude's data visualization compared to other tools I have used is the easy integration with clickstream data. It was seamless for that data to be loaded into Amplitude, with a good volume that easily loads onto Amplitude without having to create intermediate tables, which was the case with Tableau. Everything on top of that is easy usage and functionality because we used to do it on Chrome without needing a desktop server to create data visualizations. This entire package is really robust.

Collaboration was a significant part. What improves collaboration is the self-serve functionality, which was a big deal for PMs to have access to just that data and also the base layer of how that data is structured, which connects to clicks that every report refers to. Business stakeholders can pull different cuts and slices without relying on analytics, which is usually quite loaded with tasks. That was the best thing, as collaboration allowed business stakeholders to attempt to go through the reports and create their own reports, which was beneficial.

I notice faster decision-making for sure, as business stakeholders could themselves get their own reports.

I think areas for Amplitude's improvement include data retention. The maximum data I have worked with, the clickstream data on Amplitude, is two years, whereas we rely on Tableau for historical data of at least two years. I am not sure whether it was my organization paying for lower retention or not, but having historical data would take away the reliance on Tableau. Secondly, reconciling clickstream data with Databricks or other AWS systems could help analysts spend less time verifying the accuracy of both sources, which would be really helpful. Lastly, a more focused approach on error logs is necessary. I have found that, at least with Intuit, we used Splunk more for error logs than Amplitude. Although Amplitude had the capability, developers seemed to prefer Splunk, so if that could be improved, it would be good.

I have been working in my current field for about seven and a half to eight years. I have been using Amplitude for five to six years.

I did not notice any delays or issues with Amplitude's performance and speed when handling large datasets. One of the strongest points of Amplitude is its functionality for making visualizations, and speed while handling large datasets is really good. There has never been an issue where it hung or took a lot of time, and that is where Amplitude has the edge in handling large datasets with clickstream data.

I did not work a lot on the integration side of Amplitude, so the data engineers worked on integrating clickstream data, and my problems revolved around reconciling this clickstream data on Amplitude with the Databricks data. It made for a tiresome experience because essentially they should be the same, but they were not due to different reasons on the data engineering side. I did not really integrate Amplitude with other tools per se.

Amplitude's security and access controls are completely in-house, and organization-wide accesses were provided right when we onboarded onto our analytics roles, so that was never a problem. Access controls were also straightforward, and we did not have any issues there.

Managing data privacy and compliance requirements with Amplitude was easy. As far as I remember, the challenges with data privacy and compliance requirements did not raise any issues flagged at any point by the data engineers or the Amplitude admin. We could seamlessly use the data from an analyst perspective.

We did not use the mobile app, so I cannot comment more about it.

I would describe Amplitude's reporting and analytics capabilities compared to other tools I have used as really good. I would say it is on par or just shy of Tableau, which, for me, is the best tool in the market, so it is right up there.

I went through the training resources and documentation when I joined in 2019, and as far as I remember, they were useful. The training may have included videos or articles, but I do not fully recall. The prompts on the website and the nudges were really helpful.

My advice for others looking into using Amplitude is that if it is clickstream data, Amplitude is likely the best option. Having accessible data which can be easily customized and manipulated by even business stakeholders with less technical knowledge is one of the best things. I rate Amplitude an eight because the changes I mentioned, including longer data retention, easier integration with AWS data sources, and a better focus on error logs, would make it a ten for me.

My main use case for Amplitude is for data extractions from multiple sources, and I have used Amplitude in my recent project at Citi. Data extraction and behavioral analytics represent my primary use cases.

A specific example of how I used Amplitude in my HCT project involved using Amplitude exports to derive behavioral features like session frequencies and feature adoption, which boosted customer retention predictions. I used Amplitude to extract user engagement data and enrich predictive analytics with behavioral insights.

Besides data extraction and behavioral analytics, my other use case is enabling product and customer analytics. I generated clickstream, CRMs, and transactional data sets into Amplitude to measure user journeys, funnel drop-offs, and retention trends, along with marketing attributes.

My company provided me with access to Amplitude through their purchase.

Amplitude offers excellent features including behavior level analytics, as well as funnel analysis and cohort analysis, which are very easy to access and visualize. Cohorting is something that other BI tools cannot do natively, and that is the main feature I value about Amplitude.

The cohorting feature specifically helps in my day-to-day work by allowing me to understand where the drop-off points are. Funnel analysis shows me what the customer journey is and what the retention rate looks like. When my task was to create a unified event analytics pipeline, I used Amplitude for real customer behavior insights, which made it easier for me to grasp the basic idea about the customers and the data. The dashboard shows real-time funnel and retention curves and marketing insights such as MTA, which improves campaign targeting and raises personalization accuracy.

Amplitude has positively impacted my organization by providing better behavior level analytics individually, which other BI tools cannot do natively. It has helped the product teams or my team to make faster decisions without relying on engineering for every question.

Since I can see everything in Amplitude dashboards, it helped the product teams to make quicker decisions to understand the drop-off points. For example, if someone added something to the cart and did not purchase it, I can understand the retention of that customer and that product, making it much easier to make decisions without relying on other engineering teams for data and approvals. For ad-hoc analysis, it is much better.

I am very comfortable using Amplitude and do not have any other feedback other than it being a very useful tool that I appreciate using in my projects. It is good as of now, and I have no additional thoughts about needed improvements.

I give it a nine because it is close to a perfect ten for me, but it is only useful in one layer of the project, not the other, which the tool is supposed to do. In general, it is very impactful in my project.

I have been using Amplitude for three to four years.

Amplitude is stable.

Amplitude is quite scalable. It is a good tool to use and a very helpful addition to my projects.

I have not reached out to customer support because I have not had any issues; everything has been manageable.

I have always been using Amplitude.

Amplitude has provided a return on investment. It has helped us improve campaign targeting and raised personalization accuracy by almost twenty-five percent, and it has saved us a lot of time since I can see the analysis as quickly as possible in the dashboard, resulting in significant time and money saved.

I am not entirely certain about the pricing, as my company has given me access. Amplitude's pricing is good and not overpriced; it is fair for the amount of data we are extracting and the analysis we perform.

My company has provided me with this tool only, so I have been working with Amplitude from the early stages of my career.

The advice I would give to others looking into using Amplitude is to start using this tool because other BI tools cannot do everything, and the dashboards with live dashboarding are superior. This is the better tool available in the market, so I would advise opting for Amplitude.

I really appreciate using Amplitude; it is a nice addition to my projects, and it helps me make faster decisions. I give this product a rating of nine out of ten.

Amplitude is our main product insights system, and it allows us to view the activity on our website and quantify certain KPIs about how users interact with the site.

We measure things such as monthly active users by seeing how many users have performed a tracked action within the last month. Monthly active users, or MAUs, is tracked in that way. We also have time series charts that establish patterns of user behavior as they make their way across our site, and we use those to analyze how they are using our site and how they are interacting with our products.

When we offer special sales on our products to our users, it is often crucially important to know how they are engaging with the sale and if they purchase that sale product or any additional products during that time. We have often used the funnel analyses of interactions during this time to enhance our sale offerings in the future and to make decisions about which products are giving the most return for our users.

The best features Amplitude offers are their funnel analyses, which allows you to specify any number of events in series and look at how many users performed those events in the certain configuration over time. Their time series graphing is also quite impressive, and time series analysis is normally something that is quite tedious to do manually. Amplitude does an excellent job at taking care of that, linking tracked events.

Amplitude has provided almost instant value to our dev team when they are deploying new trackable events and seeing how those events line up before they go out to production. The positive impact on our organization is really felt mostly by our product team because the product insights that we get from Amplitude are used to enhance and redesign our products as well as influence new offerings.

We have been able to assess the friction points on our website that users often encounter that lead to negative outcomes, and we have been able to either reduce or completely re-engineer those friction points to ease the friction on the user.

Amplitude can be improved by allowing more than a two-year look back window for most analyses. Usually, all they offer is that two-year look back window, and longer form time series analysis seems nearly impossible to do on this platform. Extending the time window with which you are able to look back can definitely be improved.

We attempted to use their screen recording and session recording capabilities as a replacement for a previous vendor, and we found that the functionality they offered did not stack up to the previous vendor. There is a lot of room for improvement on session recording.

I have been using Amplitude for four years.

Amplitude is very stable.

Amplitude is very scalable, considering that we do not have to do any manual work ourselves. It is all done on the back end.

The customer support is exceptional. They also make themselves available in a Slack group. You can pursue answers whichever way you would prefer through the normal support routes or you can source it from the community that they offer on Slack.

Positive

We attempted to use their screen recording and session recording capabilities as a replacement for a previous vendor, and we found that the functionality they offered did not stack up to the previous vendor.

I was not part of the setup cost scenario because it was already established before I joined the company. However, I am familiar with the re-upping of our contract over time and the pricing associated with that. Pricing is often egregiously high, and the company has changed billing models on us once already. It often needs to be negotiated with sales reps, which makes the process a bit long, and for a public benefit corporation, we do not often see any special accommodations budget-wise, which is a little disappointing.

I chose a rating of nine out of ten because Amplitude has virtually every functionality that we need except for the aforementioned lack of long form time series analysis, and their pricing is often a bit egregiously high, needing to be negotiated down on an enterprise level.

There does not need to be a third-party cloud provider because Amplitude uses their own resources.

We do not have any established metrics simply because we have been using Amplitude for too long in order to have some formal metric. We are completely tied to Amplitude for our product insights at this point. It would simply be too great an expense for us to spin up another system that would provide such a service in such a robust fashion in a way that would be cost-effective.

I am not familiar with the initial implementation as Amplitude was already in use when I joined the company.

Be aware that Amplitude is very powerful, but also very expensive accordingly.

We do not have a business relationship with this vendor other than being a customer. My overall rating of this product is nine out of ten.

Private Cloud

Other

My main use case for Amplitude is to set up analytics dashboards for monitoring and understanding user behavior and spotting issues and bugs when we release software.

A quick specific example of how I used Amplitude for monitoring user behavior or spotting issues is when we want to release feature A and have the user stories that incorporate events, which pop up on the Amplitude dashboard. From that perspective, I could see the adoption, see if expected users have expected features, and if we see some spikes or drops, then we understand something went wrong. From the technical perspective, we monitor our API endpoints, seeing both successful and error responses, and we can set up alerts if something goes wrong to track down details and figure out what went wrong.

My main use case is very useful for exploratory testing, understanding user behavior, and feeding back into testing techniques and the software development life cycle. Things that we could miss during planning, things we are not aware of, we feed back, implement them, and see how it goes moving forward.

The best features Amplitude offers are useful dashboards that I set up easily from a user journey perspective, as well as a single point to understand one event. I appreciate how it integrates with other systems and all the insights you can drill into, giving you a lot of information for one of the users. You can see not only how they use the product but also which platforms they are on and which areas they are using. All those details help a lot to understand users from a holistic point of view.

The dashboard setup is easy to discover for a newbie; although sometimes over time, it gets complicated. Last year's release or UI redesign got a bit more confusing on how to make one or the other dashboard. In general, you have user paths, so there are two or three main paths to go through, which was good to understand. For integrations, we integrate with tools such as Slack and other monitoring tools as well as our SDK for our apps, allowing us to send events from our applications to Amplitude.

Amplitude offers a lot of features. I'm not an analyst to use all of them; I'm a quality software engineer, so I'm sure I didn't use all of them. For me, it was enough. From my perspective, the simpler, the better, so I can quickly leverage the features. Analysts might do more complicated things, and it was also useful; I remember you can use different queries if you need to find information very quickly, which was useful.

Amplitude has impacted my organization positively in a huge way. Everyone uses Amplitude if they want to have some learnings before implementing new features. It is used during software implementation to gain insights into understanding user behavior, which is massive for debugging issues. You can find the user, see where they're coming from, and what went wrong. So it is absolutely the same as on monitoring. Everyone in the business adopts data-driven development, and Amplitude is one way to understand that data and user behavior, which backs up everyone's work. This leads to a massive positive change, positive attitudes, lots of learning, and encouragement to use Amplitude in daily work for everyone in the company, not just analysts.

A specific outcome and metric that show Amplitude's impact is when I have a dashboard monitoring users logging into an iOS app for a particular release. I want to monitor, hypothetically, and it is useful if the chart is going smooth and the adoption of the new version is going up, which means things are going well for users. The version is out there, downloaded, and people can log into the app. If we can see previous app behavior, it indicates that if people downloaded the new app version, the previous one is going down. If things aren't going well, such as people can't log in or aren't adopting the version much, we drill down to understand what happened. Mostly, we monitor new feature adoption or existing core parts of the business functionality on a daily basis, having Slack channels notify us if anything goes beyond the threshold. This helps us spot lots of bugs, such as personalization that we thought some segments of people would get, but they were not getting it, allowing us to fix our personalization because we had insights and understood what segment of people did not get what we expected.

I would improve Amplitude by making it as clear and easy to use as possible. The feature discoverability could be simpler. I think AI could help in building queries and dashboards based on data, assisting people in learning about the tool, whether they're new or not analysts, helping them discover what they can do more. Additionally, insights on monitoring, identifying potential issues, and suggesting areas to look at to better understand trends on that dashboard would be appreciated. I realize that every context matters, but making it less confusing would be my main approach.

I choose nine because, lately, when I was using it, the more people wanted to improve, the more complex things got—not in a good way, but confusing. If I were using it right now without prior knowledge, I wouldn't know where to start. It matters when an expert is in the room and when new users want to do some things. I wouldn't know where to start; that would be my main concern—how you help people who are not data analysts or who want to discover their data to get into Amplitude.

I have been using Amplitude in my previous job for about two or three years.

My advice to others looking into using Amplitude is to understand what you want to get, what your main goal is because Amplitude can offer a lot.

I have a very positive experience with Amplitude. I enjoyed it a lot in my work. I don't use it now, but I hope to have a chance to use it in the future. I would rate my overall experience with Amplitude a nine out of ten.

Amazon Web Services (AWS)

My main use case for Amplitude is user behavior analysis within products.

For user behavior analysis within my products using Amplitude, I can see how users are interacting with the product, specifically how they're using it, splitting them up into different cohorts to find out which users are converting to paid subscribers and which users are not, and identifying the behaviors of those that are converting to paid subscribers to understand the behavior to drive in the overall user base to increase conversion rate.

In addition to user behavior analysis, my main use case with Amplitude includes finding bugs in a system and conducting cohort analysis, using it to AB test feature flags and various features in a product to identify how the subscription rate, or conversion rate, has increased based on different variants, along with sending out surveys to users and analyzing that data, creating audiences of data for advertising purposes and reselling it as well. I have used Amplitude at many different companies as a data or director leader over the last seven years across 10 different products.

The best features of Amplitude are that it's a database with a visualization layer on top of it; at a foundation level, that's what it is. You can do anything with that, and there's a whole toolkit available. One feature worth noting is abnormality detection, which can detect abnormalities in metrics over time and can trigger alerts or emails to notify the necessary parties when an issue arises, such as a spike in users trying to log in but failing, indicating potential failures in the authentication part of the product.

The abnormality detection feature helps my team respond to issues or improve our product by alerting us to critical failures in the application that might otherwise go undetected; while ARM tools may catch more technical failures, some failures are only detectable through user behavior analysis. Amplitude impacts my organization positively as it serves as a central point that allows everyone within the organization to speak the same language of data.

Regarding how Amplitude can be improved, I think that dashboards and charts are ephemeral; people often create dashboards but rarely revisit them, so while a handful of dashboards might survive, the real value lies in the insight derived from them. I believe Amplitude should bypass the whole dashboard approach and proactively surface insights instead.

I have been using Amplitude for seven years.

Amplitude is stable.

Amplitude's scalability is fine; I have millions of active users, tens of millions, with high throughput, and it performs great.

Amplitude customer support is responsive.

Negative

I have used other solutions including Power BI, Heap, Mixpanel, Grafana, Looker, and DataDog.

I have seen a return on investment with Amplitude, saving about 120 man hours per month for a specific report that needs to be created and generating revenue by creating a product where Amplitude is the foundation.

My experience with pricing, setup cost, and licensing involved lots of negotiation, but the setup cost was negligible.

Before choosing Amplitude, I evaluated all the options I just mentioned.

The advice I would give to others considering Amplitude depends on the person; if they know what they're doing, I would suggest doing event-based pricing because it provides more control versus user-based pricing.

I could go down any path, and I understand you may have some script that you want to follow, but if there's something more specific that you're after, then I would have some insight. I have used Amplitude in nearly every way possible, even in ways that they don't advertise because Amplitude doesn't know you can use it that way. I have worked closely with the founders to get features off the ground for Amplitude, and I have alpha tested every feature, or beta tested, whatever you call it, so I know it inside and out. My overall rating for Amplitude is eight out of ten.

Private Cloud

Amazon Web Services (AWS)

My main use case for Amplitude is serving as the analytics lead, creating dashboards on Amplitude, exporting data from Amplitude to Snowflake for different analytics questions, measuring the performance of our game, and supporting user acquisition. There are multiple sources and destinations, and I need to connect everything with Amplitude to obtain all sorts of analytical solutions from our game.

A quick, specific example of how I use Amplitude to solve an analytics question occurs when the product team CEO asks about the performance of one of our features, such as our daily task feature in the game. I quickly create a simple chart based on the percentage of daily active users engaged with the daily task feature or even a more complicated chart showing the percentage of eligible daily active users or how many daily active users are completing all three challenges. In this way, I can answer simple and quick analytical questions without coding.

I find the process of creating these charts and reports in Amplitude to be easy to use, and I can create a variety of charts and reports. However, for some use cases, I cannot create the exact charts according to the requirement, so I use SQL through Amplitude data because we migrated and downloaded Amplitude data to Snowflake, where I use SQL. For most use cases, if I can find simple answers from Amplitude, I don't require SQL or any other resources, so it is quite useful and fast.

Amplitude is very useful for getting something really quick, as product managers and CEOs want fast answers to their questions and fast analysis. Amplitude is really useful for quick and fast answers, and we have created multiple dashboards for all our products, allowing us to create numerous charts. I think it is really useful.

The best features Amplitude offers include everything, and the variety of charts they can create, as well as Amplitude data where I can combine all my sources and destinations, are key features. Even if we don't use them much due to our plan or tier that Amplitude provides, I still feel that is useful.

The most valuable chart types and integrations for my analysis include main segmentation, which is really useful for most of my work since we want to get the game performance based on the percentage of daily active users doing this or that. The second chart type would be the funnel for checking how any feature in our game works. There is always use for retention charts to understand how retention flow works for our game, as well as user sessions to check user session engagement. For complex calculations, I also create some data tables. These are the charts we use. For destinations, we use Snowflake as a destination when we download all the data from Amplitude to Snowflake, where we ingest event and user data from Unity, allowing us to obtain media sources and campaign information easily from Unity to Amplitude.

Amplitude has positively impacted our organization by helping with all our product performance and has been an integral part of our product team on our product journey. We are collecting data based on Amplitude and using Amplitude data format to send to Snowflake, and for quick calculations, we also use Amplitude, so all data-related tasks are dependent on Amplitude.

Specific outcomes that show how Amplitude has helped my team or business include time savings for us in understanding the overall performance of the game. Based on Amplitude charts and outcomes, our product team takes decisions, so it has improved decision-making. We also analyze engagement of different features in our game, and based on Amplitude charts, we have made product decisions that have helped increase engagement.

Amplitude is almost perfect, but there are some charts I cannot create due to the large data structure. For those, I need to use Excel or SQL sometimes. It would be great if we could have various types of graphs available, but overall, it is a perfect product.

Regarding needed improvements, speed is fine and integration is fine. Support could be improved. Sometimes I need to create a ticket and communicate with one of their advisors via email. Providing live chat support would be more helpful.

I have been using Amplitude for more than three years.

Amplitude's scalability has handled our growing data and user needs well until now, and I am hopeful it will continue to do so in the future.

I would say customer support is adequate. It is neither too good nor too bad. I think there could be live chat support for different types of charges or solutions that would be more helpful, but the current support is fine. It is not too bad and certainly not perfect.

Neutral

The experiment feature and more advanced features, such as some AI tools available in the market with Amplitude, are things I am interested in learning.

My advice for others looking into using Amplitude is to appreciate its speed of execution. It can generate quick charts and solutions for all your product needs. Its integrations work seamlessly with multiple software, including Unity and various others that we have, and it is relatively affordable compared to other products in the market, so it is perfect.

Amplitude is a perfect product that will always fulfill all the data-related needs that your company has, and I would suggest anyone to go for it. I rate the overall solution as a 9 out of 10.

My main use case for Amplitude is to use it as a dashboard to view my business metrics and measure results of AB test experiments.

A specific example of a metric I have tracked recently with Amplitude is the number of new paid users on my site, as I look at a chart in Amplitude.

The best feature Amplitude offers is the ability to track metrics without having to specify them ahead of time.

This flexibility helps me in my day-to-day work because it saves time.

Amplitude has positively impacted my organization as it allows us to make decisions based on data and iterate faster.

It has helped me iterate faster by using Amplitude to measure the results of AB tests, which enables us to de-risk features and ship value to customers.

Amplitude could be improved by being cheaper.

I have been using Amplitude for probably six or seven years.

Amplitude is stable.

Amplitude's scalability is fine.

I haven't had much experience with customer support.

Neutral

I have used a number of tools in the space and the last one was Google Analytics.

I switched from Google Analytics to Amplitude because of the ability to see events without programming them ahead of time.

I haven't seen a return on investment and cannot share any relevant metrics, such as time saved, money saved, or fewer employees needed.

My experience with pricing, setup cost, and licensing is that we are using a free version and would upgrade to a paid version if it were cheaper.

I didn't evaluate other options before choosing Amplitude.

My advice to others looking into using Amplitude is to try it. My company does not have a business relationship with this vendor other than being a customer. I would rate this review an 8.

Public Cloud

We used it for data inboards and exposure.

We had to integrate Amplitude into our system and enable import and export features. I worked with it in my previous company, where I integrated Amplitude with the app. We could import and export data, events, and user properties from Amplitude to our system. Amplitude collects the data, and we could have that data in our system so clients who use the app could also have access to Amplitude.

Real-time analytics:

We enabled real-time analytics in our app product, but it's our customers who utilize these features for their business use cases. We allow real-time tracking, segmentation, and have a complex architecture. 

When we receive an event, we process it through our Kafka clusters, and consumers get their relevant events. Tagged segments track changes in events or user properties. Whenever an event qualifies for a particular segment, the track segment is updated.

Segmentation is nice. We mostly generate our data so it can be effectively segmented. The data from Amplitude has good properties for segmentation. 

Other areas like cohort analysis, defining key events, and user properties were also well-suited for Amplitude. It is an easy tool to use.

A few things could be improved. The part that we used didn't need much improvement, but for end-users, the real-time analytics based on Amplitude's data could be improved. 

• The visualization of the properties can also be enhanced. Basically, the visualization could be better, and the real-time analytics can be enhanced. 

• Currently, real-time analytics still has some delays. Amplitude could reduce latency to provide faster insights. For visualization, they could have more charts and graphs to give users a better picture of their data.

• The query builder could be improved. Simplifying the query builder with a better interface would make it easier for regular users. It might be easier for developers right now, but going forward, Amplitude could make it more UI-based.

I have been using it for a year. 

We had a support team. If we encountered bugs or needed assistance with any feature, we could contact them on their channel, and they would extend their support.

I personally didn't face any stability challenges, but other people working with them would usually post requests for support. If we wanted to make some changes to their common APIs, we could raise a request or create a pull request in their common repos.

I would rate the stability a nine out of ten. Its uptime and reliability are good. We didn't face issues with that. But why not ten out of ten because there are still areas for improvement. For example, the latency part. Reducing latency would improve real-time data processing. Also, Amplitude could have more detailed errors that could help make the system more stable. If users know the reason behind an error, they would understand that the system is still stable.

The scalability was also good. We could handle large volumes of data efficiently.

It can handle large volumes of data and process real-time data. We can also get insights from it. The schema is flexible, which is a major concern for scalability. We can do a lot of horizontal scaling. It is available with Amplitude. 

Scalability is good, but there might still be some areas for improvement. So, I would rate it nine out of ten.

The customer service and support were responsive and had multiple channels for interaction, such as email, chat, and phone. They responded in a timely manner, especially through email. 

However, they didn't offer 24/7 support, which would be more useful.

Positive

I didn't have much difficulty with integration or setup because I had the required documentation. 

They already had steps for installing the Amplitude SDK and the initial setup with the API key, so it wasn't challenging.

Deployment time: It would have taken a couple of days.

It is worth it because it collects high-quality data. For "cost efficiency" or "worth the money." What you give and then what you get. If I have to evaluate based on that, then it's like an eight out of ten.

It gives a good amount of utility for the cost we pay, like scalability and user-friendly features. Most of the things are user-friendly.

Overall, you can get a good experience working with it, even though it's a little higher on the pricing. If you're considering whether it's worth it in terms of money, you should look at your scalability needs.

If you anticipate that your data volume is going to increase a lot, then you have to consider the packages they offer. It's more of an analysis that you have to do based on your particular use case. 

Pricing is a little on the higher end, especially when considering scalability. The cost goes up significantly with larger volumes of data. Better cost management could be implemented.

I would completely recommend it.  

1. Considering scalability, cost efficiency, and other aspects, I would give it an eight out of ten.


2. For features, capabilities, and scalability, I'd give it a nine out of ten. 
3. For stability, I'd also give it a nine out of ten. 
4. For support and cost-effectiveness, an eight out of ten. 
5. Regarding integration, it has been effective and good, but with some other similar tools, it has been even more seamless. So, for ease of integration, I would also give it an eight out of ten. 

Overall, considering all five factors, it would be somewhere between eight and nine. So, I'll rate it an eight out of ten. 

I have been working with Amplitude Analytics for around one year, mainly using it alongside GMP products like Google Analytics Four and Google Tag Manager. 

We recently started using Amplitude Analytics and are in talks with Amplitude for a partnership. It provides valuable real-time insights, particularly beneficial for media services and e-commerce websites needing immediate data-driven decisions.

In Amplitude, clients can leverage existing models like the linear model and first-click model to compare their campaign performance based on specific requirements.

Amplitude offers flexibility in real-time data analysis, allowing users to make immediate decisions. It provides in-built A/B testing functionality, which eliminates the need for third-party integrations. A

mplitude's session replay feature allows recording of user interactions, which helps identify and fix user challenges on specific pages. The reporting functionalities are superior, particularly with Amplitude's ability to create multi-step funnels, unlike Google Analytics Four.

The free features in Amplitude Analytics need enhancement. The limitations, such as not being able to use the splitting method for certain events, restrict reporting capabilities. This contrasts with Google Analytics Four, where there's more freedom in passing parameters and creating reports.

I've been working with analytics, including Amplitude Analytics, for about one year.

There have been no stability issues with Amplitude in the time that I have used it.

Amplitude is scalable, efficiently processing large volumes of data.

Though I had a call with Amplitude Analytics support, the representatives lacked technical knowledge. I resolved most issues through the online community and did not raise any further technical support queries.

Positive

I switched from relying primarily on Google Analytics Four due to Amplitude's ability to provide real-time data and in-built A/B testing functionality.

The initial setup involves understanding the client's business needs and KPIs. An event taxonomy is created before development begins, ensuring no direct changes are made to the production environment to avoid data noise.

In Amplitude, clients can leverage existing models like the linear model and first-click model to compare their campaign performance based on specific requirements.

Amplitude used to charge based on monthly users. However, a recent notification indicated that event count also plays a role in pricing, causing some confusion regarding the cost structure.

I would recommend using Amplitude based on individual use cases, especially for real-time reporting and A/B testing features. 

I rate Amplitude as an eight out of ten.

Public Cloud

Google

We use Amplitude for reporting and monitoring purposes and to check the business KPIs. I'm working with Western Union, and we monitor our daily KPIs, including successful transactions and log-ins. We have created dashboards in Amplitude. We generate daily reports and share them with the business stakeholders.

The solution's most valuable features are segmentation and funnel. We can create charts and bar charts for visualization purposes and check real-time data with the solution. The solution is very easy to use.

We have seen tagging issues with Amplitude in rare scenarios, which can be improved. Most of the time, the events will not be triggered, or they will be there but not triggered.

I have been using Amplitude for five years.

We are not facing any stability issues with Amplitude.

I rate the solution’s stability an eight to nine out of ten.

The solution is easy to scale. Around 1,000 users are using the solution in our organization.

The solution's technical support team is very helpful, and we get timely responses from them. Whenever we face issues with the solution, we directly send an email to the support team. The support team immediately raises a ticket and tries to resolve it as soon as possible.

Positive

We also use Adobe Analytics in our organization. While there is a two-hour data delay in Adobe Analytics, Amplitude provides real-time data most of the time.

The solution’s initial setup is easy.

We take real-time decisions based on the solution's charts. We get an automated email from the solution in our mailbox so that we can particularly only check those error reports into Amplitude. If an end user gets an error while trying to do a transaction, we get alerts from the solution.

I would recommend the solution to other users. Amplitude is a very easy-to-use and user-friendly tool. It allows us to create charts, demonstrate data, and view it effectively.

Overall, I rate the solution a nine out of ten.