The Trade Desk Conversions
Use warehouse conversion events for Trade Desk measurement and attribution.
Connect this destination to write warehouse conversion events onto The Trade Desk, for use in measurement and attribution. You do not need an audience.
This destination writes to your Trade Desk account and is a good fit when you want to:
- Get measurement and attribution in The Trade Desk
- Use a warehouse table that has conversion events with timestamps
- Provide at least one supported identity or an impression ID
- Send customer opt-out requests to The Trade Desk for a specific merchant
This maps to GrowthLoop Syncs:
| Use it for | Syncs |
|---|---|
| Sending conversion events for measurement and attribution | ✓ |
| Sending customer opt-out requests for a specific merchant | ✓ |
Do not use this workflow to add contacts to a targeting audience. To activate customers for targeting, use The Trade Desk or The Trade Desk CRM. To publish provider-owned segments for other advertisers, use The Trade Desk Marketplace.
Prerequisites
Make sure you have:
- An active The Trade Desk advertiser account with offline conversion access. If you do not have one, contact The Trade Desk here.
- Your Advertiser ID.
- A Platform API key (
TTD-Auth) used to validate access and manage offline tracking tags. - Your offline data provider secret (labeled Advertiser Secret in GrowthLoop). This is the data provider secret for your Offline Data Provider ID, not the advertiser first-party secret from Advertiser Preferences > Seat Identifiers & Keys in The Trade Desk. Obtain it from your Trade Desk Technical Account Manager (TAM) for the provider ID you configure on the destination.
- Your Data Provider ID (optional if GrowthLoop already has a provider ID configured for your organization). Ask your TAM if you are unsure.
- UID2 resolution for your organization if you plan to map email or phone. See UID2 identifiers.
- Your Merchant ID and an API Key with access to the merchant opt-out API, if you plan to send merchant opt-outs.
NoteDo not reuse first-party, CRM, or Marketplace secrets for this destination. GrowthLoop signs offline conversion uploads with the offline data provider secret.
Set up The Trade Desk Conversions as a destination
- In GrowthLoop, click the Destinations tab on the left sidebar.
- Click New Destination on the upper right side.
- Search for The Trade Desk: Offline Conversion and click Add The Trade Desk: Offline Conversion.
- Enter the required information, then click Create.

| Field | Description |
|---|---|
| Destination Name | Name this destination in GrowthLoop. Use a name so your team recognizes its purpose, like "Trade Desk Conversions". |
| Sync Frequency | Set the default sync frequency (for example, daily or weekly). You can override this setting for individual syncs. |
| Advertiser ID | Your Trade Desk advertiser identifier. |
| API Key | Your Trade Desk Platform API key (TTD-Auth) you've created. |
| Advertiser Secret | Enter the data provider secret for your Offline Data Provider ID. This is not the advertiser first-party secret from Advertiser Preferences > Seat Identifiers & Keys in The Trade Desk. The Trade Desk uses this key to validate the TtdSignature HMAC-SHA1 header on POST /providerapi/offlineconversion. Obtain the secret from your TAM for the provider ID entered in Data Provider ID (or the provider ID GrowthLoop has configured for your organization). |
| Data Provider ID | Optional. If you leave this blank, GrowthLoop uses the Trade Desk data provider ID configured for your organization. Your TAM issues the Advertiser Secret for this provider ID. |
| Tracking Tag ID | Optional. GrowthLoop uses this tracking tag when a row does not map its own Tracking Tag ID. |
| Merchant ID | Your Trade Desk merchant identifier. Required for merchant opt-outs unless you map it on the sync. A nonempty value in a source row overrides this default; a blank value uses the default. |
GrowthLoop validates the credentials against The Trade Desk Platform and Offline Conversion APIs. The Trade Desk: Offline Conversion then appears in your list of connected destinations.
Create a sync in GrowthLoop
Create a sync from a warehouse table to write conversion events onto The Trade Desk. See Syncs for information on how to complete those steps.
Select an Object Type:
| Object | Use it for | Recommended update rule |
|---|---|---|
| Offline Conversion | Conversion events and merchant opt-outs | Insert or update |
When you configure the sync:
- Update Rule: Choose Insert or update for this setup, including when a customer's opt-out status changes on an existing source record.
- Dataset/Table: Select the table that holds the records you want to send. Use a stable, unique key for each record. See Keep consent status current when sending merchant opt-outs.
- Connection: Select your The Trade Desk: Offline Conversion destination.
- Object Type: Select Offline Conversion.
- Match Field: Map a stable identity such as
email,uid2,tdid, or another supported identifier.
Each conversion row needs a timestamp and at least one supported identity or impression ID. Re-sending a conversion, including after changing an existing source record or choosing a backfill, can create a duplicate conversion in The Trade Desk.
NoteInsert or update does not update conversion events already sent to The Trade Desk. GrowthLoop adds new conversion events; it does not edit or remove previous events. When you click Run, changed source records can be sent even if Insert only is selected. Do not rely on Insert only to prevent those records from being resent.
Required event fields
| Destination field | Description |
|---|---|
| Timestamp UTC | When the conversion occurred, in UTC. Use ISO 8601 format, for example 2026-07-29T10:00:00Z. Do not use a future time. |
| At least one identity or Impression ID | Include a usable identity on every event. See Supported identities. |
Supported identities
Map at least one of the following. A single row can include more than one identifier. GrowthLoop drops rows with no usable identity and counts them as failed.
| Match field | Description |
|---|---|
| Trade Desk ID (TDID) | The Trade Desk user identifier |
| Device advertising ID (DAID) | Device advertising ID (IDFA or AAID) |
| UID2 | Raw Unified ID 2.0 |
| UID2 token | UID2 in token form |
| Email→UID2 | Email address. GrowthLoop resolves it to a raw UID2 before upload and never sends raw email to The Trade Desk |
| Phone→UID2 | Phone number, preferably E.164. GrowthLoop resolves it to a raw UID2 before upload and never sends raw phone to The Trade Desk |
| Identity Link (IDL) | LiveRamp IdentityLink / RampID-style identifier supported by The Trade Desk offline conversion API |
| EUID / EUID token | European Unified ID and its token form |
| Impression ID | GUID linking the conversion to a Trade Desk impression. Use this when you do not have another user identifier |
GrowthLoop resolves email and phone to UID2 through the UID2 identity service. See UID2 identifiers.
Optional conversion fields
| Destination field | Description |
|---|---|
| Tracking Tag ID | The offline tracking tag that should receive the event |
| Event Name | A label for the conversion event. If you omit it, GrowthLoop defaults to the sync name |
| Value | Monetary value of the conversion |
| Value Currency | Currency code for Value, for example USD |
| Order ID | Order or transaction identifier |
| Merchant ID | Your Trade Desk Merchant ID. A nonempty row value overrides the destination default; a blank value uses that default |
| Merchant Opt-Out | Whether the customer has opted out for this merchant, as a boolean. See Send merchant opt-outs |
| Referrer URL | Referrer URL associated with the conversion |
| Client IP Address | Client IP address associated with the conversion |
| Country | Full country name. If you map Country, also map Region. GrowthLoop rejects rows that include country without region |
| Region | Region or state. Required when you map Country |
| Metro | Metropolitan area geotargeting code |
| City | City name |
| Postal Code | Postal or ZIP code |
| TD1–TD10 | Custom reporting fields, max 64 characters each |
| Privacy Type / Privacy Applicable / Consent String / Privacy Settings | Optional privacy metadata for the conversion event |
See The Trade Desk Offline Conversion API for field definitions.
Send merchant opt-outs
Use the Offline Conversion object to send merchant opt-outs through a sync. Your source data supplies each customer's current opt-out status for the relevant merchant.
Before you start, ask your data team to provide a boolean opt-out column with a value on every row:
| Source value | What happens |
|---|---|
true | GrowthLoop sends a merchant opt-out request instead of a conversion for that row. |
false | GrowthLoop processes the row as a conversion, subject to the normal conversion requirements. It does not skip the row or reverse an earlier opt-out. |
| Blank or invalid | GrowthLoop rejects the row when Merchant Opt-Out is mapped. |
Then configure the sync:
-
Enter your Merchant ID on the destination, or map a Merchant ID column on the sync. Map the column when different rows belong to different merchants.

-
Map a customer identity, such as Trade Desk ID (TDID), UID2, or Email→UID2. Impression ID alone does not identify a customer, so opt-outs do not support it. Keep the Timestamp UTC mapping required by the sync form.
-
Map your opt-out column to Merchant Opt-Out.

-
Choose Insert or update as the Update Rule for this setup.
-
Click Create sync for a new sync or Save changes when editing an existing sync.
-
If prompted, review whether to send existing records. Choosing Backfill can resend historical conversions, including rows marked
false. -
Enable the sync and check Activity for a run. If no run has started, wait for the scheduled run or click Run to start one manually.
GrowthLoop checks the mapping when you save. If the sync has no customer identity, or no Merchant ID on either the sync or the destination, GrowthLoop shows an error and does not save the sync.
Keep consent status current
A customer can opt out without making another purchase. Ask your data team to make sure that a change in opt-out status produces a record the sync can send, even when there is no new purchase.
After a customer opts out, make sure every future record for that customer and merchant reflects their current opt-out status, or exclude their future conversion records from the sync. Sending one opt-out request does not automatically stop GrowthLoop from sending later source records marked false as conversions.
WarningChanging Merchant Opt-Out back to
falsedoes not send a request to opt the customer back in. Ask your TTD TAM about the appropriate process before resuming conversion delivery.
Sync behavior
This is what GrowthLoop writes when you sync conversion events to The Trade Desk.
| Behavior | What happens |
|---|---|
| When it runs | GrowthLoop sends the sync as a batch on the next successful run. |
| Conversion events | GrowthLoop adds conversion events. The sync does not update or remove conversion events already uploaded to The Trade Desk, even when you choose Insert or update. |
| Duplicate-event risk | Re-sending the same event can create duplicate conversions in The Trade Desk. Use unique event keys in your source table. |
| Batching | GrowthLoop uploads conversions in batches of up to 3,000 events, matching The Trade Desk API limits. |
| Rate limits | If The Trade Desk rate-limits an upload, GrowthLoop retries with backoff. |
| Raw PII | When you map Email→UID2 or Phone→UID2, GrowthLoop resolves those values to a raw UID2 before it sends the event. |
| Deletes | GrowthLoop does not delete previously uploaded conversion events. |
| Missing identifier | Rows without the required identifier fail. |
| Merchant opt-out | When Merchant Opt-Out is true, GrowthLoop sends an opt-out request for the row's identity and merchant instead of a conversion. |
| Undoing an opt-out | Changing Merchant Opt-Out to false does not send a request to opt the customer back in. |
Confirm the export was successful
When the run finishes, open Syncs, select your sync, and review Activity for the delivery results, record counts, and any errors.
- Conversion events: Open the tracking tag you configured in The Trade Desk and confirm the latest conversion events.
- Merchant opt-outs: Check that the opt-out records were delivered successfully. TTD does not show merchant opt-outs in conversion reporting. A successful delivery confirms that TTD accepted the request; it does not independently verify that the customer has been removed from targeting.
If your sync sends both conversions and opt-outs, an overall success count can include both. Contact GrowthLoop Support if you need help confirming the opt-out delivery or resolving errors.
This workflow does not create a targeting audience. See Syncs for more information about reviewing your runs.
Congrats on successfully exporting to The Trade Desk Conversions!
Troubleshooting
These are the issues we see most often. You can always email us at [email protected] for help.
| Problem | Cause | Resolution |
|---|---|---|
| Connection fails to validate | Advertiser Secret is the advertiser first-party secret | Use the offline data provider secret from your TAM. |
| Rows fail | Timestamp or identity is missing | Include a timestamp and at least one identity or impression ID on every event. |
| Country rows fail | Region is missing | If you mapped Country, also map Region. |
| Duplicate conversions appear | The same event was sent more than once | Use stable, unique event keys. Review changes and backfills that could resend conversion records. |
| Sync does not save: Merchant ID error | No Merchant ID on the sync or the destination | Map Merchant ID on the sync, or enter it on the destination. |
| Sync does not save: user identity error | Only Impression ID is mapped | Map a customer identity such as TDID or UID2. |
| Opt-outs fail with 403 IncorrectPermissions | The API Key is not authorized to send opt-outs for the specified merchant | Ask your TAM to confirm access for your Merchant ID. If they issue a new key, update API Key on the destination and re-authenticate before retrying the failed delivery. |
Updated 2 days ago
