Crazy Egg
How to configure Crazy Egg 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
Overview
This guide explains how to implement different privacy configurations for Crazy Egg 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 Crazy Egg tracking script (heatmaps/snapshots, recordings, surveys, A/B testing). Crazy Egg, Inc. is a US company.
What the service does in this scope. The Crazy Egg pixel "only uses 1st party cookies" and records, among other things, whether a visitor is new or returning and the referrer. Visitors receive a UUID; "IP addresses of visitors are always anonymized before being stored"; keystroke data in all input fields is suppressed client-side. Additional elements can be masked and whole pages skipped in recordings. Advanced tracking options (Recording Identifier, Custom User Variables) can link recordings to known users. A GDPR DPA and SCCs are available on request.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Heatmaps and recordings with default suppression, sensitive elements masked and sensitive pages skipped; no advanced tracking options; after consent. |
| Configuration B — Higher risk | As A, plus Recording Identifier and Custom User Variables linking recordings to known users; after consent. |
No configuration without prior consent. A returning-visitor identifier is stored; no consent-free configuration is documented.
Step 1 — Configure Crazy Egg
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service |
| 2 | Masking | Recordings dashboard > Customize Recordings > Mask Elements | Mask sensitive elements | Default |
| 3 | Page skipping | Recordings settings (skip page / end recording) | Skip checkout and account pages | Not used |
| 4 | Advanced tracking options | Recording Identifier, Custom User Variables | Not used | Used |
| 5 | DPA / SCCs | Request by email | Concluded | Concluded |
| 6 | Loading | Consenter script blocking | After consent | After consent |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Crazy Egg, Inc. is a US company subject to the US CLOUD Act; the United States is listed as a processing and potential access location.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service | Improve the service |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers, Authentication-derived identifiers |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers, IP address anonymised, Aggregated site statistics | Browsing and interaction data, Device characteristics, Device identifiers, IP address anonymised, Authentication-derived identifiers, Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Not documented | Not documented |
| Processing location | United States | United States |
Privacy-policy follow-up
- Crazy Egg as processor; heatmaps and recordings; first-party cookies; masking; identification (B); US processing and potential access by US authorities.
Verification checklist
- No Crazy Egg requests before consent.
- Skipped pages produce no recordings.
- DPA and SCCs on file.
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