Why content may be missing

Heatmaps need a page background to place visitor interaction data in context. If the background page or screenshot is incomplete, the heatmap may show blank areas or missing sections.

Common causes include:

• page content requires login
• assets are blocked
• the page changed after data was recorded
• lazy-loaded content did not appear during capture
• consent or cookie banners changed the view
• the page blocks automated capture
• the selected device layout does not match the available background

Authenticated pages

Pages behind login can be difficult to capture because the heatmap background may not have access to authenticated content.

For private app pages, consider whether the page should be tracked at all. If it is tracked, make sure sensitive content is masked and that reports are safe to view.

Lazy-loaded sections

Some content loads only after scrolling or after a script runs. If that content is not present when the background is captured, it may be missing in the heatmap.

Check whether the missing section is lazy-loaded, personalized, or dependent on a third-party script.

Blocked assets

CSS, images, fonts, or scripts can be blocked by:

• Content Security Policy
• CORS settings
• hotlink protection
• private CDNs
• expired signed URLs
• bot protection

Open browser developer tools while viewing the heatmap to check for failed network requests.

Page changed after recording

If the website was redesigned after the data was collected, the current page background may not match older heatmap data.

Use a date range after the redesign or regenerate the report using current data where possible.

Troubleshooting checklist

• Confirm the page is publicly reachable.
• Check whether the page requires login.
• Check failed asset requests.
• Test the same device type.
• Review lazy-loaded content.
• Use a recent date range after major design changes.
• Confirm privacy masking is not hiding the whole page.