OrcLink
← Help Center

Ad platforms

The Trade Desk conversions

Coming soon. The Trade Desk: not available yet. OrcLink would match only on the click (impression) id carried in the landing URL, never on TDID or other cross-site ids, and it cannot store that id yet; the API format is not public.

Coming soonComing soon: The Trade Desk: not available yet. OrcLink would match only on the click (impression) id carried in the landing URL, never on TDID or other cross-site ids, and it cannot store that id yet; the API format is not public.

Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.

How to connect

  • Not available yet: the destination cannot be switched on and no test can be sent.

What OrcLink reads

  • Ad cost: upload a CSV in Conversions > Ad costs (platform column "ttd"). Cost days are the ad account's calendar days (in the ad account's time zone); conversion and outcome days are UTC days. Near midnight, a cost and its conversions can be on different days.

What OrcLink writes back

  • Conversions for the stages you set to relay (Outcomes > Stages), each with its click id and the hashed email and phone the platform matches on. Each batch waits for approval when approval is on (the default).

Never stored

  • Raw email or phone: only hashes leave OrcLink.
  • Page paths, page titles, referrers and IP addresses: never sent to an ad platform.

Known limits

  • The Trade Desk cost: upload a CSV in Ad costs (platform column "ttd").
  • The Trade Desk: not available yet. OrcLink would match only on the click (impression) id carried in the landing URL, never on TDID or other cross-site ids, and it cannot store that id yet; the API format is not public.

The adapter is built (Real-Time Conversion Events API, shape from Tealium and RudderStack docs; The Trade Desk's portal is behind a login; UNVERIFIED) and never sends.

  • OrcLink would match on the click (impression) id carried in the landing URL only. It never captures, stores or sends TDID, UID2, EUID or device ids.
  • Match-rate loss: The Trade Desk attributes mostly by TDID / UID2, and most programmatic display and CTV conversions are view-through or cross-device. Click-id-only matching sees only conversions that followed a click on the same browser with the id in the click URL: a small share of what The Trade Desk's own pixel reports; CTV conversions never match.
  • Blocked until: the impression id has a database column, and the request format and click macro are confirmed with The Trade Desk.
  • Health, legal and financial workspaces, and every workspace in HIPAA mode: blocked.

Cost: CSV upload only (platform ttd), see csv-cost.md.