Running Hotjar?

Hotjar recordings missing or consent blocking? We sort it out.

Hotjar is simple to install and surprisingly subtle to live with. The consent banner blocks the tag on half your traffic, the SPA router hides the interesting page changes, the heatmap you built last quarter aggregated across two different layouts, and the session quota ran out on day twelve. We tidy each piece so the recordings you look at are actually representative of the traffic you care about.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

hotjar-session.log

still broken

What it is

Hotjar at a glance

Hotjar is a behavior analytics and user feedback tool founded in 2014, aimed at product and marketing teams who want to see what users actually do rather than just count clicks. It records sessions, builds heatmaps of clicks and scrolls, runs on-page surveys, and collects targeted feedback with floating widgets.

A single JavaScript snippet does all of it, and the data lives on Hotjar's platform. In 2021 Hotjar was acquired by Contentsquare, and the product has continued under the Hotjar brand with a free tier and paid plans scaled by daily or monthly session counts. It is complementary to quantitative analytics tools rather than a replacement for them: Hotjar shows you why something is happening, after Amplitude or Google Analytics tells you what.

Type
Behavior analytics, session recording, and feedback tool
First released
2014
License
Proprietary SaaS, session-volume based pricing
Maintained by
Hotjar Ltd., part of Contentsquare since 2021
Typically used for
Session replay, heatmaps, on-page surveys, feedback widgets, UX research

The honest version

Hotjar pros and cons

No technology is all upside. This is where Hotjar earns its place and where it tends to cause trouble.

Where Hotjar is strong

  • Session recordings are the fastest way to see UX bugsWatching ten sessions on a checkout page tells you more in an hour than any dashboard will about where real users get stuck.
  • Heatmaps are easy to generateClick, scroll and movement heatmaps come up with a few checkboxes rather than a bespoke instrumentation project.
  • On-page surveys are quick to launchA one-question micro-survey triggered after a goal event takes minutes to configure and produces real user words, not just numbers.
  • Free tier is genuinely usefulSmall teams can run real research on the free tier without a procurement process, and upgrade only when session volume demands it.
  • One snippet does everythingRecordings, heatmaps, surveys, feedback and NPS all run from a single script tag, which keeps the page weight and the maintenance surface small.
  • Reasonable PII controlsAttribute-based masking, suppressed inputs, and element masking rules let you keep session replay compliant with sensible effort.

Where Hotjar bites

  • Consent and ad-blockers cut coverageA strict cookie banner or any ad-blocker stops the tag from firing at all. The sessions you record are the ones with the most tolerant settings, which skew the sample.
  • SPA tracking needs manual helpClient-side route changes do not count as new pageviews by default. If you do not call hj('stateChange') on route transitions, heatmaps aggregate across different layouts and look like nonsense.
  • Sampling and quota behavior is opaqueOn busy days, Hotjar silently samples. The quota counter gives you a number but the UI does not tell you which sessions got recorded and which got skipped.
  • Masking rules are only as good as your disciplineA new form field with sensitive data will be recorded verbatim unless you remember to mask it. The responsibility sits with the developer every time.
  • Cross-origin iframes are mostly invisibleEmbedded Stripe Checkout, Calendly or any iframe on a different origin will not show up in the recording. The user vanishes from the session during the most interesting step.
  • Pricing scales by session volume quicklyA viral spike, an automation accident, or a crawler run burns through the daily quota in hours and leaves the rest of the month with no visibility.

Sound familiar?

Common Hotjar problems we fix

The Hotjar problems that bring people to us, and what you have once each one is fixed.

Hotjar blocked by CSP

Script will not load in production

A Content Security Policy that allows the main site's scripts but not the Hotjar CDN, or a nonce-only policy that the inline snippet cannot satisfy. Recordings show nothing.

Script loading with CSP intact

SPA route change not tracked

Heatmaps aggregate across different pages

A React or Vue app whose URL changes but whose Hotjar instance does not know the virtual page changed. Clicks from three layouts land on one heatmap.

Virtual pageviews fire on every route

Consent not granted

Most visitors are not being tracked

A consent banner that defaults to deny, or a region (EU, UK) where deny is required by law. The recordings you see are a small, self-selected minority of real traffic.

Sample representative of real users

Daily session quota approaching limit

Session quota burns out mid-month

A campaign landing page that suddenly drew more traffic than expected, or an internal tool left in a test loop. The last two weeks of the month have no recording coverage.

Quota matched to the real traffic

Masking rule matched 0 elements

PII shows up in replay

A form field that was renamed or added after the masking rule was written. Session replay captures credit card numbers, SSNs or free-text PII in clear.

Masking rules keep up with the forms

Survey trigger did not fire

On-page surveys never appear

A trigger based on an element that is unmounted before the delay completes, or a target page the user never actually reaches. The survey has zero responses and looks broken.

Surveys firing on the right moment

Recording stopped on cross-origin navigation

Checkout steps vanish from the session

A payment or booking step hosted on a different domain, which Hotjar cannot follow across. The session reads like the user gave up at step two.

Journey visible across all steps where possible

Sampling rate dropped to 10%

High-traffic days are mostly unrecorded

The plan ceiling kicked in and Hotjar switched to a lower sampling rate without an obvious warning. Comparisons between weeks are suddenly not apples to apples.

Sampling policy understood and planned

What we do

Hotjar help, from one missing recording to the whole setup

Ask us about one empty heatmap, or let us look after the full behavior stack.

Rescue
Recordings not loading, consent blocking everything, or quota exhausted a week in. We get the sample back to representative and the dashboards back to usable.
SPA and consent integration
Virtual pageviews wired to the router, consent gating that distinguishes essential from analytics, and masking rules audited against the current form fields.
Research workflows
Survey triggers aligned to real user moments, feedback widgets that do not collide with support chat, and tagging so recordings can be found when a researcher needs them.
Quota and sampling
Plan sized against the last 90 days of real traffic, exclusion rules on internal and bot traffic, and alerts before the ceiling is reached rather than after.
Migrations
Moving in from FullStory, LogRocket, Mouseflow or Microsoft Clarity, with equivalent research artifacts rebuilt rather than exported raw.
Managed Tech
Masking rules reviewed, SPA integration tested after each release, quota watched, and an engineer available when a campaign spike burns out the plan at the wrong time.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Hotjar alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Hotjar questions

Something else? Call+1 737 727 7327

Why am I missing so many Hotjar recordings?

The three common causes are a consent banner that defaults to deny analytics, a Content Security Policy that blocks the Hotjar script, and ad-blockers that strip the tag in the browser. We check which of those is biting and either widen the CSP, adjust the consent flow where it is legal, or accept that the sample is biased and document the caveat.

How do I make Hotjar track pages in a single-page app?

The tag fires on the initial load, but client-side route changes are invisible unless you explicitly tell Hotjar. Calling hj('stateChange', url) on every router transition is the standard fix. Without it, every virtual page under the same URL path collapses into one heatmap, which is almost always not what you want.

Is Hotjar GDPR and CCPA compliant?

It can be, but compliance is a shared responsibility. Hotjar provides masking rules, consent flags, and an EU data residency option. You still have to gate the tag behind consent in the right regions, mask sensitive form fields explicitly, and keep the privacy policy accurate about what is captured. We can audit the setup against the common pitfalls.

How does Hotjar compare to FullStory or Microsoft Clarity?

Clarity is free with unlimited sessions and basic replay and heatmaps, which makes it hard to beat on cost alone. FullStory is heavier and is pitched at enterprise with deeper search, segmentation and funnel tools. Hotjar sits in between with a friendly UI, surveys and feedback built in, and reasonable pricing for mid-market teams.

Can we keep Hotjar from capturing sensitive form fields?

Yes. Element-level masking, suppressed inputs, and the data-hj-suppress attribute let you hide specific fields from both heatmaps and recordings. The catch is that it only works for fields you remember to mask, so an audit after every release that adds forms is the best defence against drift.

How much does Hotjar help cost?

Our quote is free. Send over a sample recording URL that is empty, the current plan, and a snippet of the consent setup, and we return a price before writing any code.

Free estimate

Hotjar giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.