After running an activation query, you can push the resulting file to create a targetable segment on The Trade Desk platform.

To push results to The Trade Desk (TTD), you will need to create a Destination to connect the InfoSum Platform and your Trade Desk seat. There are two destinations: Standard TTD Destination and TTD CRM Destination. The difference is the keys that can be pushed to each

Both destinations will map the provided keys to UID2.0 (or EUID if located in the EU)

Before starting, you will need the following to hand:

• Trade Desk Advertiser ID: This is in your TTD platform, please contact your TTD representative if you are unsure as to this
• Target segment name: It can be an existing segment to refresh or a new segment name that doesn’t yet exist)
• Trade Desk Secret API key: Please contact your TTD representative for this.
• Signed Access Letter: Please contact your TTD representative to obtain a copy if you have not already signed one
• Signed UID2.0/EUID Service Agreement (if using the CRM destination)

In this article you will find instructions for how to:

• Set up a Standard TTD Destination
• Set up a TTD CRM Destination
• Use the TTD Destination for your activation 

The Trade Desk standard destination setup

The standard TradeDesk destination allows for the export of segments which have the following keys:

• UID2 (Outside of EU only)
• RampID
• TTD Cookie
• MAID

These keys will be shown as UID2/EUID in your platform.

This screen contains the following fields:

1. Advertiser ID: TTD account ID for advertiser
2. Region: Target region for the audience to be used in
3. Secret API Key: A long lived or short lived API token (Details are here)
4. Segment Name: The name of the segment. If no segment with this name exists, a new one will be created. If an existing segment exists with this name then that will be used in preference to creating a new segment.
5. TTL in Days: Time-to-live (TTL) in days for the anonymized identifiers generated by the mapping process. If not provided, the default value is 90 days.

Optional fields

1. TTL Start Date and Time: Date/Time from which data should be considered live. TTL will apply from this point. Format YYYY-MM-DD HH:MM

Complete all the mandatory fields and click submit. As the destination is reusable all fields can be specified as editable/non editable at point of export to allow you to customize all specific exports.

Please note that any fields that you make editable at push time will be editable by companies that you share the destination with.

Once completed, this destination can be used in the export configuration detailed above.

The Trade Desk CRM destination setup

The TradeDesk CRM destination allows for the keys below to be sent to your chosen TradeDesk account which the TradeDesk will then map to their own UID (EUID for UK/Europe and UID2 for the rest of world). These keys can be provided clear or hashed:

• Email
• Phone number (Outside EU only)

For customers outside of the EU/UK region, you can include both email or phone numbers in your files, but you can only choose one key to map your UID to.

This screen contains the following fields:

1. Advertiser ID: TTD account ID for advertiser
2. Region: Target region for the audience to be used in
3. Secret API Key: A long lived or short lived API token (As detailed in the introductory note above)
4. Segment Name: The name of the segment. If no segment with this name exists, a new one will be created. If an existing segment exists with this name then that will be used in preference to creating a new segment.
5. PII type: The type of personally identifiable information (PII) to be sent. The options are:
   1. RawEmail - Raw email data will be sent.
   2. HashedEmail - Emails from your dataset will be hashed prior to sending.
   3. PreHashedEmail - Pre-hashed emails from your dataset will be sent as-is, use this option if you already have hashed emails in your dataset that you wish to send as-is.
   4. RawPhone - Raw phone number data will be sent.
   5. HashedPhone - Phone numbers from your dataset will be hashed prior to sending
   6. PreHashedPhone - Pre-hashed phone numbers from your dataset will be set as-is, use this option if you already have hashed phone numbers in your dataset that you wish to send as-is

If Phone data is to be exported then all phone numbers need to be in the E.164 format: `[+][country code][subscriber number including area code]` (with no spaces, hyphens, parentheses, or other special characters). Please note that only emails may be used for mapping in the UK/EU region.

6. PII Column: The name of the column in the activation data that contains the PII to upload.
7. Mergemode: The way the newly uploaded personally identifiable information (PII) is to be merged with the existing data. Options are:
   1.  Add: you can add individual rows to the existing segment or by specifying a TTL of 0 on the rows, remove individual records for consent changes for example.
   2. Replace: replace specifies a complete refresh of the segment with a new segment. 

Optional fields

1. Retention enabled toggle: If set to true, PII data is retained in hashed form for 90 days and is refreshed daily as UIDs decay. If set to false, PII data is processed once and then discarded.
2. TTL in Minutes: Time-to-live (TTL) in minutes for the anonymized identifiers generated by the mapping process. If not provided, the default value is 129600 minutes (90 days).

Complete all the mandatory fields and click submit. 

As the destination is reusable, all fields can be specified as editable/non editable at push time to allow you to customize all specific exports later in the process. 

Please note that any fields that you make editable at push time will be editable by companies that you share the destination with.

Additional Information

1. You can find your InfoSum uploaded audiences within your chosen Trade Desk seat under the Data tab > 1st Party Data > My Imported Data
2. TTD CRM Connector Documentation from the Trade Desk can be found here

Using a TradeDesk destination for your activation

You can activate results to a file using either Segment Builder or the Query Tool. Go to the Activation tab under Activate, where you will see some information about the campaign and its status. The total rows gives you an insight into the size of the dataset, before pushing it to the destination.

At the bottom of the page, you will see a box providing more details on the campaign, such as the query used and the name of the output column. There are three menu tabs within this box - Details, Export Configuration and Export History. Once you've pushed the results, the details and status will be viewable under the Export History tab.

For now, switch to Export Configuration, choose the destination options and choose your TradeDesk destination (standard or CRM). If you haven’t set up a TradeDesk destination, click on Create New to set up your reusable destination (See below).

Switch to the Export History tab to see the status and check for any errors. Once the status has a green tick, the file has been successfully pushed to the client’s segment in The Trade Desk. Note: The TradeDesk states a 24 hour period for processing exports. If you don’t see segments in your account within that period, please contact your TradeDesk account manager.

If you are experiencing slower than expected import/export speeds and you're using a VPN or firewall that can block data upload or download, please refer to Add IP addresses to an Allowlist.