The Trade Desk

the trade desk is a programmatic advertising platform for display, video, audio, and connected tv campaigns this destination loads the trade desk universal pixel javascript sdk in the browser and forwards page views, e commerce events, and conversion data for measurement and audience targeting there is no server side component getting started this is a device mode destination the trade desk universal pixel sdk is loaded automatically — no manual script installation is required you will need advertiser id — your trade desk advertiser id, found in your trade desk account universal pixel id — your trade desk universal pixel id, found in your trade desk account under pixels this pixel id fires on all page views and is also used as a fallback for any event below that does not have a dedicated pixel id per event pixel ids (optional) — trade desk allows advertisers to define dedicated pixel ids per conversion (add to cart, purchase, etc ) if you configure any of the per event pixel ids below, the corresponding event will fire against that pixel id instead of the universal pixel id purchase pixel id — used for order completed events (ttd purchase ) add to cart pixel id — used for product added events (ttd addtocart ) product viewed pixel id — used for product viewed events (ttd viewitem ) cart viewed pixel id — used for cart viewed events (ttd viewcart ) checkout started pixel id — used for checkout started events (ttd startcheckout ) add to wishlist pixel id — used for product added to wishlist events (ttd addtowishlist ) products searched pixel id — used for products searched events (ttd searchitem ) connecting to the trade desk pixel cdp destination warning 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 log into the chord data platform navigate to the cdp click the "add" button next to destinations select the trade desk pixel from the destination catalog enter the destination name, advertiser id , and universal pixel id optionally fill in any per event pixel ids you want to route separately click "create" to connect events event mapping all events include the ttd event name field, mapped from the cdp event name to a ttd predefined event name https //partner thetradedesk com/v3/portal/data/doc/trackingtagsevents#predefined item events every forwarded event also includes a pixelids array scoping the event to a single pixel id (the event specific pixel id when configured, otherwise the universal pixel id) chord event ttd event name pixel id used revenue data item data notes page sitevisit universal order completed purchase purchase → universal yes yes checkout started startcheckout checkout started → universal yes yes product added addtocart add to cart → universal yes product viewed viewitem product viewed → universal yes cart viewed viewcart cart viewed → universal yes product added to wishlist addtowishlist add to wishlist → universal yes products searched searchitem products searched → universal search query sent as td1 identify (not forwarded) — (other track events) (silently skipped) — the pixel id used column shows the resolution order for example, order completed fires against the purchase pixel id when configured, otherwise it falls back to the universal pixel id page events fires a conversion event with event name "sitevisit" , scoped to the universal pixel id ttd sdk call ttdconversionevents("event", { event name "sitevisit", pixelids \["\<universalpixelid>"] }) revenue data for purchase and startcheckout events, order level revenue data is included ttd attribute chord source (priority order) notes order id properties order id omitted if not present value properties total > properties revenue omitted if not present currency properties currency omitted if not present item data for events with product information, an items array is sent with item level detail multi product events ( order completed , cart viewed , checkout started ) map from properties products\[] single product events ( product added , product viewed , product added to wishlist ) extract from the event properties directly ttd item attribute chord source notes item code product id / sku / id required; products without an identifier are excluded name name defaults to empty string qty quantity defaults to 1 price price defaults to 0 cat category defaults to empty string products searched fires an event with event name "searchitem" if properties query is present, it is included as the td1 dynamic parameter unmapped events track events not listed above are silently skipped identify events are not forwarded initialization the plugin loads https //js adsrvr org/up loader 3 0 0 js and calls ttdconversionevents("init", { advertiserid, pixelids \[ ] }) , registering the universal pixel id together with every configured per event pixel id (de duplicated) each subsequent event call includes pixelids \[ ] so it fires against exactly one pixel id — the event specific one when configured, or the universal pixel id as a fallback 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 and processed after initialization completes 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 updated 15 apr 2026