(Beta) The Trade Desk - CRM connection
- If you source data in the EU, please use the The Trade Desk - CRM (EU) destination.
- If you source data in the APAC or NAMER regions, please use the The Trade Desk - CRM (NAMER & APAC) destination.
Overview overview
This document is designed to help you activate profiles to your Trade Desk account for audience targeting and suppression based on CRM data.
This connector sends data to the The Trade Desk first-party endpoint. The integration between ÃÛ¶¹ÊÓƵ Experience Platform and The Trade Desk does not support exporting data to the The Trade Desk third-party endpoint.
The Trade Desk(TTD) does not directly handle the upload file of email addresses at any time nor does The Trade Desk store your raw (unhashed) emails.
Prerequisites prerequisites
Before you can activate audiences to The Trade Desk, you must contact your The Trade Desk account manager to sign the CRM Onboarding contract. The Trade Desk will then give permission and share your advertiser ID to configure your destination.
ID Matching Requirements id-matching-requirements
Depending on the type of IDs that you ingest into ÃÛ¶¹ÊÓƵ Experience Platform, you must adhere to their corresponding requirements. Please read the Identity Namespace overview for more information.
Supported identities supported-identities
The Trade Desk supports the activation of identities described in the table below. Learn more about identities.
Both plain text and SHA256 hashed email addresses are supported by ÃÛ¶¹ÊÓƵ Experience Platform. Follow the instructions in the ID matching requirements section and use the appropriate namespaces for plain text and hashed email addresses, respectively.
email as the target identity when your source identity is an Email namespace or attribute.hashed_email as the target identity when your source identity is an Email_LC_SHA256 namespace or attribute.Email hashing requirements hashing-requirements
You can hash email addresses before ingesting them into ÃÛ¶¹ÊÓƵ Experience Platform or use raw email addresses.
To learn about ingesting email addresses in Experience Platform, read the batch ingestion overview.
If you select to hash the email addresses yourself, make sure to comply with the following requirements:
-
Remove leading and trailing spaces.
-
Convert all ASCII characters to lowercase.
-
In
gmail.comemail addresses, remove the following characters from the username part of the email address:- The period (. (ASCII code 46)). For example, normalize
jane.doe@gmail.comtojanedoe@gmail.com. - The plus sign (+ (ASCII code 43)) and all subsequent characters. For example, normalize
janedoe+home@gmail.comtojanedoe@gmail.com.
- The period (. (ASCII code 46)). For example, normalize
Export type and frequency export-type-frequency
Refer to the table below for information about the destination export type and frequency.
Connect to the destination connect
Authenticate to Destination authenticate
The Trade Desk CRM Destination is a daily batch file upload and does not require authentication by the user.
Fill in Destination Details fill-in-details
Before you can send, or activate, audience data to a destination, you must set up a connection to your own destination platform. While setting up this destination, you must provide the following information:
- Account Type: Please choose the Existing Account option.
- Name: A name by which you will recognize this destination in the future.
- Description: A description that will help you identify this destination in the future.
- Advertiser ID: your Trade Desk Advertiser ID, which can either be shared by your Trade Desk Account Manager or be found under Advertiser Preferences in the Trade Desk UI.
When connecting to the destination, setting a data governance policy is completely optional. Please review the Experience Platform data governance overview for more details.
Activate audiences to this destination activate
-
To activate data, you need the View Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.
-
To export identities, you need the View Identity Graph access control permission.
Read activate audience data to batch profile export destinations for instructions on activating audiences to a destination.
In the Scheduling page, you can configure the schedule and the file names for each audience you are exporting. Configuring the schedule is mandatory, but configuring the file name is optional.
In the Mapping page, you must select attributes or identity namespaces from the source column and map to the target column.
Below is an example of correct identity mapping when activating audiences to The Trade Desk CRM destination.
Selecting source fields:
- Select the
Emailnamespace or attribute as source identity if using the raw email address on data ingestion. - Select the
Email_LC_SHA256namespace or attribute as source identity if you hashed customer email addresses on data ingestion into Platform.
Selecting target fields:
- Input
emailas target identity when your source namespace or attribute isEmail. - Input
hashed_emailas target identity when your source namespace or attribute isEmail_LC_SHA256.
Validate Data Export validate
To validate that data is correctly exported out of Experience Platform and into The Trade Desk, please find the audiences under the ÃÛ¶¹ÊÓƵ 1PD data tile within The Trade Desk Data Management Platform (DMP). Here are the steps to finding the corresponding ID within the Trade Desk UI:
- First, select the Data tab, and review the First-Party section.
- Scroll down the page, under Imported Data, you will find the ÃÛ¶¹ÊÓƵ 1PD Tile.
- Click on the ÃÛ¶¹ÊÓƵ 1PD tile, and it will list out all audiences activated to the Trade Desk destination for your advertiser. You may also use the search function.
- The Segment ID # from Experience Platform will appear as the Segment Name in the Trade Desk UI.
Data usage and governance data-usage-governance
All ÃÛ¶¹ÊÓƵ Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how ÃÛ¶¹ÊÓƵ Experience Platform enforces data governance, see the Data Governance overview.