Hotjar
Why Hotjar
Hotjar is a product-experience analytics tool combining heatmaps, session recordings, surveys and feedback widgets to reveal how visitors interact with your website. It exposes conversion friction and helps uncover objections and hesitations through targeted one-question surveys. Best for marketing, product and UX teams wanting qualitative insight into on-page behaviour and user feedback without lengthy analysis.
What it does
Hotjar shows you how people actually use your website. Heatmaps show where visitors click, hover and scroll. Session recordings let you watch real visits. Surveys and feedback widgets let you ask visitors a question at the right moment, and funnels show where people drop off. Error monitoring flags JavaScript problems.
Hotjar is now part of Contentsquare, and it has an AI layer that summarises heatmaps and recordings and lets you ask questions of the data.
Why you would need it
Analytics tells you that a page loses visitors. It does not tell you why. You can stare at a bounce rate for weeks and still not know that a button is hidden on mobile or a form field confuses people.
The moment you need Hotjar is when a funnel stalls and the numbers do not explain it. Watching a handful of visits usually shows the problem within an afternoon.
Where it fits
Hotjar sits on top of your website as the qualitative layer, next to quantitative tools such as Google Analytics and Mixpanel. It integrates with tools such as Slack, Jira and Unbounce, so you can share a recording straight into a team channel or a ticket.
It sits in the same space as Microsoft Clarity and Contentsquare, and it replaces guesswork about design changes.
What stands out
- Heatmaps, session recordings, surveys and funnels in one tool.
- Quick set-up: one script on the site, often added through Google Tag Manager.
- Sharing to Slack and Jira, which turns a recording into evidence for a developer.
- AI summaries of heatmaps and recordings, to save time on review.
My take
I adopted Hotjar in 2014 and it remains in my toolkit. Watching recordings of prospects rage-click a disabled button on a signup form exposed a bug that no report had shown. I add the script through Google Tag Manager, and when a funnel stalls I run it for a week, watch about twenty recordings and usually find the next fix.
It has limits. The free plan captures a limited number of sessions, so on a busy site I sample traffic or record only during research sprints. It is page-level, not full product analytics, so deep event analysis still happens in Mixpanel or similar. I also switch recording off during high-traffic launches.
Verdict
Pick Hotjar when you need to understand why visitors behave as they do and you will actually watch the recordings. Skip it when your site has very little traffic, or when strict privacy rules make recording sessions hard.
Books behind it
Notes
Your note
Before you choose
It is now part of Contentsquare
Hotjar is part of Contentsquare, and the vendor's pricing page redirects there. As far as I could see, legacy Hotjar no longer takes new sign-ups, so check how you would buy and what you get before you plan around it. Compare Microsoft Clarity, which is free, and Contentsquare.
Read moreShow less
Session limits
The free plan caps the number of recorded sessions, and busy sites hit that quickly. Decide whether you sample traffic or record only during research periods, and check the plan limits first.
Privacy and consent
Recording sessions means collecting behaviour data. Mask sensitive fields, set up consent so recording starts only after agreement, and set retention to match your policy. Ad blockers can also stop some sessions from being recorded, so the sample is never complete.
Page-level, not product analytics
Hotjar shows what happens on pages. It does not follow people after they leave, and it does not replace event analytics. Pair it with Mixpanel, Amplitude or Heap when you need deeper behavioural analysis.