Set up your bannerConfigure Your ToolsAnalytics

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.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. 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.

ConfigurationSummary
Configuration A — Medium riskIP and geolocation autocapture off; text capture disabled; no Session Replay; no identify; after consent.
Configuration B — Higher riskGeolocation 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 areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionImprove the serviceImprove the service; Support marketing analytics
2IP AutocaptureAccount > Manage > Privacy and SecurityOffOff (default)
3Geolocation AutocaptureSameOffOn
4Target text capturePrivacy settings toggle or disableTextCaptureDisabledEnabled
5Element-level controlsheap-ignore, data-heap-redact-attributesSensitive elementsSensitive elements
6Session ReplaySession Replay settingsOffOn
7Identify / user propertiesheap.identify, addUserPropertiesNot usedUsed
8LoadingConsenter script blockingAfter consentAfter 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 fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesImprove the serviceImprove the service, Support marketing analytics
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiersDevice identifiers, Authentication-derived identifiers
Data categoriesAggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiersAggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, Non-precise location data, Authentication-derived identifiers, Users' profiles
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationNo personalisation
Maximum storage durationPer contractPer contract
Processing locationUnited StatesUnited 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.com requests 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

On this page