Heatmaps visualise where visitors click, move, and scroll. Like any aggregate visualisation, they're only useful once you have enough samples to separate signal from noise. Below the minimum, a single visitor's behaviour can dominate the picture.
Rough thresholds
| Heatmap type | Minimum sessions for a usable read | Recommended for confident decisions |
|---|---|---|
| Click | 100 | 500+ |
| Scroll | 100 | 300+ |
| Movement | 200 | 1,000+ |
These are rough rules, not absolutes. A page with 200 clicks split across two clear hotspots gives you signal. A page with 200 clicks scattered across a hundred elements does not.
Why movement needs more data
Mouse-movement heatmaps record continuous coordinate streams, so per-session noise is much higher than a few discrete clicks. We typically wait for at least 200 sessions before showing a movement heatmap, and the pattern only sharpens up around 1,000 sessions.
What if my page doesn't reach the threshold?
If a page has fewer than ~50 sessions in your selected date range, the heatmap will display a banner: "Not enough data — collect more visits or expand the date range."
Options:
- Expand the date range — switch from 7 days to 30 days, or 30 days to 90 days (Pro plan retains 730 days of data).
- Group similar pages — use the URL pattern
/blog/*to combine all blog posts into a single heatmap. - Run a higher-traffic experiment — push the page through a campaign or A/B test to accumulate samples faster.
Reading a heatmap with low data
Even at 100–200 sessions, treat the heatmap as directional, not statistically significant:
- A clear cluster on a non-clickable element (e.g. a heading that looks like a button) is real and worth fixing.
- A single hot spot on an obscure element with 5 clicks is probably one engaged visitor, not a pattern.