What is Hotjar

What it does

Hotjar captures qualitative behaviour and feedback signals on top of your quantitative analytics.

• Heatmaps of clicks, taps, scroll depth and mouse movement.
• Session recordings that replay real visits (with sensitive-field masking).
• On-site surveys, feedback widgets and polls to capture user sentiment.
• Funnels and conversion drop-off views to spot where users leave.
• Frustration signals such as rage clicks and U-turns to flag UX problems.

Where it fits in your stack

Hotjar is the qualitative CRO layer that pairs with GA4. Analytics identifies where the problem is (which page, which step); Hotjar shows why users struggle there. Together they turn a conversion hypothesis into an evidence-backed test, which is the core loop of any CRO programme.

Strengths and limits

Strength: fast, visual insight into real behaviour that numbers alone cannot give, plus easy feedback capture. Limit: it samples rather than records everyone on lower tiers, it is qualitative (not a traffic-measurement tool), recordings can be time-consuming to review, and it collects user-session data — so consent, masking and privacy configuration are non-negotiable.

How REO Rank uses it

In CRO engagements we deploy Hotjar via Google Tag Manager with proper masking, then use heatmaps and recordings on GA4-flagged problem pages to form test hypotheses. It is evidence for a change, never the change itself — every finding feeds a measured experiment.

Why it matters

Hotjar is a behaviour-analytics tool that shows how users actually experience a site through heatmaps, session recordings, and on-site surveys and feedback. It matters because traditional analytics (like GA4) tells you what happened — how many people visited, where they dropped — but not why, and Hotjar fills that gap with qualitative insight into the real on-page experience. Seeing where users click, how far they scroll, where they hesitate or rage-click, and what they say, turns abstract drop-off numbers into concrete, fixable friction, which is why it is a staple of conversion-optimisation work.

• A behaviour-analytics tool: heatmaps, session recordings and on-site surveys
• Shows the "why" behind the "what" that analytics reports
• Turns abstract drop-off into concrete, visible, fixable friction

What it offers

Hotjar's core features are heatmaps (aggregated visualisations of where users click, move and scroll on a page), session recordings (replays of individual user visits showing exactly what they did), and feedback tools (on-site surveys, feedback widgets and polls that capture the voice of the user). Together these provide the qualitative layer of behaviour analytics: heatmaps reveal patterns across many users, recordings reveal individual struggles in detail, and surveys reveal motivations and objections directly. It is a complement to quantitative analytics, not a replacement — GA4 measures the scale of a problem; Hotjar shows you what the problem is.

• Heatmaps: aggregated click, move and scroll patterns across users
• Session recordings: replays of individual visits and where users struggle
• Surveys and feedback: the voice of the user, captured on-site
• A qualitative complement to quantitative analytics, not a replacement

In practice

A typical use pairs Hotjar with analytics in a conversion-optimisation loop: analytics identifies a page or step with high drop-off (the scale of the problem), then Hotjar's heatmaps and session recordings show why users are leaving — an unnoticed call-to-action, a confusing form field, a broken interaction, an unexpected cost — and surveys confirm the motivation. That qualitative insight becomes a specific, evidence-based hypothesis to test. The discipline is to let the behaviour data guide research rather than watching recordings aimlessly: start from a quantitative signal, use Hotjar to diagnose the cause, then test the fix. It is the "why" engine behind data-driven CRO.

• Pair with analytics: GA4 finds the drop-off, Hotjar shows why
• Heatmaps and recordings diagnose the specific on-page friction
• Surveys confirm user motivation and objections
• Feed the insight into evidence-based CRO hypotheses, not aimless watching