Hotjar vs Amplitude: Visual Behavior Analytics vs Quantitative Product Analytics
These tools complement each other more than they compete. Hotjar shows you how individual users interact with pages. Amplitude shows you what users do across entire product journeys. If you can only pick one, here is how to decide.
Quick Verdict
Hotjar for content sites, e-commerce, and marketing teams that need visual page-level insights. Amplitude for product-led SaaS teams that need event-based analytics, retention curves, and feature adoption metrics. Many mature teams run both.
Different Tools for Different Questions
Hotjar Answers
- "How are users interacting with this landing page?"
- "Where do users click on the pricing page?"
- "Why are users abandoning the signup form?"
- "What do users think about this new feature?" (surveys)
- "How far do users scroll on our blog posts?"
Visual, qualitative, page-level insights
Amplitude Answers
- "Which features drive 30-day retention?"
- "What is the conversion rate from signup to first purchase?"
- "What user paths lead to the highest lifetime value?"
- "How does feature X adoption vary across cohorts?"
- "What is the impact of this A/B test on revenue?"
Quantitative, event-based, journey-level analytics
Pricing Comparison
| Tier | Hotjar (Observe + Ask) | Amplitude |
|---|---|---|
| Free | $0 (35 sessions/day, 20 responses/mo) | $0 (50K MTU, core analytics) |
| Plus / Growth | $98/mo (Plus Observe + Ask) | $49+/mo (Growth plan) |
| Business | $178/mo (Business Observe + Ask) | $249+/mo (Growth advanced) |
| Enterprise | $372/mo (Scale both) | $999+/mo (Enterprise) |
Feature Matrix
| Feature | Hotjar | Amplitude |
|---|---|---|
| Heatmaps | Yes (click, move, scroll) | No |
| Session recordings | Yes (sampled) | Yes (Session Replay add-on) |
| Surveys | Yes (Ask product) | No |
| Event-based analytics | No | Yes (core feature) |
| Retention analysis | No | Yes (cohort curves) |
| Conversion funnels | Business+ only | All plans |
| A/B testing | No | Yes (Experiment add-on) |
| User segmentation | Basic (paid plans) | Advanced (behavioral cohorts) |
| Feature adoption tracking | No | Yes |
| Lifecycle analysis | No | Yes (new/returning/dormant) |
| Data warehouse sync | No | Yes (Snowflake, BigQuery) |
| Custom dashboards | No | Yes |
| Real-time data | Near real-time | Real-time |
| GDPR compliance | Built-in | Built-in |
If You Can Only Pick One
Choose Hotjar: Content Sites and E-commerce
Content-driven websites, e-commerce stores, and marketing teams benefit more from Hotjar. Heatmaps reveal which content sections get attention. Recordings show checkout friction. Surveys capture visitor intent. These visual insights lead directly to actionable page improvements. Content sites do not need Amplitude-style product analytics because the "product" is the content itself.
Choose Amplitude: Product-Led SaaS
SaaS products with complex user journeys, feature-based engagement, and retention-focused growth strategies need Amplitude. Understanding which features drive retention, how different cohorts behave, and what paths lead to conversion are the metrics that inform product roadmap decisions. Hotjar's page-level view is too narrow for SaaS teams that need to understand behavior across the entire product lifecycle.
Using Both: The Complementary Approach
Many mature product teams use both Hotjar and Amplitude because they serve different roles in the analytics stack:
Amplitude identifies the problem. A conversion funnel shows a 40% drop-off at the pricing page. Cohort analysis reveals enterprise prospects drop off at higher rates than SMB.
Hotjar explains why. Heatmaps show enterprise prospects clicking on a feature comparison that does not exist. Session recordings reveal they scroll past the pricing table. A survey confirms they want security certifications before requesting a demo.
The team acts. Add a security section to the pricing page. Track improvement in Amplitude's funnel. Verify with Hotjar that enterprise prospects now engage with the new section.
Combined Cost Examples