Heatmaps FAQs
Answers to common questions about heatmaps including setup, privacy, HIPAA compliance, and troubleshooting.
Heatmaps FAQs
Do I need to install anything extra?
No. Heatmaps activate automatically when session replay is configured. No additional scripts or setup needed.
Does it slow down my site?
No. Heatmap events are lightweight and batched with your existing events. No additional network requests are made.
Are heatmaps HIPAA-compliant?
Yes. No element text or user input is captured. All data flows through your first-party domain.
Do heatmaps work on authenticated (logged-in) pages?
Yes. The page background comes from a real session replay recording, so it works on any page your users visit — including pages behind login or personalization.
What's the difference between a rage click and a dead click?
A rage click highlights a burst of repeated clicks in the same area over a short period. It can point to frustration, hesitation, or a control that is slower or less clear than visitors expect.
A dead click highlights a click that did not produce an obvious on-page response. It can help you review confusing layouts or unclear affordances, especially when you confirm the behavior in session replays.
Do heatmaps work with single-page applications?
Yes. The SDK detects SPA route changes automatically. No configuration needed.
How long is heatmap data retained?
Heatmap data follows the same retention policy as your account's event data.
Do heatmap events count toward my event volume?
Yes. Heatmap events count toward your event quota like any other event.
Can I filter by traffic source?
Not yet. Filtering supports device type, date range, country, region, and browser. Traffic source filtering is planned.
Need Help?
Contact us at support@oursprivacy.com with any questions about heatmaps.
How is this guide?