The Trade Desk - CRM destination in Platform is currently in beta. The documentation and functionality are subject to change.
This documentation page was created by the Trade Desk team. For any inquiries or update requests, please contact your Trade Desk representative.
This document is designed to help you activate profiles to your Trade Desk account for audience targeting and suppression based on CRM data.
Use The Trade Desk CRM destination for CRM data mapping, like email or hashed email address. Use the other Trade Desk destination in the Adobe Experience Platform catalog for cookies and device ID mappings.
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.
Before you can activate segments 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.
Depending on the type of IDs you ingest into Adobe Experience Platform, you must adhere to their corresponding requirements. Please read the Identity Namespace overview for more information.
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 Adobe 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 addresses (clear text)||Select the
|Email_LC_SHA256||Email addresses need to be hashed using SHA256 and lowercased. Be sure to follow any email normalization rules required. You won’t be able to change this setting later.||Select the
You can hash email addresses before ingesting them into Adobe Experience Platform or use raw email addresses.
To learn about ingesting email addresses in Experience Platform, see the batch ingestion overview.
If you select to hash the email addresses yourself, make sure to comply with the following requirements:
gmail.comemail addresses, remove the following characters from the username part of the email address:
Refer to the table below for information about the destination export type and frequency.
|Export type||Segment export||You are exporting all members of a segment (audience) with the identifiers (email or hashed email) used in the Trade Desk destination.|
|Export frequency||Daily Batch||As a profile is updated in Experience Platform based on segment evaluation, the profile (identities) are updated once a day downstream to the destination platform. Read more about batch uploads.|
The Trade Desk CRM Destination is a daily batch file upload and does not require authentication by the user.
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:
When connecting to the destination, setting a Data Governance policy is completely optional. Please review the Experience Platform data governance overview for more details.
See activate audience data to batch profile export destinations for instructions on activating audience segments to a destination.
In the Scheduling page, you can configure the schedule and the file names for each segment you are exporting. Configuring the schedule is mandatory, but configuring the file name is optional.
All segments activated to The Trade Desk CRM Destination are automatically set to a daily frequency and full file export.
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 segments to The Trade Desk CRM destination.
The Trade Desk CRM Destination does not accept raw and hashed email addresses as identities in the same activation flow. Create separate activation flows for raw and hashed email addresses.
Selecting source fields:
Email_LC_SHA256namespace or attribute as source identity if you hashed customer email addresses on data ingestion into Platform.
Selecting target fields:
Email_LC_SHA256namespace as target identity when your source namespace or attribute is
To validate that data is correctly exported out of Experience Platform and into The Trade Desk, please find the segments under the Adobe 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:
All Adobe Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how Adobe Experience Platform enforces data governance, see the Data Governance overview.