Tradedoubler
How to configure Tradedoubler 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, Receive marketing offers
Overview
This guide explains how to implement different privacy configurations for Tradedoubler affiliate conversion tracking on an advertiser website 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. Tradedoubler advertiser conversion tracking.
What the service does in this scope. First Party Cookie Validation stores a Tradedoubler Unique Identifier (TDUID) at client domain level. The integration handles cookie and tracking consent, can store a "Strictly Necessary ID" to support consented traffic such as cashback/reward partners, and can track events without cookies. Tag integrations pass a tracking_consent flag alongside the tduid. Tradedoubler describes its cookieless tracking as a device fingerprint without personally identifiable information. Cross Device Tracking matches devices deterministically using hashed user IDs (extid) and requires consent.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | First-party TDUID cookie only after Consenter consent; tracking_consent passed. |
| Configuration B — Higher risk | As A, plus cookieless (fingerprint) tracking and the Strictly Necessary ID for reward partners when consent is missing. |
| Configuration C — Higher risk | As A, plus Cross Device Tracking with hashed user IDs. |
⚠ Recommendation. Tradedoubler's "strictly necessary" ID and fingerprint-based cookieless tracking in B are vendor positions. Device fingerprinting reads information from the device under § 25 TDDDG. Have your DPO assess B before using it without consent.
Step 1 — Configure Tradedoubler
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk | Configuration C — Higher risk |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Support marketing analytics | Support marketing analytics; Receive marketing offers | Support marketing analytics; Receive marketing offers |
| 2 | First-party cookie (TDUID) | Conversion tracking script | After consent | After consent | After consent |
| 3 | Consent flag | tracking_consent | From Consenter | From Consenter | From Consenter |
| 4 | Cookieless / Strictly Necessary ID | Tradedoubler account | Off | On | Off |
| 5 | Cross Device Tracking | extid (hashed) | Off | Off | On |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Tradedoubler is a Swedish company; check its terms for US sub-processors and list the United States if present.
Legal role. Confirm the role (processor or joint controller) in your Tradedoubler advertiser agreement; the table uses Joint Controller as the network also processes for its publishers.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk | Configuration C — Higher risk |
|---|---|---|---|
| Processing purposes | Support marketing analytics | Support marketing analytics, Receive marketing offers | Support marketing analytics, Receive marketing offers |
| Tracking method | Third party tracking (crosssession, cross-website) | Third party tracking (crosssession, cross-website) | Third party tracking (cross-session, cross-website, cross-device) |
| Identifier | Device identifiers | Device identifiers, Probabilistic identifiers | Device identifiers, Authentication-derived identifiers |
| Data categories | Device identifiers, Browsing and interaction data, e-commerce Activity, Privacy choices | Device identifiers, Probabilistic identifiers, Device characteristics, IP address, Browsing and interaction data, e-commerce Activity, Privacy choices | Device identifiers, Authentication-derived identifiers, Browsing and interaction data, e-commerce Activity, Privacy choices |
| Legal role of data recipient | Joint Controller | Joint Controller | Joint Controller |
| Personalisation model | No personalisation | No personalisation | Profile based |
| Maximum storage duration | Per programme cookie period | Per programme cookie period | Per programme cookie period |
| Processing location | Sweden / EU | Sweden / EU | Sweden / EU |
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