Exposure Log Matching is available to Match Booster customers and must be enabled by Hightouch. to turn it on. Exposure Log Matching for The Trade Desk supports US Match Booster data only.
Overview
This page covers details specific to The Trade Desk. For how Exposure Log Matching works and how to set it up, see Exposure Log Matching overview and Set up Exposure Log Matching. The Trade Desk delivers exposure logs through REDS (Raw Event Data Stream). REDS records each consented impression and click, along with details such as the campaign, ad group, publisher, and location. Hightouch receives these logs as Curated REDS feeds. See The Trade Desk’s REDS documentation for more about REDS.Supported feeds
Each delivery covers one finished UTC day of logs and usually arrives the following UTC day. See Delivery and history.
Identifiers and how they match
Hightouch matches UID2s and mobile device IDs in REDS impressions, starting from the identifiers mapped in your model’s Match Booster configuration:
UID2 conversion is included with Match Booster, so you don’t need a separate UID2 agreement.
Cookie IDs from The Trade Desk aren’t matched, so those rows stay unmatched unless the row also has a matching identifier.
Request the feed
These are the details for step 2 of Set up Exposure Log Matching.- Contact your Trade Desk representative and ask them to send your REDS logs to Hightouch.
- Tell them which feeds you want: impressions alone, or impressions and clicks. Hightouch accepts the clicks feed only when the impressions feed is also set up.
- Provide your Partner ID and Advertiser ID.
Each model covers one advertiser feed, with its impressions and clicks together. To match logs for more than one advertiser to one model, ask your Trade Desk representative to combine those advertisers into one feed.
Columns
Matched logs use The Trade Desk’s Curated REDS columns, which differ from the public REDS schemas:- Impressions — Add advertiser, campaign, ad group, creative, audience, and contract names. They omit some public REDS columns, such as
UserAgent. - Clicks — Don’t include cookie, device advertising ID, or IP address columns.
IMPRESSIONID and DISPLAYIMPRESSIONID. Use LOGENTRYTIME as the timestamp column when you create an event model in Customer Studio.
Hightouch adds ID and IS_FIRST_PARTY_MATCH to every row. See Columns Hightouch adds.
Clicks take their match from impressions
Clicks don’t carry an identifier Hightouch can match, so each click takes itsID from the impression it came from. That’s why the clicks feed requires the impressions feed.
Each click row includes a DISPLAYIMPRESSIONID that identifies its impression. Hightouch joins it to IMPRESSIONID in the impressions feed. A click gets the impression’s ID when that impression is in the same day’s impressions log as the click, or the previous day’s. Clicks on older impressions stay unmatched.
Redacted identifier columns
COMBINEDIDENTIFIERon impressions — Hightouch keeps the value when it’s a device ID or cookie and the row is unmatched or matched from your own data. Every other value, including UID2s, is replaced withREDACTED.RAWURLon clicks — When a click matches only through the Match Booster identity graph, Hightouch replacesRAWURLwithREDACTED, because the URL contains a device ID. These rows haveIS_FIRST_PARTY_MATCHset toFALSE.
Example rows
These impressions show three kinds of rows: a first-party match, a Match Booster identity graph match, and an unmatched row. Values are illustrative, and most REDS columns are left out.
Each
ID is a 64-character SHA-256 hex digest, shortened here.
Limitations
- The Trade Desk keeps raw REDS logs for 90 days, so Hightouch can’t load days older than that.
- History starts on the date set during setup, and Hightouch doesn’t backfill logs from before it.
- Video view and conversion feeds aren’t supported. To request support, .