Hotjar
Hotjar adds heatmaps, session recordings, and feedback polls to your site or app. You see where people click, scroll, and get stuck - and you can ask them questions in context. A free tier and simple script make it easy to add. This guide covers what Hotjar does well and how to use it without drowning in sessions.
Hotjar Tutorial: Heatmaps, Session Recordings, Surveys & User Attributes
Why hotjar fits product work
Core concepts that matter
Heatmaps
Click heatmaps show where users click (including non-links). Move heatmaps show where the cursor goes. Scroll heatmaps show how far people scroll. Use them to check if important content is seen, if CTAs get attention, and if layout matches behavior.
Session recordings
Recordings are replays of individual sessions. Filter by device, URL, country, or custom traits. Use them to investigate drop-off pages, confusing flows, or support tickets. Sample rather than watch everything - set a percentage or target key pages.
Hotjar Tutorial: How To Analyse Your Website User Behaviour
Feedback and surveys
Polls and surveys can be triggered by page, exit, or event. Keep them short (1–3 questions). Use for “what stopped you?” or “what would make this better?” - not for long questionnaires.
Privacy and sampling
Masking hides sensitive inputs and often PII. Sampling limits how many sessions you record or include in heatmaps. Set rules so you get useful signal without storing more than you need or hitting limits.
Practical habits
When hotjar isn’t the fit
Pricing (high level)
Free - Limited daily sessions, basic heatmaps and recordings. Enough to try it and use on a few pages.
Plus and above - More sessions, more heatmaps, advanced filters, feedback, support. Check Hotjar’s pricing for current plans.
Using Hotjar Heatmaps to improve website performance
Hotjar is a strong default when you want to see and hear users without running full studies. Use heatmaps and a small sample of recordings on important pages; add feedback where you need “why?”

