Heatmaps and session recordings: what they show, what they miss
A new landing page goes live. Two weeks later, the team that built it sends a heatmap glowing red around your main call-to-action and a folder of session recordings. It looks like proof the page works.
But a colorful heatmap is easy to over-read, and a few recordings only show a slice of what really happened. Before you trust either one, it helps to know what these tools measure, and where they go quiet.
What heatmaps and session recordings are
Heatmaps squeeze the behavior of many visitors into one colored image. Click maps show where people tap, scroll maps show how far down the page they get, and move maps track where the cursor travels. Red means the most activity, while areas with no color went unseen.
Session recordings work differently. Each one replays a single visit, so you watch one person move through your site from arrival to exit. Used together, they answer a useful question: where do people get stuck?
What they show well
These tools are best at surfacing problems you would never spot in a traffic report. Repeated clicks on something that is not a button. A form plenty of people start but few finish. A key message sitting below where most visitors stop scrolling. That is real, observed behavior, not a survey of what people say they do.
What they miss
Here is the part most teams skip when they hand you the dashboard. Heatmaps show you what happened, never why. A button can collect a pile of clicks because it is popular, or because it is broken and people keep tapping in frustration. The color alone cannot tell those two stories apart.
They also need volume before they mean anything. A click or scroll map only becomes trustworthy once thousands of visits sit behind it. Nielsen Norman Group, a UX research firm, puts the floor for a rigorous lab study at around 30 participants, and a live website needs far more than that. A red blob built on a few dozen visits is decoration, not evidence.
Move maps carry a quieter catch, too: your mouse is not your eyes. People park the cursor in one spot while reading somewhere else, so a hot zone is a rough proxy for attention, not a record of it.
Session recordings raise one more issue worth saying out loud: privacy. They can capture whatever a visitor types, including personal and payment details, which creates real legal exposure if no one masks the recordings or collects proper consent. Any tool you commission should redact sensitive fields by default.
When to ask for them, and when to skip
Ask for heatmaps and recordings when you already have steady traffic and one specific page that is underperforming. They earn their keep on checkout flows, signup forms, and long landing pages, where small frictions cost real money. Planning a new site instead? Decide how you will measure behavior as part of the website design brief, not after launch.
Skip them when a page is brand new with barely any traffic, or when your real question is why rather than where. For the why, pair them with something qualitative: a few user interviews or one short usability test will explain in an afternoon what a month of recordings only hints at.
One thing worth knowing before you pay: many of these tools are free. Microsoft Clarity costs nothing, and most rivals offer a free tier. What you are really paying for is the analysis and the fixes, not the software itself. Paying someone to install and configure it is fair, especially if you are not technical, but it is a small one-time job. If most of the bill is setup rather than insight, ask what you are actually getting.
Questions to ask before you commission them
- Does this page get enough traffic for the data to mean anything?
- How are you masking personal and payment data in the recordings?
- Once you spot a problem, what is the plan to find out why?
The third answer matters most. Heatmaps and recordings are good at raising questions. They were never built to answer them, and the team you hire should be the first to tell you so.
If anyone sells you a tool as proof your site works, treat it as your cue to slow down. These are instruments, not verdicts. The teams worth working with know the difference, and they will show you where the data stops before you pay for the dashboard.