The Trade Desk CRM Destination

The Trade Desk 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 to The Trade Desk platform, enhancing targeted reach to brand’s first-party audiences.

This integration lets users link 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.

The Trade Desk destination can only be connected to Twilio Engage sources.

Getting started

Obtaining credentials from The Trade Desk

Before you begin, generate a long-lived token on The Trade Desk’s Developer Portal.

Connecting The Trade Desk CRM

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.
2. Access Engage > Engage Settings and click on Destinations. Confirm that you are in the correct Engage space.
3. Search for The Trade Desk CRM and select the destination.
4. Click on Configure The Trade Desk CRM.
5. On the Select Source screen, your Engage space should already be selected as the source. Click on Confirm Source.
6. Generate a long-lived token on The Trade Desk’s Developer Portal.
7. After authenticating, enter your Authentication Token and Advertiser ID from your The Trade Desk’s CRM Data Platform API account. Enable the destination by toggling Enable Destination and click Save Changes.
8. Navigate to the Mappings tab, click New Mapping, and choose Sync Audience to CRM Data Segment.
9. In the Select mappings section, input the PII Type and maintain other defaults. Click Save and toggle to enable the mapping.
   • Create only one mapping for every instance.
   • If any of the emails stored in your Engage audience are already in a hashed format, please specify the PII type as Hashed Email. Failure to do so results in The Trade Desk categorizing the hashed records as invalid during the ingestion process.
10. Return to Engage > Audiences and select the audience from Step 1.
11. 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. Fill out the audience settings, specifically the region field, with the geographical region of the CRM data segment based on the origin of the PII (US, EU, or APAC). Click Save Settings.

Setup is now complete, and the audience starts syncing to The Trade Desk.

To sync additional Audiences from your Engage space, create a separate instance of The Trade Desk CRM Destination.

Destination Settings

Available Actions

Build your own Mappings. Combine supported triggers with the following The Trade Desk Crm-supported actions:

• Sync Audience to CRM Data Segment

Sync Audience to CRM Data Segment

Drop users into the given CRM Data Segment

Sync Audience to CRM Data Segment is a Cloud action. The default Trigger is: event = "Audience Entered"

Click to show / hide fields

Limitations

• An audience must have at least 1500 unique members; otherwise, the destination fails, and the data won’t sync.
• Audience attempts to sync once per day.
• Audience sync is a full sync.

FAQs

How is the CRM Segment Created?

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.

How does TTD handle emails that don’t already exist?

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.

What PII format should I send?

The Trade Desk recommends transmitting personally identifiable information (PII) in its original, non-hashed format. TTD’s preference is to handle the hashing of any PII, like emails, on their end. However, if your data already contains any hashed emails, please ensure you are normalizing and hashing the emails by designating the PII type as Hashed Email, in line with TTD’s PII Normalization and Hash Encoding documentation.