You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-the-trade-desk-crm/index.md
+39-36Lines changed: 39 additions & 36 deletions
Original file line number
Diff line number
Diff line change
@@ -7,62 +7,65 @@ beta: true
7
7
id: 6440068936c4fb9f699b0645
8
8
---
9
9
10
+
[The Trade Desk](https://www.thetradedesk.com/us){:target="_blank"} empowers companies and their partners to leverage data in their expansive data marketplace, facilitating seamless discovery, creation, and engagement with valuable audiences. Segment's integration with The Trade Desk allows you to 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, enhancing targeted reach to brand's first-party audiences.
10
11
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
+
This integration enables users to effortlessly link their Engage Audiences to The Trade Desk and transmit Personally Identifiable Information (PII), including email addresses and hashed emails. Users have the flexibility to configure their delivery preferences within Segment.
12
13
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
+
> info ""
15
+
> The Trade Desk destination can only be connected to Twilio Engage sources.
14
16
15
-
The [Trade Desk](https://www.thetradedesk.com/us){:target="_blank"} destination can be connected to **Twilio Engage sources only**.
17
+
## Getting Started
16
18
17
-
##Getting started
19
+
### Obtaining Credentials from The Trade Desk
18
20
19
-
### Credentials from The Trade Desk
21
+
> info ""
22
+
> Before activating audiences on The Trade Desk, contact your The Trade Desk account manager to sign the UID POC contract. Following this, The Trade Desk will grant permission and share your advertiser ID and secret key for configuring your destination.
20
23
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.
24
+
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"}.
23
25
24
-
To add the The Trade Desk CRM destination:
26
+
### Connecting The Trade Desk CRM
25
27
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**.
28
+
1. Go to the Segment web app and navigate to **Engage > Audiences**. Ensure you are in the Engage space you intend to use with The Trade Desk. Choose an existing Engage Audience or create a new one. This is the audience you plan to send to The Trade Desk.
29
+
2. Access **Engage > Engage Settings** and click on **Destinations**. Confirm that you are in the correct Engage space.
30
+
3. Search for **The Trade Desk CRM** and select the destination.
31
+
4. Click on **Configure The Trade Desk CRM**.
32
+
5. On the **Select Source** screen, your Engage space should already be selected as the source. Click on **Confirm Source**.
33
+
6. Once authenticated, enter 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. Enable the destination by toggling **Enable Destination** and click **Save Changes**.
34
+
7. Navigate to the **Mappings** tab, click **New Mapping**, and choose **Sync Audience to CRM Data Segment**.
35
+
8. In the **Select mappings** section, input the PII Type and maintain other defaults. Click **Save** and toggle to enable the mapping.
36
+
- If you see a field labeled "Segment Name," please input the same name as the audience you have connected the destination to. Ensure that there is no existing segment in TTD with the identical name. Additionally, fill out the "Region" field with the geographical region of the CRM data segment, based on the origin of the PII.
37
+
-_**Create only one mapping for every instance.**_
38
+
9. Return to **Engage > Audiences** and select the Audience from Step 1.
39
+
10. Click **Add Destinations** and choose The Trade Desk CRM destination you just created. In the settings that appear in the side panel, enable the **Send Track** option and **do not** alter the Audience Entered/Audience Exited event names. If you missed providing the Segment Name and Region in step 8, please complete the Audience Settings, specifically the region field, with the geographical region of the CRM data segment based on the origin of the PII. Please note that the Public Beta only supports `US`. Click **Save Settings**.
39
40
40
-
Setup is now complete and the audience will start syncing to The Trade Desk.
41
+
Setup is now complete, and the audience starts syncing to The Trade Desk.
41
42
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
+
To sync additional Audiences from your Engage space, create a separate instance of The Trade Desk CRM Destination.
43
44
44
45
{% include components/actions-fields.html settings="true"%}
45
46
46
-
## Public Beta instructions
47
+
## Public Beta Instructions
47
48
48
-
* The Segment team will need to enable the feature for your Engage spaces.
49
-
* Once you agree to join the public beta, Segment will enable all Engage spaces that are part of your Segment workspace.
50
-
* New Engage spaces you create won't automatically be enrolled. Contact your Account Team/CSM to get these spaces enrolled.
49
+
* The Segment team needs to enable the feature for your Engage spaces.
50
+
* Once you agree to join the public beta, Segment enables all Engage spaces that are part of your Segment workspace.
51
+
* New Engage spaces you create won't be automatically enrolled. Contact your Account Team/CSM to get these spaces enrolled.
51
52
53
+
## Limitations
52
54
53
-
### Limitations
55
+
* An audience must have at least 1500 unique members; otherwise, the destination fails, and the data won't sync.
56
+
* Audience sync occurs once per day.
57
+
* Audience sync is a full sync.
54
58
55
-
1. The Trade Desk requires a minimum of 1500 distinct IDs with each batch upload, so audiences must have at least 1500 unique users.
56
-
2. Segment performs audience syncs to The Trade Desk every 24 hours.
57
-
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.
59
+
## FAQs
58
60
59
-
###FAQs
61
+
#### How is the CRM Segment Created?
60
62
61
-
1.**How does TTD handle emails that don't already exist?**
63
+
When connecting your audience from your Engage source to an enabled TTD destination, there's no need to manually create CRM Segments. Segment automatically generates a CRM Segment in your TTD account, mirroring the name of the audience linked to the TTD instance.
62
64
63
-
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.
65
+
#### How does TTD handle emails that don't already exist?
64
66
65
-
2.**What PII format should I send?**
67
+
The CRM endpoint maps email addresses into UID2s. If it's a valid email address, TTD generates 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.
66
68
67
-
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.
69
+
#### What PIIformat should I send?
68
70
71
+
The Trade Desk 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.
0 commit comments