Skip to content

Commit 329f685

Browse files
authored
Merge pull request #5057 from segmentio/maryam-ttd-docs
The Trade Desk Documentation
2 parents 4c93657 + 3cbaaa0 commit 329f685

File tree

1 file changed

+62
-0
lines changed
  • src/connections/destinations/catalog/actions-the-trade-desk-crm

1 file changed

+62
-0
lines changed
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
title: The Trade Desk CRM Destination
3+
hide-personas-partial: true
4+
hide-boilerplate: true
5+
hide-dossier: false
6+
beta: true
7+
id: 6440068936c4fb9f699b0645
8+
---
9+
10+
11+
The [Trade Desk](https://www.thetradedesk.com/us){:target="_blank"} gives companies and their partners the power to activate data into their robust data market, making it easy to discover, create and reach valuable audiences. Segment's integration with the Trade Desk lets you push first party user data from audiences created in [Twilio Engage](https://www.twilio.com/en-us/engage){:target="_blank"} to The Trade Desk platform to target brand’s first-party audiences more effectively.
12+
13+
This integration will allow users to connect their Engage Audiences to The Trade Desk and send PII, including email and hashed email. Users will be able to configure their delivery preferences within Segment.
14+
15+
The [Trade Desk](https://www.thetradedesk.com/us){:target="_blank"} destination can be connected to **Twilio Engage sources only**.
16+
17+
## Getting started
18+
19+
### Credentials from The Trade Desk
20+
21+
> info ""
22+
> Before you can activate audiences to The Trade Desk, you must contact your The Trade Desk account manager to sign the UID POC contract. The Trade Desk will then give permission, share your advertiser ID, and secret key to configure your destination.
23+
24+
To add the The Trade Desk CRM destination:
25+
26+
1. Generate a [long lived token](https://partner.thetradedesk.com/v3/portal/api/doc/Authentication#ui-method-create){:target="_blank"} on [The Trade Desk's Developer Portal](https://api.thetradedesk.com/v3/tokens){:target="_blank"}.
27+
2. From the Segment web app, navigate to **Engage > Audiences**. Ensure you are in the Engage space you plan to use with The Trade Desk. Either choose an existing Engage Audience or create a new one. This is the audience you plan to send to The Trade Desk.
28+
3. Within the audience, click **Settings** and copy the audience key. You'll need this key later.
29+
4. Navigate to **Engage > Engage Settings** and click **Destinations**. Ensure you are still in the correct Engage space.
30+
5. Search for **The Trade Desk CRM** and select the destination.
31+
6. Click **Configure The Trade Desk CRM**.
32+
7. On the **Select Source** screen, your Engage space should already be selected as the source. Click **Confirm Source**.
33+
8. Once authenticated, input your Authentication Token and Advertiser ID from your [The Trade Desk's CRM Data Platform API](https://api.thetradedesk.com/v3/portal/data/doc/DataIntegrateCRMData){:target="_blank"} account. Toggle **Enable Destination** on and click **Save Changes**.
34+
9. Navigate to the **Mappings** tab, click **New Mapping**, and select **Sync Audience to CRM Data Segment**.
35+
10. Under **Select mappings**, input the name of the Trade Desk Data Segment you want to sync to. If you don't have a segment with that name in your Trade Desk Account, then Segment will create one for you. Input the Region and PII Type and do not change any other defaults. Click **Save** and toggle to enable the mapping.
36+
- Only create one mapping for every destination.
37+
11. Navigate back to **Engage > Audiences** and click on the Audience from Step 1.
38+
12. Click **Add Destinations** and select The Trade Desk CRM destination you just created. In the settings that appear in the side panel, toggle the **Send Track** option on and do **not** change the Audience Entered/Audience Exited event names. Click **Save Settings**.
39+
40+
Setup is now complete and the audience will start syncing to The Trade Desk.
41+
42+
To sync additional Audiences from your Engage space, create a separate mapping in The Trade Desk destination. Navigate to **Connections > Destinations**, search for and select The Trade Desk destination, and follow Steps 9-11 above.
43+
44+
{% include components/actions-fields.html settings="true"%}
45+
46+
47+
### Limitations
48+
49+
1. The Trade Desk requires a minimum of 1500 distinct IDs with each batch upload, so audiences must have at least 1500 unique users.
50+
2. Segment performs audience syncs to The Trade Desk every 24 hours.
51+
3. The Trade Desk lets you have multiple CRM Data Segments with the same name. If you are trying to sync to a Trade Desk Data Segment that is a duplicate, your Segment events will fail.
52+
53+
### FAQs
54+
55+
1. **How does TTD handle emails that don't already exist?**
56+
57+
The CRM endpoint maps email addresses into UID2s. If it's a valid email address, TTD will always generate a UID2 for it. However, if there are no bid requests coming in from the SSP with the specific UID2, then the ID would exist in the segment until it hits the TTL and won't be used when purchasing an impression.
58+
59+
2. **What PII format should I send?**
60+
61+
Segment recommends transmitting personally identifiable information (**PII**) in its original, non-hashed format. TTD's preference is to handle the hashing of the data on their end.
62+

0 commit comments

Comments
 (0)