Hotjar Is Worth It If You Watch, Then Ask Why
Hotjar review for UX researchers: heatmaps show what happened on the live page; surveys ask why. Live pricing, sampling limits, and when Clarity is enough.

Hotjar review for UX researchers: heatmaps show what happened on the live page; surveys ask why. Live pricing, sampling limits, and when Clarity is enough.

Pay for Hotjar if you will watch a live page, then ask why in the same session. Skip Observe-only work. Microsoft Clarity is free, and new Hotjar signups now buy Contentsquare after the 1 July 2025 merge.
Experience Analytics Growth is $49/mo billed annually. Voice of Customer Growth is from $99/mo. Hotjar still documents itself as Observe (heatmaps, recordings), Ask (surveys), and Engage (interviews).
Hotjar is not a replacement for Google Analytics. The loop that still justifies a bill is heatmap, then survey, then a filtered recording.
The 2026 catch is replay sampling on Contentsquare Free (5% of sessions, max 10k per month) and a split bill for analytics versus surveys.

Hotjar is a behavior-analytics and feedback product for sites you own. David Darmanin founded it in Malta in 2014 as a distributed company. Contentsquare acquired it on 1 September 2021.
Hotjar Ltd legally merged into the Contentsquare Group on 1 July 2025. New buyers sign up at app.contentsquare.com. Pricing lives on Contentsquare pricing.
Help.hotjar.com still describes the product as Observe, Ask, and Engage. Observe is heatmaps and recordings. Ask is surveys and on-site feedback.
Engage is recruit, schedule, host, and transcribe interviews. The tracking snippet and help center still exist.
The commercial identity changed. Competitor blogs that still quote 35 sessions per day as the live free tier are describing a card you cannot buy.
The live Hotjar landing claims 1.3+ million websites. Treat that as a vendor install counter, not a 2026 customer census.
Contentsquare also owns Heap (product analytics), a separate module.
For how this class of tool sits next to interviews, diary studies, and usability tests, use the UX research methods guide.
A Hotjar heatmap is an aggregate of pointer and viewport data on the current live page. You see how far people scrolled, which controls they clicked, and which blocks they ignored. That is issue indication and a place to look, not a diagnosis.
Nielsen Norman Group treats this class of data as issue indication, investigation, and triangulation next to qualitative work. The useful loop is: pick a page with a goal, heatmap that page, poll it, then watch a named cohort.
David Darmanin, Hotjar's founder, warned against reading a heatmap in isolation.
"I think heat maps using isolation can be very dangerous because they're pretty much open to interpretation."
David Darmanin in "Are You Using Heatmaps Correctly?" (Talia Wolf)
Sit down without a question and the same interview is blunt:
"you're literally looking for a needle in a haystack."
David Darmanin (Talia Wolf, 8:44)

Official heatmap limits are the part of the product that actually changes a study. Iframes are a black box: no click data inside. HTML capture caps at 10MB.
Screenshot height caps at 50,000 pixels. Canvas and WebGL are not in the DOM, so they never appear.
Scroll inside a <div> instead of <body> produces the wrong screenshot height, with no workaround. Screenshots do not execute JavaScript. Dynamic content (pop-ups, dropdowns, lazy-load) used to be missed by default.
Hotjar now says the update screenshot tool can capture it in most cases. Content that unloads on scroll is still inconsistent.
Custom fonts can fail. You cannot share a heatmap by link to someone without access.
Mobile heatmaps record tap or vertical scroll. Horizontal swipe (a carousel) is not tracked. Hotjar cannot detect scroll when both html and body have overflow-x: hidden.
Deleting a recording deletes associated heatmap data. Sites you do not own, and native apps, are out.
Click maps are not eye-tracking. NN/g gaze heatmaps aggregate eye fixations and need about 30 participants to be reliable.
Hotjar click, scroll, and move maps are pointer and viewport aggregates from live traffic. Do not equate red clusters with gaze.
Split heatmaps by device. Desktop and mobile layouts differ, so a blended map mixes two pages.
A red cluster on a pricing table can be confusion about a metric, not intent to buy. On r/PPC, the recurring use of heatmaps is confirmation after a paid-traffic miss, not a revelation.
"Hotjar and Clarity are useful but honestly they're more confirmation than revelation. You watch a session replay and think 'interesting' but rarely have an 'aha' moment that changes everything. Heatmaps tell you where people scroll, not why they left."
u/dillwillhill in r/PPC (Apr 2026)
You see the struggle on a form, a rage click on a dead control, or a scroll past the CTA. A recording captures one visit: mouse movement, clicks, scrolls, and typed input (unless suppressed).
You still do not know if the cause was price, copy, or comparison shopping. Filter first.
Watch converters, a micro-conversion, a landing page you are about to change, or a funnel step that already fails. An unused library of abandoners is the default failure mode, on Hotjar and on every rival.

Product managers on Reddit treat unfiltered playback as low context.
"I am not a fan of watching videos because they're so low context. I think where they can be helpful is if you already have a theory that you want to test."
u/undertheliveoaktrees in r/ProductManagement (Apr 2025)
The same thread still prefers five people in the room, because you can ask why.
"You watch 5 people in person go through the user flow. Then when they have difficulty you can ask them why."
u/r1pen in r/ProductManagement (Apr 2025)
That is usability testing, not session replay. Recordings support a hypothesis you already have. They are a poor substitute for a moderated session.
A session ends after 30 minutes of inactivity, or when the visitor leaves and does not return within 30 minutes. That is not a live war-room feed.
Max session length is four hours. Hotjar cannot track across multiple top-level domains.
Navigating to a third-party payment gateway always stops a recording. Numbers with 9 or more characters are always suppressed on-device. Shorter numbers are suppressed by default.
Ads, chat, and other iframe content are suppressed in playback. Default ignore covers sessions under 30 seconds (toggleable).
That gap versus GA4 bounce reporting is a common source of "Hotjar undercounts" tickets.
Vendor copy that says replay "reveals why users struggle" is marketing. Replay shows the struggle. Why still needs a survey, an interview, or an experiment.
Contentsquare, Mouseflow, and FullStory posts use the same "why" language for what happened on the page.
Burst capture beats always-on libraries. Ruben Ugarte puts it as: run a week, pause, then run another week.
Pair that with an identity so you can filter by plan or "cancelled in the last 30 days," not by random traffic.
Replay fidelity bugs (broken images, CORS on heatmap screenshots, missing CSS) hit Hotjar and Clarity. One r/PPC comment preferred Hotjar because Clarity failed to load CSS. Treat that as a local implementation issue, not a ranking of engines.
If you only need a replay catalog, stop here and use Clarity. For a tools landscape, Marketful's session replay tools already covers the category.
Ask is the layer Reddit still pays for. Clarity has heatmaps and replay. Clarity does not have native surveys.
"Hotjar also has surveys, which can be useful in helping diagnose conversion problems, but that's the only thing I miss from Hotjar that Clarity doesn't provide."
u/wearethemonstertruck in r/PPC (Mar 2025)

Surveys run on-site (Popover, Button, Embedded, Bubble, Full Screen) or as a link survey on another domain with no tracking code. Targeting uses URL, JS Events, and User Attributes.
Partial responses count when the user clicks Next. A response can connect to a session recording. That join is the research product.
AI can create, summarize, tag, and score sentiment. NPS is a 0-10 score. One language per survey.
Survey plus email can invite someone into an Engage interview.
Ask is metered separately from Observe. Allowance resets on the 1st of the month. Unused responses do not roll over.
Live Contentsquare Voice of Customer (29 August 2026): Free is $0, up to 100 survey or feedback responses per month, 3 widgets, 1 month of response access. Growth is from $99/mo billed annually, starting at 500 responses, unlimited widgets.
The Experience Analytics Free card also mentions 100 "basic surveys" per month, then Voice of Customer is sold again as its own product. One $49 bill does not cover research-volume surveys.
Surveys collect claimed intent. They do not recover behavior. Nielsen Norman Group's 2025 line: say vs. do are different things.
Just asking users what they want isn’t enough. What people say vs. what they do are different things. That’s why UX relies on: ✅ User interviews → Understand beliefs & goals ✅ Usability testing → Spot usability issues Learn more: https://t.co/E3mpZ9Y5bg #UserResearch https://t.co/C6k6ciPaSx
Rapport has a ceiling too. MeasuringU's 2026 warning: push it too far, and it can do the opposite of making honesty easier.
Rapport is supposed to make honesty easier. Push it too far, and it can do the opposite. https://t.co/gP1Gc35Ucn https://t.co/1B895YGxdk
Engage is the interview surface: recruit, schedule, host, record, transcribe, collaborative notes. Documented uses include prototype tests, usability tests of a shipped feature, rebrand interviews, and persona interviews.
NN/g still applies: interviews fail on behavior questions (will they buy, which color, which features). Observe those. Ask about goals, expectations, and feelings.
For the broader qualitative stack (interviews, diary studies, thematic analysis), see qualitative research.
Hotjar is strong at what happened on the current live page. It is weak at everything a journey map, a prototype test, or a causal "why they left" question needs.
NN/g is direct: analytics cannot tell you each user's specific goals or expectations, and cannot provide thoughts and feelings that make journey mapping valuable. Path reports mix people who may have had different intentions.
Two people exiting a SERP without a click can be frustration or good abandonment. The recording will not tell you which. A heatmap will not either.
A click or scroll heatmap cannot answer sequence. If a map shows 40% on the size guide and 30% on add-to-cart, you still do not know which came first.
It cannot recover an individual journey. The scroller who abandoned is blended with the one-pass buyer.
It cannot prove causation. A cold zone can mean boring, or already absorbed. It cannot show an unbuilt page.
It can show scroll-depth invisibility, dead clicks, and a mismatch between attention and the intended CTA.
Darmanin again, on the ceiling:
"The first thing is understanding the limitations of a heatmap. They can only show you what's happening. It can only give you the what."
David Darmanin (Talia Wolf, 28:11)
On r/userexperience, the practical fix is purpose, not more tape.
"Watch them for a purpose. You're creating a new feature which will change the settings page, go look at some user interactions with that page."
u/Ezili in r/userexperience (May 2026)
Skip Hotjar for journey mapping, unbuilt UI, causal "why they left," native apps, iframe widgets, canvas, WebGL, and pages you do not own. Skip it for live war-room watching and for conversion rates on a sampled Observe plan. Third-party checkout stops the recording.
If the job is a full UX research tools stack (moderated tests, card sorts, prototype studies), Hotjar is one instrument. It is not the lab.
Each Hotjar site has a daily session capture limit for heatmaps and recordings.
Exceed it and Hotjar samples at an even rate over a moving 24-hour window. It does not stop. It does not queue.
Coverage is roughly plan daily limit divided by potential traffic. Docs use 500 daily on 1,000 potential as 50%.
The coverage widget ignores targeting and can overstate real coverage. After install, potential traffic is estimated until Hotjar has enough days of measurement.
Untrackable traffic includes JS blocked, cookies blocked, DNT, incognito, ad blockers, and CSP. Discarded even when the script loaded: plan exhausted, 30-second filter, or targeting miss.
A stored session still needs activity (input, key, click, select, or viewport scroll) in the Observe model.
Heatmaps can still show a pattern under sampling. Recordings of abandoners cannot. Funnel math on a sampled Observe plan is the worst case: you are reading a rate from a non-census.
Contentsquare Free (live 29 August 2026) advertises up to 200k sessions per month. Session-replay capture on that plan is 5% of sessions, max 10k per month, with 1 month of replay retention.
Growth replay is 15% (min 20k) with 2 months. The 200k figure is analytics sessions, not watchable recordings.
Microsoft Clarity's 2026 warning makes the sample even noisier: a growing share of site traffic is not human.
🤖 𝐈𝐧 𝐜𝐚𝐬𝐞 𝐲𝐨𝐮 𝐦𝐢𝐬𝐬𝐞𝐝 𝐢𝐭: AI Bot Activity in Microsoft Clarity just got a major update. A growing share of your site traffic isn't from humans. It's from AI crawlers, automated agents, and bots. Here's what you can now do with the enhanced Bot Activity https://t.co/HyaDoqFcNZ
Any Observe claim about "what users did" has to survive that filter. 2020 Hotjar discourse did not have to.
Suppression runs in the browser before data is sent. It is not retroactive.
User input is suppressed by default. Unless the end user gave clear advance consent, do not use recordings to inspect an identifiable person.
Turning session capture off stops recordings and heatmaps. Surveys continue.
<div> scroll: the help center tells you what will lie.Prices below are from contentsquare.com/pricing (checked 29 August 2026). You pick a plan per product.
EU billed in EUR; everyone else USD. Growth is self-serve. Pro and Enterprise are sales.
Plan | Price | Sessions | Replay capture |
|---|---|---|---|
Free | $0 | Up to 200k/mo | 5%, max 10k/mo; 1 month |
Growth | $49/mo, billed annually | From 7k (table also 7k-10m) | 15% (min 20k); 2 months |
Pro / Enterprise | Let's talk | From 1m+ / custom | Up to 100%; 2-24 months |
Growth is marketed "from 7k monthly sessions" while Free is "up to 200k." Free's 200k is analytics sessions. Live checkout is the only way to settle how $49 Growth at 7k beats Free.
Plan | Price | Responses | Widgets |
|---|---|---|---|
Free | $0 | Up to 100/mo | 3 |
Growth | From $99/mo, billed annually | From 500/mo | Unlimited |
Product Analytics (Heap) is sales-gated.
These are not current checkout: Observe Plus ~$32/mo, 35 sessions/day as the free tier, $39 Observe, or three Hotjar subscriptions as the live card.
The Contentsquare + Hotjar landing is the primary old-versus-new Free table: 35/day versus 200k/month, 20 versus 100 survey responses.
Existing Hotjar orgs follow a migration FAQ: 30 days of dual collection, then (unless the Account Owner opts out) the Hotjar subscription switches to Contentsquare Growth.
The Hotjar account is read-only for 90 days, then Hotjar data is deleted. You cannot go back to Hotjar after those 30 days.
Opt-out keeps Hotjar. Contentsquare data from the 30 days is deleted within 90 days.

Value for a researcher is the join, not the session count. If you will not run Ask, you are buying a sampled Observe catalog that Clarity already gives away.
If you will run Ask on the same sessions, $49 plus Voice of Customer from $99, billed annually, is the self-serve research bill.
Hotjar is ideal for:
Hotjar is NOT ideal for:
Clarity processes anonymous behavior data to improve Microsoft ML models. That is Microsoft's first-party rationale. Decide if your research ethics bar accepts it.
Buy Hotjar (now Contentsquare) when the research loop is watch the live page, then ask in the same session. Do not buy a bigger replay library to fix unused recordings. If Observe is all you need, Clarity is the default.

13 AI wireframe generators ranked by output type, with real free-tier limits, pricing comparisons, and hands-on picks for UX designers and product teams.

Compare the 10 best brainstorming tools for 2026. Features, pricing, pros and cons of Miro, FigJam, MURAL, MindMeister, and more.

Compare the 10 best Miro alternatives for UX teams in 2026, including FigJam, Mural, Excalidraw, Whimsical, and more.