Tradedoubler

Datafly Signal reports sales to tbs.tradedoubler.com and leads to tbl.tradedoubler.com server-to-server, attributed by the TDUID click reference, with the hashed email for Tradedoubler’s cross-device tracking.

Prerequisites

Get your IDs

Tradedoubler supplies your organisation ID and the event IDs for sales and (if you report them) leads.

Keep the tduid on landing URLs

Tradedoubler links land with a tduid parameter, which the Datafly collector captures.

Configure in Signal

Configuration Fields

Field	Required	Description
`organization_id`	Yes	Your Tradedoubler advertiser organization ID. Supplied by Tradedoubler when your program is set up.
`sale_event_id`	Yes	The Tradedoubler event ID for sale conversions. Found in your Tradedoubler advertiser account under the program’s tracking events.
`lead_event_id`	No	The Tradedoubler event ID for lead conversions. Only required if you report leads (sign-ups, form submissions) in addition to sales.
`checksum`	No	Optional. Sent as the checksum parameter (blueprints from 0.7.0) only when set. Tradedoubler computes its fraud-protection checksum per transaction with an algorithm your Tradedoubler contact supplies, so a fixed value is only useful if Tradedoubler tells you to use one. Leave blank otherwise.

Management UI Setup

Go to Integrations > Add Integration > Tradedoubler.
Choose a preset: Default (default), Retail (ecommerce), Lead Generation (lead_gen), Insurance (insurance), Travel (travel).
Fill in the fields above and click Save.

Request format

A sale:

GET https://tbs.tradedoubler.com/report?cons=true&currency=GBP&event=51&event_time=2025-09-22+00%3A13%3A20&extid=86e0b9e56c17cc4d12387e1949b85053fbe73bc3ce5a1188713a9d300cc6133d&exttype=1&orderNumber=ORD-1001&orderValue=259.99&organization=1234567&reportInfo=f1%3DSKU_1%26f2%3DParka+Hood%26f3%3D120.00%26f4%3D2%7Cf1%3DSKU_2%26f2%3DGloves%26f3%3D19.99%26f4%3D1&tdEventName=sale&tduid=e0f15774d8d148963fd2df1bf9396d54&voucher=SAVE10

reportInfo carries the products (f1 ID, f2 name, f3 unit price, f4 quantity). Tradedoubler asks for it as the last parameter; Signal orders parameters alphabetically (#1516).

A lead:

GET https://tbl.tradedoubler.com/report?cons=true&event=52&event_time=2025-09-22+00%3A13%3A20&extid=86e0b9e56c17cc4d12387e1949b85053fbe73bc3ce5a1188713a9d300cc6133d&exttype=1&leadNumber=Q-77&organization=1234567&tduid=e0f15774d8d148963fd2df1bf9396d54

Event Mapping

Signal event	Vendor event	Presets
`purchase`	`sale`	Default, Retail, Insurance, Travel
`generate_lead`	`lead`	Default, Lead Generation, Insurance
`sign_up`	`lead`	Lead Generation
`quote_completed`	`lead`	Insurance
`booking_completed`	`sale`	Travel

Identity

tduid is required; conversions without it are not sent. extid is the SHA-256 of the normalised email with exttype=1. No plaintext personal data is sent.

cons=false is sent when the visitor refused marketing consent (Tradedoubler assumes consent when it is absent), and the hashed email is then not sent. Affiliate conversions are not held back for marketing consent: the affiliate who referred the visitor is paid through them (product decision, #1219). Operators whose legal advice differs can set the pipeline’s affiliate_click_ids_require_consent, or assign a consent category to the integration.

Troubleshooting

Problem	Solution
Leads not recorded	Set the Lead Event ID: lead events are not sent without it.
Checksum errors	Leave Checksum blank unless Tradedoubler gives you a value to send.

Blueprint

The Tradedoubler blueprint version is 0.7.0. It was last reviewed against the vendor’s documentation on 2026-09-23.