Heap
How to configure Heap at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Improve the service, Support marketing analytics
Overview
This guide explains how to implement different privacy configurations for Heap and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. The Heap web SDK (heap.js) with autocapture and optional Session Replay. Heap is part of the Contentsquare group; Heap's DPA includes SCCs for EU–US transfers.
What the service does in this scope. Heap autocaptures interactions and sets first-party cookies including _hp2_id.{APP_ID} (user cookie). By default, Heap identifies geolocation but does not capture the IP address; IP Autocapture and Geolocation Autocapture can be toggled. Target text capture can be disabled globally (setting or disableTextCapture), and elements can be ignored or attributes redacted. Session Replay inherits these settings.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | IP and geolocation autocapture off; text capture disabled; no Session Replay; no identify; after consent. |
| Configuration B — Higher risk | Geolocation on; text capture on; Session Replay; identify with user properties; after consent. |
No configuration without prior consent. _hp2_id persists a user identifier; no consent-free configuration is documented.
Step 1 — Configure Heap
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service; Support marketing analytics |
| 2 | IP Autocapture | Account > Manage > Privacy and Security | Off | Off (default) |
| 3 | Geolocation Autocapture | Same | Off | On |
| 4 | Target text capture | Privacy settings toggle or disableTextCapture | Disabled | Enabled |
| 5 | Element-level controls | heap-ignore, data-heap-redact-attributes | Sensitive elements | Sensitive elements |
| 6 | Session Replay | Session Replay settings | Off | On |
| 7 | Identify / user properties | heap.identify, addUserProperties | Not used | Used |
| 8 | Loading | Consenter script blocking | After consent | After consent |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Data transfers from the EU/EEA to the US are covered by SCCs in Heap's DPA. Heap's US entity can be required to disclose data in its possession, custody or control regardless of storage location.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service | Improve the service, Support marketing analytics |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers, Authentication-derived identifiers |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, Non-precise location data, Authentication-derived identifiers, Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Per contract | Per contract |
| Processing location | United States | United States |
Privacy-policy follow-up
- Heap as processor; autocapture; replay (B); identification (B); US transfer with SCCs; potential access by US authorities.
Verification checklist
- No
heapanalytics.comrequests or_hp2_*cookies before consent. - Privacy toggles match the configuration.
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on