The Trade Desk Third-Party Data Connector Setup Guide | Server-Side Connectors

This connector is not currently available in the Connector Marketplace. Using the The Trade Desk Third-Party Data connector requires support from both Tealium and The Trade Desk account managers. To use this connector, contact your Tealium account manager.

API Information

This connector uses the following vendor API:

API Name: The Trade Desk API
API Version: v3.0
API Endpoint: https://bulk-data.adsrvr.org
Documentation: The Trade Desk API

Batch Limits

This connector uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:

Max number of requests: 10000
Max time since oldest request: 30 minutes
Max size of requests: 2 MB

Connector Actions

Action Name	AudienceStream	EventStream
Upload 3rd Party Data	✓	✗

Configure Settings

Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see About Connectors.

After adding the connector, configure the following settings:

Secret Key
Required. The secret key.
API Base URL
Required. Select your API base URL.

Actions

Enter a name for the action and select the action type from the drop-down menu.

The following section describes how to set up parameters and options for each action.

Upload 3rd Party Data

Parameters

Parameter	Description
Data Provider ID	Required. The provider ID supplied by your Technical Account Manager.
TDID	The Trade Desk 36-character GUID (including dashes) for this user.
DAID	The raw device ID for this user sent in 36-character GUID format (including dashes). Use iOS IDFA or Android’s AAID.
UID2Token (already SHA256 hashed)	The user’s Unified ID 2.0, already SHA256 hashed.
UID2Token (apply SHA256 hash)	The user’s Unified ID 2.0, to which a SHA256 hash will be applied.
UID2	The user’s Unified ID 2.0 as a 44-character base64-encoded SHA-256 string. For more information, see PII Normalization and Hash Encoding and Unified IDs.
EUIDToken (already SHA256 hashed)	The user’s European Unified ID, already SHA256 hashed.
EUIDToken (apply SHA256 hash)	The user’s European Unified ID, to which a SHA256 hash will be applied
EUID	The user’s European Unified ID as a 44-character base64-encoded SHA-256 string. For more information, see PII Normalization and Hash Encoding. EIUD offers user transparency and privacy controls designed to meet market requirements in Europe and the UK, and it requires the same normalization and encoding of email addresses as UID2. For more information, see Unified IDs.
IDL	The 49-character or 70-character RampID (previously known as IdentityLink). This value must be a RampID from LiveRamp that is mapped specifically for The Trade Desk. For more information about mapping a RampID, see LiveRamp documentation.
Name	Required. The segment name. Maximum 128 characters.
TTL in Minutes	Required. Time to live (TTL) is the amount of time (in minutes) during which this user is to remain active relative to the `TimeStampUtc` value. When the TTL has expired, the user will no longer be used for targeting. We recommend a value of 43200 minutes (30 days).
Timestamp	The timestamp of when a user is eligible for a segment. If not specified, the timestamp will be assigned based on the time when the data is processed. This timestamp is used to determine a user’s recency for targeting and bid adjustments.