The Trade Desk

overview the trade desk cdp destination allows you to send first party event data from your store directly to your trade desk account this enables precise audience targeting, better campaign optimization, and improved return on ad spend (roas) across programmatic channels chord’s integration helps brands activate meaningful customer signals — like purchases, views, and carts — within the trade desk to inform smarter bidding and retargeting strategies what this destination does once connected, chord will stream customer behavior and conversion events to the trade desk in real time power campaign targeting, suppression, and lookalike modeling enable seamless measurement and performance tracking based on first party data how to connect the trade desk before connecting destinations in the chord cdp, please verify with all destination owners that all non chord cdp configured destinations are disabled running external destinations alongside configured chord cdp destinations can result in duplicate events downstream set up your trade desk pixel before connecting chord, you’ll need to generate a trade desk pixel id log in to the trade desk navigate to pixels & trackers create or select your event pixel copy the pixel id — you’ll need this for the next step don’t have access? contact your trade desk account manager to request a pixel add the trade desk as a destination in chord cdp log into your chord dashboard go to cdp → destinations click add destination select the trade desk from the destination list paste your advertiser id and trade desk pixel id click create to activate the connection once saved, chord will begin forwarding supported events automatically events page fires an empty trade desk conversion event the trade desk uses url based mapping to classify page views, so no additional attributes are sent ttd sdk call ttdconversionevents("event", {}) track order completed fires a trade desk conversion event with order data ttd sdk call ttdconversionevents("event", eventdata) ttd attribute chord source (in priority order) notes order id order orderid > order id omitted if neither is present value order total > order value > order revenue omitted if no value is found currency order currency omitted if not present all other track events are silently skipped the trade desk uses url based mapping rather than event types for classification identify events are not forwarded to the trade desk initialization the plugin initializes by loading https //js adsrvr org/up loader 3 0 0 js and then calling ttdconversionevents("init", { advertiserid, pixelids \[pixelid] }) before the script loads, a queue ( ttdconversioneventslayer ) buffers any events the plugin manages sdk loading state ( fresh → loading → loaded / failed ) to prevent duplicate script loads concurrent events during loading are queued via a shared initialization promise if the script fails to load, subsequent events are silently dropped csp requirements if your site uses a content security policy, allow the following domains directive domain script src https //js adsrvr org connect src https //js adsrvr org best practices use clear audience naming conventions when building trade desk segments from chord events avoid duplicate pixel tracking — do not install trade desk pixels separately on site if chord is managing the connection confirm event data in event pixel logs within your trade desk account