Hotjar Heatmap Not Collecting Data: How to Troubleshoot It
When a Hotjar heatmap is not collecting data, the heatmap stays empty or never reaches enough sessions. The cause is usually the page URL targeting, traffic volume, dynamic page behavior, consent or a website update. Heatmaps need a specific page target and enough matching sessions, so confirm both before assuming the heatmap is broken.
Table of Contents
- 01.What a heatmap needs to collect
- 02.What to check first
- 03.The page URL and targeting
- 04.Traffic and session count
- 05.Dynamic pages and single-page applications
- 06.Consent and website updates
- 07.How to test the fix
- 08.How to validate the final result
What a heatmap needs to collect
A heatmap collects data for a specific page target. It needs the tracking code to load, the page URL to match the target, enough matching sessions to build the heatmap and consent where applicable. When a heatmap stays empty, one of those conditions is not met. The page target and the session count are the two most common causes.
| Cause | What happens | How to check |
|---|---|---|
| Wrong page URL | Page does not match the target | Compare the live URL with the heatmap target |
| Low traffic | Not enough sessions yet | Check traffic to the page |
| Dynamic page | URL or content changes | Check for query parameters or SPA behavior |
| Consent | Sessions not eligible | Check consent state |
| Tracking missing | No data at all | Confirm the tracking code loads |
What to check first
- Compare the exact live page URL with the heatmap page target.
- Check the traffic volume to the page over the collection period.
- Confirm the tracking code loads on the page.
- Check the consent state for the sessions you expect.
- Confirm whether the page is dynamic or uses query parameters.
The page URL and targeting
A heatmap targets a specific page URL. If the live URL does not match the target, the heatmap collects nothing. The match can fail because of a trailing slash, a query parameter, a subdomain or a URL change. Compare the exact URL in the browser address bar with the heatmap target. Use the targeting rules to match the URL correctly, including or excluding query parameters as needed. Page targeting problems are covered in the guide on Hotjar tracking wrong pages.
Traffic and session count
A heatmap needs enough matching sessions to build a useful picture. A low-traffic page may take a long time to collect enough data. Check the traffic to the page over the collection period. If the page gets few visits, the heatmap will be sparse or empty. This is not a tracking problem, it is a traffic problem. Do not invent a specific session threshold, because the needed count depends on the page and the heatmap type.
Dynamic pages and single-page applications
Dynamic pages and single-page applications can break heatmap collection. A page that loads content dynamically may change without a URL change, which can confuse the heatmap. A single-page application that updates the URL through routing may not trigger a new page view in the way the heatmap expects. Confirm how the page behaves and whether the heatmap target matches the actual URL the user sees.
Consent and website updates
Consent affects heatmap collection the same way it affects recordings. Sessions without consent are not captured. A website update can also break a heatmap if it changes the page URL, removes the tracking code or changes the page structure. If the heatmap stopped collecting after a site change, check the code and the page. Tracking installation is covered in the guide on Hotjar tracking not working.
How to test the fix
- 1.Confirm the live page URL matches the heatmap target exactly.
- 2.Confirm the tracking code loads on the page.
- 3.Grant consent where applicable and visit the page in a new session.
- 4.Allow time for the session to be captured and added to the heatmap.
How to validate the final result
The heatmap is collecting when new sessions are added after the fix and the click and scroll data builds over time. If the URL matches and the code loads but the heatmap stays empty, traffic volume is the likely cause. If the page is dynamic, confirm the heatmap target matches the URL the user actually sees.
Frequently Asked Questions
Why is my Hotjar heatmap not collecting data?
The page URL may not match the heatmap target, the page may have low traffic or the tracking code may not load. Compare the exact live URL with the target, check the traffic volume and confirm the code loads. A low-traffic page takes longer to collect enough sessions.
How many sessions does a Hotjar heatmap need?
It depends on the page and the heatmap type. There is no universal threshold. A low-traffic page takes longer to collect enough data. Check the traffic to the page over the collection period rather than assuming a fixed session count.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Hotjar Tracking Not Working: What to Check First
When Hotjar tracking does not work, the cause is the tracking code, page coverage, consent, a website change or browser behavior. Confirm the code is present and loading before debugging anything deeper.
Hotjar Is Tracking the Wrong Pages: How to Fix Page Targeting Problems
Wrong page tracking comes from URL targeting rules, query parameters, dynamic URLs or SPA behavior. Compare the rules with the actual URLs the site uses to find the mismatch.
Hotjar Recordings Not Showing: Common Tracking and Session Problems
Recordings can be missing even when tracking is installed, because of consent, sampling, page targeting or browser restrictions. Distinguish a tracking problem from a capture problem first.