Overview
TTD (The Trade Desk) 1P is a feature that allows marketers to leverage their 1P data to create more targeted and personalised advertising campaigns. Integrated with Zeotap it allows marketers to create custom audiences and more personalisation for the targeted audience.Supported Identifiers
This integration is supported for both MAIDs/Device IDs and TTD cookies.Available Actions and Supported Features
The following table lists the available action types for the integration and the supported features for each action type:| Action Name | ID EXTENSION | DELETE | DELTA UPLOAD |
|---|---|---|---|
| Send identifiers to TTD 1P | ✅ | ✅ | - |
Components
Ensure that you have details about the below components of TTD available before creating a Destination.Advertiser ID
Advertiser ID is your TTD 1P Ad Account ID.Secret Key
A Secret Key is the piece of information that is used to encrypt and decrypt messages. You can navigate to the TTD 1P console and look for the Advertiser ID and Secret Key under the First Party Data Credentials section.
Create a Destination for TTD 1P
Perform the following steps to create a Destination for TTD 1P:
Click TTD 1P. A screen appears displaying details about the particular destination towards the left. On the right-hand side of the screen find a list of fields that are required for the integration to be established. Enter the required details as mentioned in the following steps:a. Enter a name for the Destination.b. Enter the Advertiser ID.c. Enter the Secret Key.d. Review all the values entered above and then click Next to proceed.
In the new screen that appears, choose the appropriate Action and mapping as explained below.a. Choose the desired action under Choose your Action and then choose the corresponding identifiers under Map the Fields. By default, the Output Identifiers that are accepted by the platform such as, MAIDs, Cookies, email Ids and more are displayed. However, you can edit, add or remove an identifier from the list. To do so, refer here.b. Click Create Destination. The created Destination gets listed in the Target and Audiences applications, which can be linked to an Audience/segment.
Link an Audience to the TTD Destination
For information about how to link an Audience or segment to the created Destination in the Audiences application, refer here.Note:The following are some useful information related to pushing a segment to TTD 1P Destination:
- The identifiers that appear in the window are the ones that are available in the segment and supported by TTD 1P.
- The audience creation step in Audiences and the corresponding audience IDs are for internal reference only. As such segments are not available immediately in the client account as soon as they are created. These segments are directly available in the client’s TTD account once the data is successfully uploaded.
- It can take up to three business days for segments to be available at the TTD 1P seat.
- In order to be reflected in The Trade desk Platform, there needs to be a minimum of 1000 IDs in a segment. The minimum limit also depends on the type of campaign that is to be run on that segment.
- The maximum limit for the JSON file is 50,000 IDs, and 4 MB for the API payload. If the size is greater than the maximum limit, then the segment can be broken down internally by Zeotap and then stitched back again by TTD platform.
- The Segment can be updated daily, but will be deleted from the data base of The Trade Desk on failing to update within 30 days.
User Disqualification from Audiences
This integration supports user disqualification from audiences. That is, a user can be disqualified from an audience (segment) for various reasons, such as not meeting audience criteria, consent requirements or other conditions set for a particular audience.- When a user disqualifies from an audience, Zeotap CDP initiates a user deletion request in the next refresh cycle. These requests are sent to the audiences linked to the specific destination.
- The disqualified users are excluded from the audiences based on the configured refresh frequency for a particular audience.
- User disqualification is a programmatic process that works automatically. You do not need to specify anything to trigger the disqualification and exclusion of users from audiences.