Mixpanel
How to configure Mixpanel 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 Mixpanel 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 Mixpanel JavaScript SDK (mixpanel-browser) on a website, including the optional session replay and heatmap features. Mixpanel, Inc. is a US company.
What the service does in this scope. The SDK tracks events and user properties and stores a distinct ID in a cookie or local storage (persistence). Mixpanel "does not store IP addresses" but uses them to assign geolocation properties on ingestion; geolocation can be disabled (ip: false / ip = 0). Users can be opted out by default with opt_out_tracking_by_default: true and opted in after consent. Projects can be created with EU Data Residency, which requires sending data to the EU ingestion host. Session replay (record_sessions_percent) and heatmap capture are optional init settings.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | EU Data Residency; geolocation disabled; opted out by default and opted in after consent; no session replay; no identification. |
| Configuration B — Higher risk | US project (default); geolocation on; session replay and heatmaps; identify with user IDs and profile properties; after consent. |
No configuration without prior consent. The SDK persists an identifier; no consent-free configuration is documented.
Step 1 — Configure Mixpanel
| # | 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 | Data residency | "EU Data Residency" when creating the project; api_host: "https://api-eu.mixpanel.com" | EU | US (default) |
| 3 | Consent gating | opt_out_tracking_by_default: true, then opt_in_tracking after consent | Yes | Yes |
| 4 | Geolocation / IP use | ip: false in config or ip = 0 per payload | Disabled | Enabled |
| 5 | Session replay and heatmaps | record_sessions_percent, record_heatmap_data | Off | On |
| 6 | Identification | identify, people properties | Not used | Used |
| 7 | Data retention | Data retention policy in project settings | Shortest suitable | Default |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Mixpanel, Inc. is a US company and can be required to disclose data in its possession, custody or control regardless of storage location. The United States is listed as a potential access location in all configurations.
| 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, IP address, 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, IP address, 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 retention policy | Per retention policy |
| Processing location | EU (Frankfurt); United States as potential access location | United States |
Privacy-policy follow-up
- Mixpanel as processor; events and identifiers; replay (B); residency; retention; potential access by US authorities.
Verification checklist
- No events sent before
opt_in_tracking. - A: requests go to
api-eu.mixpanel.com; no geolocation properties in events. - Withdrawal calls
opt_out_tracking.
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