# The Trade Desk Export Integration

You can write job results from Treasure Data directly to The Trade Desk. In The Trade Desk, you can then distribute advertisements to each DSP targeting segment.

## Prerequisites

- Basic knowledge of Treasure Data, including the [TD Toolbelt](https://toolbelt.treasuredata.com/)
- An account in The Trade Desk
- Authorized Treasure Data account access to The Trade Desk


## Limitation

The Trade Desk Export Integration does not support Personal Identifiable Information (PII) data.

## Integration Overview

This integration has two parts:

1. **Cookie-syncing between The Trade Desk DMP and Treasure Data CDP** — This is required to create a mapping between The Trade Desk DMP ID and Treasure Data's ID td_global_id.
2. **Data export from Treasure Data CDP into The Trade Desk DMP** — Based on the mapping created when you sync cookies, Treasure Data's ID translates segments keyed on their ID into segments keyed on The Trade Desk DMP. Then, you can export the translated segmented data into your The Trade Desk account using the Treasure Data output data connector.


**Cookie Syncing between The Trade Desk and Treasure Data**

![](/assets/trade-desk-integration.39f65762f4f5a83713aa583e6ca314a1e694e6f42e666d2d4d5e263438f457cb.7f5c9654.png)

**Data Transfer from Treasure Data to The Trade Desk**

![](/assets/ttddataxfer.139600ac80280f4591a0d02797e91707aa19cd5d20a96abb3aeb3eaa74ec9be9.7f5c9654.png)

## Implementing a Cookie-Syncing Tag

You must first set up Treasure Data's JavaScript tag, td_global_id, as illustrated in the previous section and documented in [using JavaScript SDK for Cross-Domain Tracking.](https://docs.treasuredata.com/smart/project-product-documentation/enabling-cross-domain-tracking-with-javascript-sdk)

TTD Sync tag is provided per each region. Once it is accessed, they are redirected to `https://in.treasuredata.com/postback/v3/event/ttd/sync?td_format=pixel&td_write_key=%%TTD_PUID%%&td_global_id=td_global_id&td_ip=td_ip&ttd_id=%%TTD_TDID%%&td_ua=td_ua`. It’s stored in `ttd` (DB) `sync` (table). Customer needs to create them before they implement the tag. TD Write APIKEY should be url encoded. Please change  to %2F

- US Region: https://match.adsrvr.org/track/cmf/generic?ttd_pid=01qhnrr&ttd_tpi=1&ttd_puid={please paste your TD Write API KEY}
- EU01 Region: https://match.adsrvr.org/track/cmf/generic?ttd_pid=996ppa1&ttd_tpi=1&ttd_puid={please paste your TD Write API KEY}
- Tokyo Region: https://match.adsrvr.org/track/cmf/generic?ttd_pid=6nh6mgj&ttd_tpi=1&ttd_puid={please paste your TD Write API KEY}


Add code similar to the following into the website where The Trade Desk DMP's tag is already installed. The following code is an example for EU01 region. Please update the code based on your requirement.


```html
<script type="text/javascript">
!function(t,e){if(void 0===e[t]){e[t]=function(){e[t].clients.push(this),this._init=[Array.prototype.slice.call(arguments)]},e[t].clients=[];for(var r=["addRecord","blockEvents","fetchServerCookie","fetchGlobalID","fetchUserSegments","resetUUID","ready","setSignedMode","setAnonymousMode","set","trackEvent","trackPageview","trackClicks","unblockEvents"],s=0;s<r.length;s++){var c=r[s];e[t].prototype[c]=function(t){return function(){return this["_"+t]=this["_"+t]||[],this["_"+t].push(Array.prototype.slice.call(arguments)),this}}(c)}var n=document.createElement("script");n.type="text/javascript",n.async=!0,n.src=("https:"===document.location.protocol?"https:":"http:")+"//cdn.treasuredata.com/sdk/4.0/td.min.js";var o=document.getElementsByTagName("script")[0];o.parentNode.insertBefore(n,o)}}("Treasure",this);

function createIframe(iframeSrc) {
  var gdpr = false;
  var gdpr_consent = '';

  // The parameter value provides information about vendor consent.
  // iframe not necessary but a recommendation given by The Trade Desk
  var iframe = document.createElement('iframe');
  iframe.src = iframeSrc;
  iframe.height = 1;
  iframe.width = 1;
  iframe.style.border = 'none';
  document.body.appendChild(iframe);

  function loadPixel(pixelSrc) {
    var pixel = document.createElement('img');
    pixel.src = pixelSrc;
    pixel.width = 1;
    pixel.height = 1;
    pixel.style.display = 'none';
    iframe.contentWindow.document.body.appendChild(pixel);
  }

  // new TTD URL
  var ttd_url = 'https://match.adsrvr.org/track/cmf/generic?';
  var params = [
    'ttd_pid=996ppa1',
    'ttd_tpi=1',
    'ttd_puid=' + 'your td api key',
    `gdpr=${gdpr ? 1 : 0}`,
    `gdpr_consent=${gdpr ? gdpr_consent : ''}`,
    `domain=${(window != window.parent) ? (new URL(document.referrer).hostname) : window.location.host}`
  ];
  loadPixel(ttd_url + params.join('&'));
}

var iframeSrc = 'about:blank';
var td = new Treasure({
  host: 'eu01.in.treasuredata.com',
  writeKey: 'your td api key',
  database: '{{name}}_ttd', // db where you will store pageviews
  startInSignedMode: true,
  trackCrossDomain: true,
  cdpHost: 'cdp-eu01.in.treasuredata.com'
});
var tbl = 'sync';
td.setSignedMode();
td.set('$global', 'td_global_id', 'td_global_id');
td.trackPageview(tbl, createIframe(iframeSrc));
</script>
```

## Using the TD Console to Create Your Connection

You can use the TD Console to configure your connection.

### In The Trade Desk: Getting the Secret Key

Go to **Your Advertiser > Preferences** and scroll down to get your **Secret Key**

![](/assets/ttd_advertiser_pref.9cd11bf875f9a1d64b3e98413e570d333b0e0721c545c31e7c2d34c2bf56c183.7f5c9654.png)

### 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** Output connector.
![](/assets/tradedeskoutput.9a703415a16009d454fe7e47c9a8d7b03d10d4ee5b4a1585afa37dd8f19ca476.7f5c9654.png)
4. Select **Create Authentication**.
The New Authentication dialog opens.
![](/assets/tradedeskauthdialog2.2e6573bbefd15353cc941478944c0d93b9dd499e682694eb51110489ae0cccde.7f5c9654.png)
5. Edit the secret key you obtained from The Trade Desk, and select **Continue**.
6. Enter a name for the connection.
![](/assets/tradedesknewauthb.1c83a3cb0dcb352f1b606312d0876c7ef00c89eb9f6f015a6d45062a4b51db64.7f5c9654.png)
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**:

- **Advertiser ID**(required): Your advertiser ID.
- **Select host name**(required): Use the host name closest to the location of users targeted by your campaign. Default TOK (Tokyo)
- **Recency targeting** (optional): Recency targeting (optional): A UTC timestamp by which a user, who qualifies for your target audience, is tagged. Omitting this field assumes the user was put into the segment as soon as The Trade Desk processed the data. Alternatively you specify a date and time by which a user is eligible for the data segment. Specify a timestamp in UTC. The format is: yyyy-MM-dd HH:mm. MM represents month (not minute), HH represents 24 hours (not 12). Default : blank
- **Data remains active in a duration of** (required): Specify the length of time that a user remains active, as relative to Recency targeting; when the time expires, the data is not used for targeting. Specify the Time-to-live (TTL) in minutes. The time can't be more than 259200 mins (180 days). Minimum time recommended is 2880 mins(48 hours).
- **Max records per batch request**(optional): Max Number of records to upload in each batch. Default: 5000
- **Sleep Per API request in Milliseconds** (optional): The time, in milliseconds, that the system sleeps for each request. Default : 2000, which is equivalent to 2 seconds.
- **Retry Limit** (optional): Number of retries before the system gives up. Default: 7.


### A sample configuration is as follows:

#### 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 for TDID**


```sql
SELECT id AS tdid,
name AS dataname
FROM your_table;
```

**Example Query for DAID**


```sql
SELECT id AS daid,
name AS dataname
FROM your_table;
```

**Example Query for UID2**


```sql
SELECT id AS uid2,
name AS dataname
FROM your_table;
```

**Example Query for RampID**


```sql
SELECT id AS rampid,
name AS dataname
FROM your_table;
```

### (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.
![](/assets/image2021-1-15_17-28-51.f1b242f6ecc7666a0097fdf37edd1682786ec11ef80eff68c66f091bc405c371.0f87d8d4.png)
4. In the drop-down, select one of the following schedule options:
![](/assets/image2021-1-15_17-29-47.45289a1c99256f125f4d887e501e204ed61f02223fde0927af5f425a89ace0c0.0f87d8d4.png)
| Drop-down Value | Description |
|  --- | --- |
| Custom cron... | Review [Custom cron... details](#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

![](/assets/image2021-1-15_17-30-23.0f94a8aa5f75ea03e3fec0c25b0640cd59ee48d1804a83701e5f2372deae466c.0f87d8d4.png)

| **Cron Value** | **Description** |
|  --- | --- |
| `0 * * * *` | Run once an hour. |
| `0 0 * * *` | Run once a day at midnight. |
| `0 0 1 * *` | Run once a month at midnight on the morning of the first day of the month. |
| "" | Create a job that has no scheduled run time. |



```
 *    *    *    *    *
 -    -    -    -    -
 |    |    |    |    |
 |    |    |    |    +----- 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:

| Field Value | Example | Example Description |
|  --- | --- | --- |
| A single value, within the limits displayed above for each field. |  |  |
| A wildcard `'*'` to indicate no restriction based on the field. | `'0 0 1 * *'` | Configures the schedule to run at midnight (00:00) on the first day of each month. |
| A range `'2-5'`, indicating the range of accepted values for the field. | `'0 0 1-10 * *'` | Configures the schedule to run at midnight (00:00) on the first 10 days of each month. |
| A list of comma-separated values `'2,3,4,5'`, indicating the list of accepted values for the field. | `0 0 1,11,21 * *'` | Configures the schedule to run at midnight (00:00) every 1st, 11th, and 21st day of each month. |
| A periodicity indicator `'*/5'` to express how often based on the field's valid range of values a schedule is allowed to run. | `'30 */2 1 * *'` | Configures the schedule to run on the 1st of every month, every 2 hours starting at 00:30. `'0 0 */5 * *'` configures the schedule to run at midnight (00:00) every 5 days starting on the 5th of each month. |
| A comma-separated list of any of the above except the `'*'` wildcard is also supported `'2,*/5,8-10'`. | `'0 0 5,*/10,25 * *'` | Configures the schedule to run at midnight (00:00) every 5th, 10th, 20th, and 25th day of each month. |


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.

Scheduled jobs that continuously fail due to configuration errors may be disabled on the system side after several notifications.

(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.


![](/assets/ouput.b2c7f1d909c4f98ed10f5300df858a4b19f71a3b0834df952f5fb24018a5ea78.8ebdf569.png)

- 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 Columns**to 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.


1. Set a **Schedule**.


![](/assets/snippet-output-connector-on-audience-studio-2024-08-28.a99525173709da1eb537f839019fa7876ffae95045154c8f2941b030022f792c.8ebdf569.png)

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


1. Select **Create**.


If you need to create an activation for a batch journey, review [Creating a Batch Journey Activation](/products/customer-data-platform/journey-orchestration/batch/creating-a-batch-journey-activation).

## Configuring Export Results in Workflow (Optional)

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


```yaml
timezone: UTC

_export:
  td:
    database: sample_datasets

+td-result-into-target:
  td>: queries/sample.sql
  result_connection: your_connections_name
  result_settings:
    secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    advertiser_id: xxxxxx
    data_activation_duration: 43200
    ....
```

Review [information on using data connectors in workflow](https://docs.treasuredata.com/smart/project-product-documentation/using-integrations-to-import-data-with-td-workflows) to export data.

## Using TD Toolbelt and Your The Trade Desk Connection

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

Example TDID


```bash
td query \
  --result '{
    "type": "thetradedesk",
    "secret_key": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "advertiser_id": xxxxxx,
    "data_activation_duration": 43200
  }' \
  -d sample_datasets \
  "SELECT tdid, dataname FROM (
     VALUES
       ('d46a3975-c267-404e-89ae-0a9ff0cdce5f', 'demo-segment'),
       ('244d97ec-c258-4359-ae80-c67bf92bd294', 'demo-segment'),
       ('f749cd45-c6e2-4a82-87fe-afb7d2cd1188', 'demo-segment')
   ) AS tbl (tdid, dataname)" \
  -T presto
```

Example DAID


```bash
$ td query --result '{"type":"thetradedesk","secret_key":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxx","advertiser_id":xxxxxx,"data_activation_duration":43200}' -d sample_datasets "SELECT daid, dataname FROM (
 VALUES ('d46a3975-c267-404e-89ae-0a9ff0cdce5f','demo-segment'),
 ('244d97ec-c258-4359-ae80-c67bf92bd294','demo-segment'),
 ('f749cd45-c6e2-4a82-87fe-afb7d2cd1188','demo-segment')
) tbl (daid, dataname)" -T presto
```

Example DAID


```bash
td query \
  --result '{
    "type": "thetradedesk",
    "secret_key": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "advertiser_id": xxxxxx,
    "data_activation_duration": 43200
  }' \
  -d sample_datasets \
  "SELECT daid, dataname FROM (
     VALUES
       ('d46a3975-c267-404e-89ae-0a9ff0cdce5f', 'demo-segment'),
       ('244d97ec-c258-4359-ae80-c67bf92bd294', 'demo-segment'),
       ('f749cd45-c6e2-4a82-87fe-afb7d2cd1188', 'demo-segment')
   ) AS tbl (daid, dataname)" \
  -T presto
```

Example DAID


```bash
td query \
  --result '{
    "type": "thetradedesk",
    "secret_key": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "advertiser_id": xxxxxx,
    "data_activation_duration": 43200
  }' \
  -d sample_datasets \
  "SELECT rampid, dataname FROM (
     VALUES
       ('XY1005wXyWPB1SgpMUKIpzA0I3UaLEz-2lg0wFAr1PWK7FMhs', 'demo-segment'),
       ('XY1005wXyWPB1SgpMUKIpzA0I3UaLEz-2lg0wFAr1PWK7FMhs', 'demo-segment'),
       ('XY1005wXyWPB1SgpMUKIpzA0I3UaLEz-2lg0wFAr1PWK7FMhs', 'demo-segment')
   ) AS tbl (rampid, dataname)" \
  -T presto
```