exactag
How to configure exactag at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Support marketing analytics
Overview
This guide explains how to implement exactag and how to reflect it in the Consenter Manager.
- Configure the third-party service.
- Map the configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configuration is a comparative example, not a guarantee of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. exactag marketing attribution tracking on an advertiser's website.
What the service does in this scope. exactag collects data with cookies and processes it for measuring advertising and content performance, which it lists as consent-based purposes. Results can be pushed to publishers ("Attribution Push"), for Google Ads via offline conversions. Users can object with an optout cookie set by exactag.com.
Simplified format. exactag's public documentation does not describe privacy settings the operator can change (such as IP truncation or retention). The guide uses a single fixed-behaviour configuration.
Step 1 — Configure exactag
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Support marketing analytics |
| Loading | Blocked by Consenter until consent (exactag lists these purposes as consent-based) |
| Tracking technology | Cookies |
| Opt-out | optout cookie on exactag.com |
| Attribution Push to ad platforms | Contractual option; if used, the receiving platform needs its own entry |
| Retention / IP handling | Not documented — request from exactag |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Support marketing analytics | Attribution of conversions to channels. |
| Tracking method | First party tracking (cross-session) | Cookies on tracking subdomains of the customer domain (for example et.<customer domain>). Verify in the browser. |
| Identifier | Device identifiers, IP address | Cookie ID; IP with each request. |
| Data categories | Browsing and interaction data, Device identifiers, Device characteristics, IP address, e-commerce Activity | Customer journey and conversion data. |
| Legal role of data recipient | Processor | Verify against your contract with exactag. |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Not documented | — |
| Processing location | Per contract | exactag is a German company; check sub-processors for US providers. |
Privacy-policy follow-up
- exactag as recipient; attribution purpose; cookies; opt-out cookie; Attribution Push recipients.
Verification checklist
- No exactag requests before consent.
- Contract confirms role, retention and sub-processors.
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