The Trade Desk — server-side Conversion API export

The The Trade Desk integration now includes a Conversions Export job that sends server-side conversion events from a Lytics audience to The Trade Desk's Real-Time Conversion Events API. Use it to track page views against a universal pixel or to send user-interaction events (purchase, add-to-cart, etc.) against an event tracking tag.

How it works

• Pick a Lytics Audience and a Pixel / Event Tracking Tag ID, then choose the mode: leave Event Name empty to send page views (requires Advertiser ID and a Page URL Field), or set an event name to send user interactions (requires Merchant ID).
• Map at least one Lytics user field to a Trade Desk identifier type via Identifier Mapping. One identifier is sent per event, picked in TTD's recommended priority order: UID2, EUID, TDID, then a single device ID, then RampID. UID2 and EUID values must already be tokens — Lytics does not mint them.
• Optionally enrich events with Item Mapping (cart/product fields → items[]) and Custom Fields Mapping (td1–td10).
• Trigger conversions on audience enters, exits, or both — and optionally on changes to up to 75 user fields.
• Backfill the current audience on start with the Existing Users toggle.

What you need to do

• Create or reuse a Username and Password authorization for The Trade Desk; the Conversions Export uses the existing TTD userpass flow.
• Have your TTD universal pixel or event tracking tag ID, plus the Advertiser ID (page views) or Merchant ID (user interactions) provisioned in The Trade Desk.

See The Trade Desk for the full configuration walkthrough.