Hotjar: Complete Heatmaps and Session Recording Guide

What is Hotjar

Hotjar is a web behavior analytics platform that combines heatmaps, session recordings, surveys, and feedback forms in a single product. Founded in 2014 and acquired by Contentsquare in 2021, it has become the reference tool for CRO, UX, and product teams wanting to understand how users interact with their web pages.

Unlike quantitative analytics tools like Google Analytics or PostHog, Hotjar adds the qualitative dimension to analysis: it does not just tell you how many users abandon a page, it shows you exactly where they click, how far they scroll, and what stops them. This combination of quantitative and qualitative data is the foundation of any rigorous CRO process.

Core features

Heatmaps

Hotjar heatmaps aggregate the behavior of all users into a visual representation. There are three types:

• Click maps: show where people click, including clicks on non-interactive elements that reveal frustrated expectations.
• Move maps: track cursor movement, which correlates with visual attention on desktop.
• Scroll maps: indicate how far down the page users reach. The point where 50% of users stop scrolling is the effective visibility limit for any content below that line.

Heatmaps are especially useful for detecting high-traffic elements that do not convert, ignored buttons, or key content that falls outside the typical attention area.

Session recordings

Recordings capture each user's complete session: mouse movements, clicks, scroll, form interactions, and JavaScript errors. Hotjar applies automatic masking of sensitive data (password fields, card numbers, etc.) to comply with GDPR.

Recordings are the most valuable resource for diagnosing specific problems. If a heatmap shows that 80% of users do not scroll past the first block of a landing page, recordings show you why: is there a confusing element? A form that does not load correctly? An image that breaks the visual flow?

Combined with funnel data, they allow seeing the exact behavior of users who abandoned at each step. This is essential before designing any A/B testing hypothesis.

Surveys and feedback

Hotjar allows launching contextual surveys on the web: on page entry, on exit intent, after completing an action, or after a set time on the page. Responses are automatically linked to the user segment, device, and URL.

The feedback widget allows users to rate pages and leave comments in real time. This qualitative signal is especially useful for identifying issues that behavioral data does not directly explain.

Conversion funnels

Hotjar includes a basic funnel module showing abandonment rate between defined steps. Although less powerful than funnels in tools like PostHog or Google Analytics 4, the advantage is that from the funnel you can click on any step and go directly to recordings of users who abandoned at that point.

Hotjar vs alternatives

Feature	Hotjar	Microsoft Clarity	FullStory	Contentsquare
Heatmaps	Yes	Yes	Yes	Advanced
Session recordings	Yes	Yes	Yes	Yes
In-page surveys	Yes	No	No	No
Feedback widget	Yes	No	No	Yes
Revenue analysis	No	No	Yes	Yes
AI insights	Basic	Basic	Advanced	Advanced
Price	Freemium	Free	Enterprise	Enterprise
Session limit	By plan	Unlimited	By plan	By plan

Microsoft Clarity is the most direct free alternative. It offers heatmaps and recordings with unlimited sessions at no cost, but lacks surveys, feedback, and more advanced integrations. For teams with limited budget, Clarity is an excellent starting point.

FullStory is more oriented toward product analytics with retroactive querying capabilities (you can ask questions about past events without having defined them in advance). Contentsquare is the most complete enterprise platform on the market, with revenue attribution by page zone and digital experience analysis at scale. Hotjar occupies the middle segment: more powerful than Clarity, more accessible than FullStory or Contentsquare.

How to integrate Hotjar into the CRO workflow

A rigorous CRO process follows a sequence from quantitative data to qualitative diagnosis and from there to hypothesis and experiment. Hotjar fits into the diagnosis phase:

Step 1: Identify problem pages in analytics. Google Analytics or PostHog tell you which pages have high abandonment rates, low time on page, or low scroll depth.

Step 2: Open Hotjar on those pages. The heatmap shows you visually what is happening: which elements attract attention, what gets ignored, where users click unexpectedly.

Step 3: Watch recordings of users who abandoned. Filter for users who reached that page and did not convert. Watch 20 to 30 recordings looking for recurring behavioral patterns.

Step 4: Launch an exit survey. If heatmaps and recordings are not conclusive, an exit survey asking "Why did you not complete [action]?" can reveal the real reason.

Step 5: Formulate the hypothesis and design the test. With this diagnosis, you have the basis for a well-founded hypothesis and can prioritize it within your CRO audit.

Technical implementation

Hotjar installs with a JavaScript snippet, either directly in the website code or through Google Tag Manager. GTM implementation is more recommended because it allows activating or deactivating Hotjar without touching the code, and managing its loading conditionally (for example, only on pages you want to analyze).

For high-traffic sites, it is worth configuring the session recording percentage (sampling) to control data volume and performance impact. Hotjar has minimal impact on Core Web Vitals when loaded asynchronously, but on highly optimized sites it is advisable to monitor this.

Limitations

Hotjar has limitations in revenue analysis: it cannot attribute revenue to specific page zones or calculate the economic impact of the UX issues it detects. For that, Contentsquare or FullStory are more powerful alternatives.

The AI engine for automatic insight generation is still basic compared to enterprise platforms. The qualitative signal from surveys requires sufficient response volume to be statistically representative.

Conclusion

Hotjar is an indispensable tool in any CRO team's stack. It provides the qualitative dimension of analysis that quantitative data alone cannot deliver: seeing real user behavior, listening to their feedback, and understanding the experience from their perspective. This is what turns data into well-founded hypotheses and experiments into predictable wins.

If you want to learn how to integrate tools like Hotjar into a continuous optimization process, the first step is defining the working framework. A CRO audit gives you exactly that. At Boost we help teams build diagnostic and experimentation workflows that generate measurable and sustainable results. You can also analyze your website for free with Scan&Boost.

Adrià Vidal — Boost