# Heatmaps FAQs

> Answers to common questions about heatmaps including setup, privacy, HIPAA compliance, and troubleshooting.

Source: https://docs.oursprivacy.com/docs/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. Heatmaps are built for HIPAA-regulated workflows and covered by your Business Associate Agreement with Ours Privacy. No element text or user input is captured. Compliance also depends on how you configure tracking and consent.

***

### Do heatmaps work on authenticated (logged-in) pages?

Yes. The backdrop comes from a real session replay recording, so it works on any page your visitors reach, including pages behind login or personalization.

***

### What if there's no session replay for a page?

Confirm replays are being captured for that page and try another breakpoint or date range.

***

### Can I see which exact element got clicked, not just the area?

Yes. The detail view ranks the page's elements by click count alongside the visual overlay. Add [`data-heatmap-id`](https://docs.oursprivacy.com/docs/heatmaps/data-heatmap-id) to give important elements stable, readable names in that ranking and in exports. A safe `data-cta` token can also label a CTA when no heatmap id is present.

***

### Can I compare two heatmaps?

Yes. Use **Add comparison** to view two heatmaps, for example, this month versus last month.

***

### How do I export a heatmap?

Export from the detail view as a **CSV** (heatmap data, including element-level click counts) or a **PNG** image of the rendered view (backdrop plus overlay). Both reflect your active filters and date range.

***

### 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.

***

### Can I create separate heatmaps for pages that share a path?

Yes, by URL parameter. Use the **URL parameter** filter at the top of the Heatmaps pages list to narrow matching events to those carrying a chosen URL parameter (with an optional value). The list still groups pages by their base path, so the filter narrows the events behind a row rather than adding one row per parameter value.

***

### How long is heatmap data retained?

Heatmap data follows the same retention policy as your account's event data.

***

### What can I filter heatmaps by?

Filtering supports device type, date range, country, region, and browser. All overlay layers update together when you change a filter.

***

## Need Help?

Contact us at [support@oursprivacy.com](mailto:support@oursprivacy.com) with any questions about heatmaps.
