Hotjar Alternative: Click Insight Without Recording Everyone
Heatmaps and replays raise consent and weight problems. How click tracking on the visitor record covers most Hotjar use cases, privately.
Hotjar's pitch is seductive: watch real users struggle with your page, see where they click, fix what confuses them. The insight is real. The bill arrives in three currencies — a heavyweight script on every page, a consent obligation that recording tools cannot dodge, and the quiet creepiness of replaying strangers' sessions. The question worth asking is not 'Hotjar or nothing' but 'which of these insights survive being collected respectfully?'
What teams actually use Hotjar for
Strip away the feature list and three jobs remain:
- Where do people click — and not click — on key pages?
- What did the user who hit the bug or abandoned the funnel experience?
- Occasionally: polls and feedback widgets.
Job 1: click insight without the heat-blur
Heatmaps are aggregate click data with paint. The underlying question — which elements earn attention — is answered by click events tied to pages and elements, which Clycyo captures automatically in its 1.1 KB tracker. You see the click distribution per page, segmentable by source and device ('mobile visitors from ads never touch the secondary CTA' — try expressing that in a heatmap), without recording a single keystroke. The CTA tracking guide shows the deliberate version.
Job 2: forensics without the video
Most replay-watching is forensic: a user reported a bug, a payment failed, a funnel leaked — show me what happened. A per-visitor timeline answers this directly: the pages in order, the clicks, the load time of each view, and the JavaScript error at the exact moment things broke. It reads like a flight recorder instead of a surveillance tape — and because nothing sensitive is captured, no replay-consent gymnastics are required. Inspect real timelines in the live demo to see whether they cover your forensic needs; for most teams they do.
What you genuinely lose
- Pixel-precision scroll heat and mouse-movement visualization — if design research is your daily job, a dedicated session-recording tool (carefully configured, consent-gated) still earns its place. Our session replay explainer covers the trade-offs.
- On-page survey widgets — replace with a lightweight feedback form, tracked as an event.
The weight argument, in numbers
Recording scripts observe everything, so they cost accordingly — tens to hundreds of KB plus continuous main-thread work, a direct hit on INP and LCP. The irony writes itself: a UX tool that degrades UX. The curated alternative (clicks + errors + performance on the visitor record) costs 1.1 KB total.
If your Hotjar usage is jobs 1 and 2 — as it is for most product teams — the privacy-first version is not a compromise; it is the same insight with better hygiene, a faster site, and a free tier to prove it on.