Sync offline conversion events from your data warehouse to The Trade Desk so advertisers can attribute real-world outcomes — such as in-store purchases or phone orders — back to programmatic campaigns.

GrowthLoop uploads conversion events to The Trade Desk Offline Conversion API in batches. Each event needs a timestamp, an offline tracking tag, and at least one supported identity (or an impression ID).

📘

Note

Looking for a different Trade Desk integration? See TheTradeDesk for first-party audiences, The Trade Desk CRM for advertiser CRM segments, or The Trade Desk Data Marketplace for provider Marketplace segments.

How it works

• Conversions close the measurement loop. GrowthLoop sends offline events to The Trade Desk so exposure in programmatic campaigns can be attributed to downstream outcomes.
• Tracking tags scope attribution. Each event is associated with an offline tracking tag in The Trade Desk. You can map a Tracking Tag ID from your source table, or use a default tag configured on the destination.
• Identities power matching. Map a Trade Desk identity such as TDID, DAID, UID2, EUID, Identity Link (IDL), or Impression ID. You can also map email or phone and have GrowthLoop resolve them to a raw UID2 before upload.
• Raw email and phone never leave GrowthLoop. When you map Email→UID2 or Phone→UID2, values are resolved to a raw UID2 before the event is sent. Personal data is not included in the Trade Desk payload.
• Insert-only syncs. GrowthLoop adds new conversion events. Syncs do not remove previously uploaded conversions.

Supported objects

GrowthLoop enables syncing to the following The Trade Desk object:

Prerequisites

• An active The Trade Desk advertiser account with offline conversion access. If you don't have one, get in touch with 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 UI. The Trade Desk uses this key to validate the TtdSignature HMAC-SHA1 header on POST /providerapi/offlineconversion. 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.
• If you plan to map email or phone, UID2 resolution must be configured for your organization so GrowthLoop can resolve those values to raw UID2s before upload.

📘

Note

Do not reuse first-party, CRM, or Marketplace secrets for this destination. Offline conversion uploads are signed with the offline data provider secret.

Set up destination

1. Log into GrowthLoop and click the Destinations tab on the left sidebar.
2. Click New Destination on the upper right side.
3. Search for The Trade Desk: Offline Conversion in the destination modal and click Add The Trade Desk: Offline Conversion.
4. Enter the required information in the modal:

1. Destination Name: How the destination is named and referred to in the app going forward.
2. Sync Frequency: How often conversion events sync to this destination by default. You can override this setting for individual syncs.
3. Advertiser ID: Your Trade Desk advertiser identifier.
4. API Key: Your Trade Desk Platform API key (TTD-Auth).
5. 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 UI. The Trade Desk uses this key to validate the TtdSignature HMAC-SHA1 header on POST /providerapi/offlineconversion. Obtain the secret from your TTD Technical Account Manager for the provider ID entered in Data Provider ID (or the provider ID GrowthLoop has configured for your organization).
6. Data Provider ID: Optional. If blank, GrowthLoop can fall back to the configured Trade Desk data provider ID for your organization. Your TAM issues the Advertiser Secret for this provider ID.
7. Click Create.

When you click Create, GrowthLoop validates the credentials against The Trade Desk Platform and Offline Conversion APIs. You should now see The Trade Desk: Offline Conversion in your list of connected destinations.

Set up a sync

1. Click the Syncs tab on the left sidebar.
2. Click Create Sync on the upper right side.
3. Configure your sync:
   1. Name: A friendly name for the sync.
   2. Sync frequency: How often conversion events sync. Options typically include 15 minutes, 30 minutes, hourly, and daily.
   3. Update Rule: Choose Insert only. This destination adds new conversion events and does not update or remove previously uploaded conversions.
   4. Dataset/Table: The table that holds your conversion events.
   5. Dataset Unique Field(s): The column(s) that uniquely identify each conversion event in the table.
   6. Match Field: The column used to match rows from your source table. Choose a stable identity such as email, uid2, tdid, or another supported identifier.
   7. Connection: Select your The Trade Desk: Offline Conversion destination.
   8. Object Type: Select Offline Conversion.
   9. Match Field (destination): Select the corresponding destination identity field.
4. Click Save Route.
5. Map the fields required for each conversion event, then activate the sync.

📘

Note

GrowthLoop prompts you to map Timestamp UTC, plus at least one identity field or Impression ID. If you map Country, you must also map Region.

Field mappings

Required

Supported identities

Map at least one of the following. A single row can include more than one identifier. Rows with no usable identity are dropped and counted as failed.

📘

Note

Email and phone are resolved to a raw UID2 through the UID2 identity service. If you plan to map these fields, make sure UID2 resolution is configured for your organization.

Common optional fields

Good to know

• Insert only: Re-sending the same conversion can create duplicate events in The Trade Desk. Use unique event keys in your source table and an insert-only sync.
• Tracking tags: Events must include a tracking tag. Map Tracking Tag ID when you need per-row control.
• Event naming: If Event Name is not mapped, GrowthLoop sends the sync name.
• Country and region: Mapping Country without Region causes those rows to be rejected.
• Timestamps: Convert warehouse timestamps to UTC before syncing. GrowthLoop normalizes common ISO-like formats for The Trade Desk.
• Batch uploads: 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.

---

You've successfully connected The Trade Desk Offline Conversion destination and created your first conversion sync!

📘

Note

Experiencing any issues connecting to or syncing The Trade Desk Offline Conversions? Reach out to us at [email protected] and we'll be in touch shortly to help resolve the matter.