Amplitude Problems & Issues

Users experience sticker shock when moving from free to paid. The jump from $0 to $49/month (Plus) seems reasonable, but Growth plan starts at $22,400/year and can reach $254,100+ annually. Pricing is the #1 cited issue for adopting Amplitude over the last 5 years.

Free plan limits of 50K MTUs with 1,000 events per MTU catch users off guard. Events exceeding 1,000 per user are converted to additional MTUs, inflating costs. If you exceed limits 3 times as a free user, Amplitude blocks your account entirely.

The platform has a steep learning curve that prevents team-wide adoption. New users struggle to navigate and do analysis independently. Documentation could be better, and advanced features require deep analytics knowledge. Teams often can't get more members involved due to complexity.

Users wish features were more integrated. Starting a query in the Funnel section requires rebuilding it from scratch in Journeys. No easy way to transfer analysis between different views. The platform feels like separate tools stitched together.

Amplitude's complexity is daunting for non-technical users. Marketing teams and business users struggle compared to data analysts. Without a dedicated analyst, meaningful events and dashboards take extensive time to configure.

The UI is always changing and teams have difficulty keeping up with new features and redesigns. Users returning after weeks find themselves lost. Interface has become increasingly complicated over the years rather than simpler.

There's no way to do month-to-date or week-to-date time selections, limiting how useful monitors and reports are. Averages are not weighted. Users find it frustrating they can't do 'monthlies' unless starting from the first of the month.

Opening reports is very slow. Reports contain excessive details that delay loading, especially for graphs and breakdown views. The analytics dashboard is well-designed but performance suffers with complex queries.

Hard to merge sessions between multiple devices and platforms. When the same user sends events from PWA and mobile app, user properties get overridden unpredictably. For complex scenarios, Amplitude's user-stitching sometimes merges users that shouldn't be merged.

Users express frustration with data export limitations and the inability to easily integrate with third-party AI tools for deeper insights. Getting data out of Amplitude for external analysis is more difficult than expected.

Free tier support described as 'generic and unhelpful.' Session replay issues go unresolved with only generic recommendations. Actions discussed with support aren't reliably delivered, context is frequently lost, and responsibility for problems feels avoided.

Significant overcounting of users due to MTU tracking methodology, especially with service worker restarts. This leads to inaccurate user metrics and inflated costs. The counting methodology differs from competitors, causing confusion.

Amplitude's session replays stopped working for some apps. Despite contacting support, only generic recommendations were provided with no actual resolution. Users report the feature simply breaks without clear reason.

Amplitude requires complex event taxonomy planning before you can get value. Implementation takes 4-6 weeks compared to 1-2 weeks for competitors like Heap with autocapture. Manual tagging leads to cumbersome setup and data management overhead.