Tradedoubler provides a global affiliation network connecting businesses with customers. Using this destination you can implement server-side tracking using the same client-side parameters.
The Tradedoubler destination provides the following key features:
Events structure: our Events reference leverages Tradedoubler lead and sale tracking, meaning that your data is properly bridged to the expected fields in an optimized way.
Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.
Support for multi-item data: information included in the item array is bridged to Tradedoubler.
User identifier: you can openly select a user identifier field for logged users.
Organization Id
Required
Your organization identifier as provided by Tradedoubler.
Conversion Type
Required
The conversion type that is bound with your activity. This can be either Sale or Lead. If conversion type is Sale, only purchase events are sent to the partner, if it's Lead, only generate_lead events are forwarded to Tradedoubler.
Event Id
Required
The event identifier for the lead/sale taking place and as provided by Tradedoubler.
Cookie Name (tduid)
User Id Type
You can bridge your selected user identifier for logged users.
generate_lead
lead
purchase
sale
Organization Id
organization
Event Id
event
id
orderNumber
value
orderValue
currency
currency
coupon
voucher
user.email or user.id
extid [1]
(User Id Type)
exttype [2]
f1=items.X.product.id&
f2=items.X.product.name&
f3=items.X.product.price&
f4=items.X.quantity |
reportInfo [3]
[1] Hashed usingSHA-256and default value:user.email
[2] Either1or0, depending if your selectedUser Id TypeisUser EmailorUser Id respectively.
[3] It takes into account each product.
Tradedoubler unique tracking identifier that is set in a cookie by the .