The Trade Desk CRM Data Integration

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

You can write job results from Treasure Data directly to The Trade Desk. In The Trade Desk, you can then use these Data Export in your ad campain.

Prerequisites

• Basic knowledge of Treasure Data, including the TD Toolbelt
• An account in The Trade Desk.
• Authorized Treasure Data account access.

Connector Usecase

• Advertiser First-Party Data API by The Trade Desk Export connector
  • What it is: A more permanent integration that syncs an advertiser’s customer database with The Trade Desk.
  • How it’s used: Strategic, always-on use of first-party data as an asset. For example, continuously syncing loyalty program members into the platform so they can be used across many campaigns over time.
  • Business value: Turns your customer base into a long-term strategic asset for advertising. Instead of campaign-by-campaign uploads, your data is always available to fuel audience creation and targeting.
• CRM Data Integration API by The Trade Desk CRM Data Export connector
  • What it is: A way to upload specific customer lists (emails, phone numbers, etc.) into the platform to build a segment.
  • How it’s used: Typically for campaign-specific or one-off use cases. For example, uploading a list of churned customers to exclude them from an upcoming campaign.
  • Business value: Gives marketers the flexibility to act quickly — “I want to target or exclude this group right now.”

Using the TD Console to Create Your Connection

You can use the TD Console to configure your connection.

In The Trade Desk: Getting the Platform API Token

Go to Manage API Tokens/Keys and create a new token/keys or select existing tokens

In Treasure Data: Creating a New Connection

1. From TD Console, select Integrations Hub.

2. Select Catalog.

3. Search for and select The Trade Desk CRM Data Output connector.

   

4. Select Create Authentication.

   The New Authentication dialog opens.

   

5. Edit the CRM Data Token and advertiser ID you obtained from The Trade Desk, and select Continue.

6. Enter a name for the connection.

   

7. Select Done.

The Trade Desk output connector is created.

Configuring Export Results in Your Data Connection

In this step, you create or reuse a query. In the query, you configure the data connection.  In some cases, you must define the column mapping in the query.

Configuring the Connection by Specifying the Parameters

1. Access the TD Console and navigate to Data Workbench > Queries.

2. Locate and select the the query that you want to use to export data.

3. Select Export Results located at top of your query editor.

   The Choose Integration dialog displays.

4. Enter The Trade Desk connection name in the search box to filter and select your connection.

5. Specify the parameters:

Parameters:

• CRM Data Segment ID(optional): Your CRM Data Segment ID. Required if Segment Name is empty.
• Segment Name(optional): Your segment name. Required if CRM Data Segment ID is empty.
• Merge Mode (required): The way the newly uploaded personally identifiable information (PII) is to be merged with the existing data. One of Add, Replace. Default is Add
• PII Type (required): The type of personally identifiable data (PII) sent by the advertiser. Select from a drop down, see PII Types. Default is Email.
• Time-to-Live (TTL)(optional): Time-to-live in minutes for the anonymized identifiers generated by the mapping process. Default is 129.600 (90 days).
• Wait Until Finished (optional): Check to let the job execution wait until drop state move to final. Default is false (unchecked).
• Max Wait Time (optional): Max time until jobs finished in minutes. Default is 720 minutes (12 hours). Allow value range 0 - 1380 (23 hours).
• Skip invalid record(s) (optional): Check to skip invalid records and process all remaining. Default is true (checked)

PII Type

A sample configuration is as follows:

Data Validation

• PII columns must not be empty.
• Timestamp_utc must not be empty. Column type can be string in datetime format or long for datetime in seconds.

Example Queries to Populate The Trade Desk

From Treasure Data, run the following query with Output results into a connection for The Trade Desk:

Example Query

SELECT
    PII,
    timestamp_utc,
    VALUE,
    value_currency,
    Country,
    Region,
    metro,
    City,
    OrderId,
    td_1,
    td_2,
    td_3,
    privacy_type,
    is_applicable,
    consent_string
FROM (
    VALUES
        ('', '2025-08-11 03:25:25.675', 4.5, 'USD', 'US', 'Region', 56, 'City', 'order id', 'custom data 1', 'custom data 2', 'custom data 3', 'GPP',  TRUE,  'consent string'),
        ('customer1@example.org', '2025-08-11 03:25:25.675', 4.5, 'USD', 'US', 'Region', 56, 'City', 'order id', 'custom data 1', 'custom data 2', 'custom data 3', 'GPP',  TRUE,  'consent string'),
        ('customer2@example.org', NULL,                        4.5, 'USD', 'US', 'Region', 56, 'City', 'order id', 'custom data 1', 'custom data 2', 'custom data 3', 'GPP',  TRUE,  'consent string'),
        ('customer3@example.org', '2025-08-11 03:25:25.675', 4.5, 'USD', 'US', 'Region', 56, 'City', 'order id', 'custom data 1', 'custom data 2', 'custom data 3', 'GPP',  FALSE, 'consent string')
) AS tbl (
    PII,
    timestamp_utc,
    VALUE,
    value_currency,
    Country,
    Region,
    metro,
    City,
    OrderId,
    td_1,
    td_2,
    td_3,
    privacy_type,
    is_applicable,
    consent_string
);

(Optional) Schedule Query Export Jobs

You can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.

Treasure Data's scheduler feature supports periodic query execution to achieve high availability.

When two specifications provide conflicting schedule specifications, the specification requesting to execute more often is followed while the other schedule specification is ignored.

For example, if the cron schedule is '0 0 1 * 1', then the 'day of month' specification and 'day of week' are discordant because the former specification requires it to run every first day of each month at midnight (00:00), while the latter specification requires it to run every Monday at midnight (00:00). The latter specification is followed.

Scheduling your Job Using TD Console

1. Navigate to Data Workbench > Queries

2. Create a new query or select an existing query.

3. Next to Schedule, select None.

4. In the drop-down, select one of the following schedule options:

   Drop-down Value	Description
   Custom cron...	Review Custom cron... details.
   @daily (midnight)	Run once a day at midnight (00:00 am) in the specified time zone.
   @hourly (:00)	Run every hour at 00 minutes.
   None	No schedule.

Custom cron... Details

 *    *    *    *    *
 -    -    -    -    -
 |    |    |    |    |
 |    |    |    |    +----- day of week (0 - 6) (Sunday=0)
 |    |    |    +---------- month (1 - 12)
 |    |    +--------------- day of month (1 - 31)
 |    +-------------------- hour (0 - 23)
 +------------------------- min (0 - 59)

The following named entries can be used:

• Day of Week: sun, mon, tue, wed, thu, fri, sat.
• Month: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec.

A single space is required between each field. The values for each field can be composed of:

1. (Optional) You can delay the start time of a query by enabling the Delay execution.

Execute the Query

Save the query with a name and run, or just run the query. Upon successful completion of the query, the query result is automatically exported to the specified destination.

(Optional) You can delay the start time of a query by enabling the Delay execution.

Activate a Segment in Audience Studio

You can also send segment data to the target platform by creating an activation in the Audience Studio.

1. Navigate to Audience Studio.
2. Select a parent segment.
3. Open the target segment, right-mouse click, and then select Create Activation.
4. In the Details panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
5. Customize the activation output in the Output Mapping panel.

• Attribute Columns
  • Select Export All Columns to export all columns without making any changes.
  • Select + Add Columns to add specific columns for the export. The Output Column Name pre-populates with the same Source column name. You can update the Output Column Name. Continue to select + Add Columnsto add new columns for your activation output.
• String Builder
  • + Add string to create strings for export. Select from the following values:
    • String: Choose any value; use text to create a custom value.
    • Timestamp: The date and time of the export.
    • Segment Id: The segment ID number.
    • Segment Name: The segment name.
    • Audience Id: The parent segment number.

6. Set a Schedule.

• Select the values to define your schedule and optionally include email notifications.

7. Select Create.

Using TD Toolbelt and Your The Trade Desk Connection

You can use TD Toolbelt from the CLI to export to The Trade Desk.

Example

td query \
  -d [database] \
  -q "SELECT * FROM offline_conversion" \
  --type presto \
  --result '{
    "type": "thetradedesk_crm_data",
    "crm_api_token": "xxx",
    "advertiser_id": "xxx",
    "crm_data_id": "xxx",
    "skip_invalid_records": true
  }'

Configuring Export Results in Workflow (Optional)

Within Treasure Workflow, you can specify the use of this data connector to output data.

timezone: UTC

_export:
  td:
    database: sample_datasets

+td-result-into-target:
  td>: queries/sample.sql
  result_connection: your_connections_name
  result_settings:
    crm_api_token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    advertiser_id: xxxxxx
    crm_data_id: xxx
    ....

Review information on using data connectors in workflow to export data.

Appendix

Statistic logs

Statistic logs for skipping records and upload detail from The Trade Desk are shown at the end of job execution.

Sample skipping records from plugin validation

2025-08-25 08:02:35.717 +0000 [INFO] (0001:transaction): ************* REPORT *************2025-08-25 08:02:35.717 +0000 [INFO] (0001:transaction): Total records: 42025-08-25 08:02:35.717 +0000 [INFO] (0001:transaction): Uploaded records: 12025-08-25 08:02:35.717 +0000 [INFO] (0001:transaction): Total skipped records: 32025-08-25 08:02:35.721 +0000 [WARN] (0001:transaction): Data error - Skip processing the record index [0]: The required field(s) is(are) null or empty: pii2025-08-25 08:02:35.721 +0000 [WARN] (0001:transaction): Data error - Skip processing the record index [2]: The required field(s) is(are) null or empty: timestamp_utc2025-08-25 08:02:35.721 +0000 [WARN] (0001:transaction): Data error - Skip processing the record index [3]: The required field(s) is(are) null or empty: timestamp_utc

Sample The Trade Desk statistic logs

2025-08-25 08:02:35.712 +0000 [WARN] (0025:task-0000): =========== UPLOAD STATISTIC FROM TTD ===========2025-08-25 08:02:35.712 +0000 [WARN] (0025:task-0000): ===== Total Records: 12025-08-25 08:02:35.712 +0000 [WARN] (0025:task-0000): ===== Valid Records: 12025-08-25 08:02:35.713 +0000 [WARN] (0025:task-0000): ===== Succeeded Records: 12025-08-25 08:02:35.713 +0000 [WARN] (0025:task-0000): ===== Failed Records: 02025-08-25 08:02:35.713 +0000 [WARN] (0025:task-0000): ===== Empty Records: 02025-08-25 08:02:35.713 +0000 [WARN] (0025:task-0000): ===== Ingested Records: 12025-08-25 08:02:35.713 +0000 [WARN] (0025:task-0000): =================================================

See Also

• Scheduling Data Connector Job Execution from the CLI