Hotjar is a behavior analytics platform offering heatmaps, session recordings, and user feedback tools to help UX and growth operators understand how visitors interact with websites.
Hotjar is a behavior analytics and user feedback platform designed to help operators understand visitor behavior without relying on code instrumentation. The core offering includes heatmaps that visualize where users click, scroll, and move; session recordings that replay individual user journeys; and feedback tools like surveys and polls. For UX operators, Hotjar's heatmaps reveal friction points—areas where users hesitate, abandon forms, or fail to scroll. Session recordings show the 'why' behind analytics numbers: whether a user left because of confusion, slow load times, or intentional navigation. This qualitative layer complements quantitative tools like Google Analytics. Growth operators use Hotjar to identify conversion bottlenecks. Recording playback of users who drop off at checkout or sign-up reveals usability issues that A/B testing alone won't surface. Heatmaps on key pages show whether CTAs are visible or ignored. Surveys can capture intent at the moment of friction. The platform operates on a freemium model. Free plans include limited recordings and heatmaps, suitable for testing on single pages. Paid tiers unlock unlimited recordings, advanced filtering, and integrations with tools like Slack, Zapier, and Google Analytics. Pricing scales with traffic volume and feature access (verify on vendor site for current rates). Hotjar does not require code changes for basic functionality—it works via a single script tag. This lowers implementation friction for non-technical teams. However, operators should note that session recording raises privacy considerations; GDPR and CCPA compliance requires careful configuration, including consent management and sensitive data masking. Common use cases include e-commerce conversion optimization, SaaS onboarding improvement, and content site engagement analysis. The tool is most valuable when paired with hypothesis-driven testing: record sessions to form hypotheses, then validate with A/B tests or surveys. Limitations include sampling on free plans, limited historical data retention (verify current limits), and the need for manual review of recordings—automation is limited to basic filters. For teams with very high traffic, recording costs and data storage can become significant.