Mapp Intelligence (formerly Webtrekk)
How to configure Mapp Intelligence (formerly Webtrekk) 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 Mapp Intelligence and how to reflect them in the Consenter Manager. It covers the TPP entries "Mapp Intelligence Full Feature Tracking", "Mapp Intelligence Tag Integration", "Mapp" and the alias "Webtrekk".
- 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. Mapp Intelligence web tracking via the Smart Pixel, Tag Integration or tracking pixel v4/v5.
What the service does in this scope. Mapp Intelligence sets cookies beginning with wt (pixel v3–5) or wtstp (Smart Pixel); the Ever ID cookie (wt3_eid / wtstp_eid) identifies the end device for 6 months with first-party tracking, and the session cookie holds the current session. The Ever ID lifetime is configurable in months, or limited to the session by entering 0. Anonymous tracking prevents user-identifiable cookies (such as eid, sid) and suppresses query parameters that could contain identifiable data; anonymousOptIn makes anonymous tracking the default until the user opts in. In anonymised (cookieless) tracking, a fingerprint formed from IP address and user agent holds the current session together. User matching between Mapp Engage and Mapp Intelligence does not work while anonymous tracking is active.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Anonymous tracking with parameter suppression; after consent. |
| Configuration B — Higher risk | First-party Ever ID cookie (6 months); after consent. |
| Configuration C — Highest risk | As B, plus customer IDs and user matching with Mapp Engage; after consent. |
No configuration without prior consent. Even anonymous tracking forms a session fingerprint from IP and user agent, which involves reading information from the device. No consent-free configuration is documented.
Step 1 — Configure Mapp Intelligence
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk | Configuration C — Highest risk |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service; Support marketing analytics | Improve the service; Support marketing analytics; Receive personalised marketing offers |
| 2 | Anonymous tracking | Smart Pixel / Tag Integration: enableAnonymousFunction, anonymousOptIn, suppressParameter | On, with suppressed parameters | Off | Off |
| 3 | Ever ID lifetime | GDPR settings: lifetime in months (0 = session) | — | 6 months | 6 months |
| 4 | Customer IDs / user matching | Tracking parameters; Mapp Engage integration | Not used | Not used | Used |
| 5 | Opt-out cookie | GDPR settings (default webtrekkOptOut) | Configure | Configure | Configure |
| 6 | Loading | Consenter script blocking | After consent | After consent | After consent |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Mapp's parent company is US-based; check the hosting region in your contract. List the United States as a potential access location.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk | Configuration C — Highest risk |
|---|---|---|---|
| Processing purposes | Improve the service | Improve the service, Support marketing analytics | Improve the service, Support marketing analytics, Receive personalised marketing offers |
| Tracking method | First party tracking (single session) | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Probabilistic identifiers, IP address | Device identifiers, IP address | Device identifiers, IP address, Authentication-derived identifiers |
| Data categories | Browsing and interaction data, Device characteristics, IP address, Probabilistic identifiers, Aggregated site statistics | Browsing and interaction data, Device characteristics, Device identifiers, IP address, Aggregated site statistics | As B, plus Authentication-derived identifiers, Users' profiles, e-commerce Activity |
| Legal role of data recipient | Processor | Processor | Processor |
| Personalisation model | No personalisation | No personalisation | Profile based |
| Maximum storage duration | Session | 6 months (cookie) | 6 months (cookie) |
| Processing location | Per contract; United States as potential access location | Same | Same |
Privacy-policy follow-up
- Mapp as processor; anonymous vs. cookie-based tracking; cookies and lifetimes; user matching (C); potential access by US authorities.
Verification checklist
- No Mapp requests before consent.
- A: no
eid/sidcookies; suppressed parameters absent from requests.
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