Configure destination for The Trade Desk 3rd-party Marketplace

The Trade Desk is a platform for wide internet advertising and enables the use of Universal ID 2.0 for first-party paid media advertising.

Use this destination to monetize your brand’s UID 2.0-based audiences by making them available to advertisers for more granular targeting.

Get details

Review the following details before configuring credentials for The Trade Desk 3rd-party Marketplace and before configuring Amperity to send email addresses, EUID, or UID2 tokens to The Trade Desk 3rd-party Marketplace.

Detail 1.

A UID 2.0 agreement and / or a European Unified ID (EUID) agreement .

Detail 2.

Credential settings

Advertiser ID

Required

The advertiser ID for your account with The Trade Desk 3rd-party Marketplace.

Advertiser secret

Required

The advertiser secret for your account with The Trade Desk 3rd-party Marketplace.

You can find the advertiser ID and secret key from the management console within The Trade Desk 3rd-party Marketplace. Open “Preferences”, and then “First Party Data Credentials” to view the advertiser ID and secret key.

Provider ID

Required

The provider ID for your account with The Trade Desk. Ask your The Trade Desk representative for details.

Platform API token

Required

A long-lived token that allows access to The Trade Desk Platform API.

Configure credentials

Configure credentials for The Trade Desk 3rd-party Marketplace before adding a destination.

An individual with access to The Trade Desk 3rd-party Marketplace should use SnapPass to securely share “advertiser ID”, “advertiser secret”, “provider ID”, and “platform API token” details with the individual who configures Amperity.

To configure credentials for The Trade Desk 3rd-party

Step 1.

From the Settings page, select the Credentials tab, and then click the Add credential button.

Step 2.

In the Credentials settings dialog box, do the following:

From the Plugin dropdown, select The Trade Desk 3rd-party Marketplace.

Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination.

Step 3.

The settings that are available for a credential vary by credential type. For the “tradedesk-3rd-party” credential type, configure settings, and then click Save.

Advertiser ID

Required

The advertiser ID for your account with The Trade Desk 3rd-party Marketplace.

Advertiser secret

Required

The advertiser secret for your account with The Trade Desk 3rd-party Marketplace.

You can find the advertiser ID and secret key from the management console within The Trade Desk 3rd-party Marketplace. Open “Preferences”, and then “First Party Data Credentials” to view the advertiser ID and secret key.

Provider ID

Required

The provider ID for your account with The Trade Desk. Ask your The Trade Desk representative for details.

Platform API token

Required

A long-lived token that allows access to The Trade Desk Platform API.

Add destination

Use a sandbox to configure a destination for The Trade Desk 3rd-party Marketplace. Before promoting your changes, send a test audience, and then verify the results in The Trade Desk 3rd-party Marketplace. After verifying the end-to-end workflow, push the destination from the sandbox to production.

To add a destination for The Trade Desk 3rd-party

Step 1.

Open the Destinations page, and then click the Add destination button.

Add

To configure a destination for The Trade Desk 3rd-party Marketplace, do one of the following:

  1. Click the row in which The Trade Desk 3rd-party Marketplace is located. Destinations list alphabetically and you can scroll up and down the list.

  2. Search for The Trade Desk 3rd-party Marketplace. Start typing “trade”. The list filters to show only matching destinations. Select “The Trade Desk 3rd-party Marketplace”.

Step 2.

Select the credential for The Trade Desk 3rd-party Marketplace from the Credential dropdown, and then click Continue.

Tip

Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to The Trade Desk 3rd-party Marketplace.

Step 3.

In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination.

Configure business user access

By default a destination is available to all users who have permission to view personally identifiable information (PII).

Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies.

Enable the PII setting checkbox to allow limited access to PII for this destination.

Use the Restrict PII access policy option to prevent users from viewing data marked as PII anywhere in Amperity and from sending data to downstream workflows.

Step 4.

Configure the following settings, and then click “Save”.

Membership duration

The length of time (in days), after which a customer is removed from this audience. This value may be between “0” - “180”. Set this value to “0” to remove all audience members.

The minimum value should be “7” because The Trade Desk 3rd-party Marketplace uses the previous seven days when building audiences. “14” is the default duration. The maximum value is “180”.

The membership duration is in days. Adjust the membership duration value to be greater than or equal to than the frequency at which your brand sends campaigns or orchestrations from Amperity.

For example: if your brand sends a campaign to The Trade Desk 3rd-party Marketplace every 30 days, then set membership duration to “30”. If your brand sends a campaign every 14 days, then set membership duration to “14”.

If your brand sends a campaign every 30 days, but the membership duration is 14, then the audience size for the last 16 days of the duration window is “0”.

Segment taxonomy ID (Required at orchestration)

The taxonomy ID for a monetized segment in The Trade Desk.

Step 5.

After configuring this destination users may use:

  • Orchestrations to send query results

  • Orchestrations and campaigns to send audiences

  • Orchestrations and campaigns to send offline events