Amplitude Digital Analytics Platform

What do you like best about the product?

I like the ability to build funnels for self-trial leads and understand the patterns of their drop-offs using Amplitude Analytics. I find the feature that collects data on events and highlights where we should focus based on drop-offs to be very useful. I appreciate the MCP and the option to export data as a PDF. Additionally, the ability to filter or group events by different factors to get more precise data is valuable to me. Overall, I am happy with Amplitude Analytics and the amount of insights I receive from it.

What do you dislike about the product?

When exporting via PDF, sometimes the text and charts overlay each other, making it not fully readable, which complicates sharing it with others. However, there are different ways to handle this, and I use those workarounds.

What problems is the product solving and how is that benefiting you?

I use Amplitude Analytics to build funnels for self-trial leads. It helps me understand drop-off patterns and indicates where we should focus more attention, based on events data.

What do you like best about the product?

It's great in viewing detailed logs of user journeys and understanding user behavior. It has a very smooth interface that is easy to understand. It's connected with claude which is good. It can handle many inputs at once. I am in intern, so pricing does not concern me. It was easy to understand and gain support, especially since claude was connected.

What do you dislike about the product?

I am not able to view personal IPs but then again Amplitude is a client-side software. Also the Inbuilt AI felt quite limited when it comes to giving de
tailed and informed responses.

What problems is the product solving and how is that benefiting you?

okay with amplitude we are able to view user behavior. for example we witnessed spikes at 1:00am throughout the week. we were able to investigate this thanks to amplitude.

What do you like best about the product?

I use Amplitude Analytics for mobile game analytics, tracking retention, revenue, funnels, and the most popular in-app purchases. I really like that it works fast and in real-time. I usually build cohort analysis and compare different audiences and cohorts effectively. The initial setup was super easy.

What do you dislike about the product?

I'd really love to have LTV and ARPPU, paying users conversion as standard, basic features, not extras. Currently, I have to use other tools to check these core metrics.

What problems is the product solving and how is that benefiting you?

I use Amplitude Analytics to track retention, revenue, and popular in-app purchases. It works really fast and in real time, helping me build cohort analysis and compare audiences.

What do you like best about the product?

I really appreciate the way Amplitude Analytics has adopted AI and offers a cloud experience where I can ask it to generate dashboards for new features like WhatsApp, and it can generate those dashboards by itself. That's pretty cool.

What do you dislike about the product?

Just too many things on the left nav bar, makes it hard for me to navigate to my things.

What problems is the product solving and how is that benefiting you?

I use Amplitude Analytics to capture UI events and track feature adoption, which helps us validate feature performance and improve the product.

What do you like best about the product?

The funnel dashboards are what I rely on most. In the past, answering a question like where users were dropping off in a flow meant submitting a data request and waiting in someone else’s queue—and by the time the answer came back, the context had usually shifted. Now I can build the funnel myself and iterate on it in the same sitting, which turns what used to be a multi-day round trip into a same-day answer. That move from “request the data” to “answer it myself” has been the single biggest win.

I also like that I can segment a funnel and immediately see which step the drop-off is concentrated in, without writing SQL. It lets me pursue my own hypotheses as they come up, instead of batching everything into one big ask.

What do you dislike about the product?

Event selection and taxonomy are my biggest friction point. In a large org, there’s a lot of duplication in the event list: several similarly named events for what is effectively the same user action. The picker also doesn’t help you tell which event is canonical or even actively instrumented. As a result, building a funnel correctly depends on already knowing the taxonomy, which is a real problem for anyone new to the workspace. Surfacing volume or last-seen data directly in the event picker would resolve most of this confusion.

Onboarding also assumes you already know the tool. Getting access isn’t the same as being productive. The docs explain what each chart type does, but not which one to reach for given a specific question, so early on I spent more time debating chart types than actually analyzing. A guided “you’re trying to answer X, start here” path would shorten ramp-up considerably.

Discoverability of existing work is another challenge. With a large number of projects and lots of previously built charts and dashboards, it’s genuinely hard to know whether the analysis you need already exists. I’ve rebuilt things that were probably already sitting in someone else’s dashboard. Search seems to rely on you already knowing the right title, and the practical result is duplicated effort across teams.

What problems is the product solving and how is that benefiting you?

The core problem it solves is the bottleneck between having a question about user behavior and getting an answer. Before, that usually meant filing a data request and waiting in an analyst queue, so turnaround was measured in days. By the time the answer arrived, the decision it was meant to inform had often already been made. Amplitude shifts that to self-serve, so the answer comes back while the question still matters.

The business benefit is twofold. First, it frees up analyst capacity: routine “where are users dropping off?” questions no longer consume specialist time, and that time can go to deeper work. Second, and more valuable, it lowers the cost of asking. When a follow-up question takes minutes instead of a formal request, more questions get asked, and decisions end up grounded in data rather than in whoever argued most confidently. Things that were previously dropped because they weren’t worth the overhead now simply get answered.

It also gives teams a shared source of truth for the numbers, so discussions start from the same figures instead of first having to reconcile competing spreadsheets.

What do you like best about the product?

I like how easy Amplitude Analytics is to understand and use. I appreciate how it makes tracking events and app errors much easier, and it helps us understand app usage better. I also find it easy to build dashboards, which is really helpful, and I like being able to ask agents for follow-ups and reports.

What do you dislike about the product?

Sometimes it's very slow, it won't load the page. Also, I don't know how to connect it to other tools, which is a bit frustrating.

What problems is the product solving and how is that benefiting you?

Amplitude Analytics simplifies tracking events and app errors, and helps us understand how and why the app is used.

What do you like best about the product?

I really like how Amplitude Analytics keeps the event specs and code in sync, making it simpler to work with the Analytics Team. It makes sure no information is missed when an analyst creates an event, as all necessary details are automatically synced into the codebase. This effectively bridges the gap between analysts and software engineers, eliminating the need for manual synchronization of event specifications.

What do you dislike about the product?

The dashboard is quite confusing to navigate, making it hard to find where events are shown and how to configure experiments. It would help to have separate views for different users, such as one for those who consume data and another for those who create events. Also, remembering to access the EU instead of the US website can be problematic, as the login flow does not redirect to the correct instance. I often find it difficult to navigate to the correct tab, especially since developer-related information lives under 'Data,' which is relatively hidden in the menu. Renaming the 'Data' tab and adding more links to it from different parts of the dashboard could be very helpful.

What problems is the product solving and how is that benefiting you?

Amplitude Analytics helps us understand user interactions, streamline communication between Analytics and Tech, and sync event specs directly into code, eliminating manual tracking.

What do you like best about the product?

I appreciate that Amplitude Analytics allows non-technical people to see and review product analytics. I love that the data is kept in very high quality, and I never found an issue with the data Amplitude presents me. I also like how intuitive the platform is, making everything very easy to use and understand. The initial setup was very easy.

What do you dislike about the product?

I find the UX sometimes not intuitive enough and it requires learning, especially for new users. The platform is very robust, and the simple happy flow is not always clear enough for more novice users.

What problems is the product solving and how is that benefiting you?

I find Amplitude Analytics allows non-technical people to see and review product analytics easily. It supports my growth analysis, retention, and usage pattern evaluations with its high-quality data and intuitive interface.

What do you like best about the product?

Honestly, Amplitude has become the tool I open before anything else in the morning. Building charts is fast and intuitive — you can go from "I wonder why checkout drop-off spiked" to a segmented funnel with cohort filters in under five minutes, no SQL needed. The event segmentation and funnel views are super flexible, and once you get the hang of the property filters, you can slice data in ways that would take hours in a BI tool.

Session replays are a nice bonus too — being able to jump from a funnel drop-off directly into real user recordings to see what actually happened is genuinely useful and saves a lot of back-and-forth with the team.

On the integration side, the MCP connector has been a game changer for us. We can pull Amplitude data into our broader analytics workflows programmatically, which means less manual exporting and more time actually acting on insights.

What do you dislike about the product?

The API has some real limitations that catch you off guard. There's a hard cap on how many series you can query at once, which means for larger analyses you end up exporting CSVs manually from the UI — not a dealbreaker, but a bit clunky. Some of the more advanced filter behaviors (especially around multi-value properties) aren't well documented, so there's a lot of trial and error if you're doing anything non-standard.

Onboarding is also trickier than it looks. The UI feels approachable but there's a lot of depth hidden underneath, and new team members often underuse it for the first few months without dedicated enablement.

What problems is the product solving and how is that benefiting you?

The biggest thing Amplitude solves for us is getting rid of the "I think users do X" problem. Before having a proper analytics setup, a lot of product decisions were based on gut feel or one-off data pulls from engineering. Now we can answer most funnel and behavior questions ourselves, in real time, without filing a data request.

it's helped us in a few key areas:

1. We can pinpoint exactly where users are falling out of a checkout or signup flow, and more importantly, segment that drop-off by platform, user cohort, or event property to figure out why. That's gone from a days-long investigation to a 10-minute chart.
2. Tracking trial-to-paid conversion, understanding what behaviors predict a purchase, and measuring the impact of pricing or UX changes has become way more structured. We've run analyses that directly shaped how we think about our subscription products.
3. Knowing whether a new feature actually gets used — and by whom — used to be guesswork. Now we instrument the feature on launch and have retention and engagement data within days.
4. Dashboards are shareable, so product, marketing, and engineering can all look at the same numbers. Fewer "which version of the data is right" conversations.

What do you like best about the product?

The way that is easy to track a user journey and also enable and disable FF

What do you dislike about the product?

is not very intuitive for user who don0t use it everyday

What problems is the product solving and how is that benefiting you?

track the user flows and take decisions based on that