> ## Documentation Index > Fetch the complete documentation index at: https://docs.hightouch.com/llms.txt > Use this file to discover all available pages before exploring further. # Exposure Log Matching for The Trade Desk > Match The Trade Desk's REDS impression and click logs to your own customer or household IDs, and receive them in your warehouse every day. > [!NOTE] > > Exposure Log Matching is available to [Match Booster](https://docs.hightouch.com/match-booster/overview) customers and must be enabled by Hightouch. [Contact us](#pylon-chat) 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](https://docs.hightouch.com/exposure-log-matching/overview) and [Set up Exposure Log Matching](https://docs.hightouch.com/exposure-log-matching/setup.md). 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](https://open.thetradedesk.com/advertiser/docsApp/GuidesAdvertiser/reds/doc/REDSGeneralInfo) for more about REDS. ## Supported feeds | Feed | Status | | - | - | | [Impressions](https://open.thetradedesk.com/advertiser/docsApp/GuidesAdvertiser/reds/doc/Impressions) | Supported | | [Clicks](https://open.thetradedesk.com/advertiser/docsApp/GuidesAdvertiser/reds/doc/Clicks) | Supported. Requires the impressions feed. | | Video views | Not supported | | Conversions | Not supported | Each delivery covers one finished UTC day of logs and usually arrives the following UTC day. See [Delivery and history](https://docs.hightouch.com/exposure-log-matching/output-reference.md#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: | Identifier | How Hightouch matches it | | - | - | | UID2 | Hightouch converts your Email, Email SHA256, Phone, and Phone SHA256 columns to UID2s with the UID2 identity service, then adds UID2s from the Match Booster identity graph. | | Mobile device ID | Your Mobile ID columns, then the Match Booster identity graph. | 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](https://docs.hightouch.com/exposure-log-matching/setup.md). 1. Contact your Trade Desk representative and ask them to send your REDS logs to Hightouch. 2. 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. 3. Provide your Partner ID and Advertiser ID. | ID | What it identifies | Where to find it in The Trade Desk | | - | - | - | | **Partner ID** | Your organization | **Preferences > Partner Info** | | **Advertiser ID** | The advertiser whose logs you want | **Advertiser Preferences > Seat Identifiers & Keys** | 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. Column names are uppercase in your warehouse, for example `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](https://docs.hightouch.com/exposure-log-matching/output-reference.md#columns-hightouch-adds). ### Clicks take their match from impressions Clicks don't carry an identifier Hightouch can match, so each click takes its `ID` 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 * **`COMBINEDIDENTIFIER` on 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 with `REDACTED`. * **`RAWURL` on clicks** — When a click matches only through the Match Booster identity graph, Hightouch replaces `RAWURL` with `REDACTED`, because the URL contains a device ID. These rows have `IS_FIRST_PARTY_MATCH` set to `FALSE`. ## 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. | ID | IS\_FIRST\_PARTY\_MATCH | LOGENTRYTIME | IMPRESSIONID | CAMPAIGNID | | - | - | - | - | - | | `220c2ca8...358d1a6c` | `TRUE` | 2026-06-01 14:03:22 | `8f2c1a7e-4b9d-4c1e-9a3f-1d2e3f4a5b6c` | `cmp7x2k` | | `c095b57f...18652f9c` | `FALSE` | 2026-06-01 14:05:47 | `3b7d9e21-6c4a-4f8b-b2d1-7e8f9a0b1c2d` | `cmp7x2k` | | null | null | 2026-06-01 14:06:10 | `c41a6f83-2e5b-4d9c-8f7a-0b1c2d3e4f5a` | `cmp4m8r` | 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, [contact us](#pylon-chat).