Integrations / Attribution
Tradedoubler
Server-side affiliate conversion tracking for Tradedoubler. Reports sales (Order Completed) to tbs.tradedoubler.com and leads (Lead Generated / Signed Up) to tbl.tradedoubler.com, attributing each conversion to the originating publisher via the persisted TDUID. Sends a SHA-256 hashed email as extid (exttype=1) for deterministic cross-device matching, and builds the pipe-delimited reportInfo product string from cart line items.
Datafly Signal delivers first-party events to Tradedoubler server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Tradedoubler expects.
Why route Tradedoubler through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Tradedoubler optimises against are not filtered by the browser.
Email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Tradedoubler receives match keys rather than raw personal data.
One consent decision governs every destination
Tradedoubler is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
generate_leadpurchasesign_upVertical presets
Retail. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Tradedoubler documentation.
Frequently asked questions
Does Datafly Signal integrate with Tradedoubler?
Yes. Datafly Signal delivers first-party events to Tradedoubler server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Tradedoubler expects. The integration is included in every deployment at no additional cost.
How is server-side Tradedoubler tracking different from the Tradedoubler tag?
The Tradedoubler tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Tradedoubler from your server, so delivery does not depend on browser conditions.
What personal data is sent to Tradedoubler?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so Tradedoubler receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Tradedoubler?
The blueprint ships with mappings for generate_lead, purchase, sign_up. Any event in your schema can be mapped to Tradedoubler through pipeline configuration without a code change.
Do I need to keep the Tradedoubler tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so Tradedoubler deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move Tradedoubler server-side?
See how Datafly Signal delivers first-party events to Tradedoubler from infrastructure you control, with hashed identity and consent enforcement built in.