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
Running Hotjar?
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.
What it is
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.
The honest version
No technology is all upside. This is where Hotjar earns its place and where it tends to cause trouble.
Sound familiar?
The Hotjar problems that bring people to us, and what you have once each one is fixed.
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
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
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
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
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
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
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
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
Ask us about one empty heatmap, or let us look after the full behavior stack.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
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
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: