The Trade Desk Offline

Datafly Signal uploads offline conversions (in-store, call centre, CRM) to The Trade Desk’s Offline Conversion API, so they can be attributed to programmatic impressions. Online conversions belong in The Trade Desk.

Why route The Trade Desk Offline through Datafly Signal

Conversions survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari’s ITP shortens the cookies it can set. Signal sends the conversion from your own server, so the conversions The Trade Desk optimises against are not filtered by the browser.
The clicked impression travels with the conversion. When the conversion came from a visitor who arrived from a Trade Desk ad, Signal sends the impression they clicked through from (captured first-party from the landing URL) as ImpressionId.
One consent decision governs every destination. The Trade Desk is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

Get offline conversions enabled

Ask your Trade Desk account team to enable offline conversions for a data provider ID and to issue a Data API token.

Create an offline tracking tag

Note the tracking tag ID conversions should be attributed to.

Configure in Signal

Configuration Fields

Field	Required	Description
`advertiser_id`	No	Not sent: the Offline Conversion API is scoped by the data provider and tracking tag. Retained for reference.
`merchant_id`	No	Optional merchant ID for retail offline conversions, sent as MerchantId on each item.
`offline_data_provider_id`	Yes	The data provider ID The Trade Desk enabled for offline conversions, sent as DataProviderId.
`api_token`	Yes	The Trade Desk Data API token, sent as the TTD-Auth header.
`tracking_tag_id`	Yes	The offline tracking tag conversions are attributed to, sent as TrackingTagId on each item.

Management UI Setup

Go to Integrations > Add Integration > The Trade Desk Offline.
Choose a preset: Default (default), Retail (ecommerce), Insurance (insurance).
Fill in the fields above and click Save.

Request format

POST https://offlineattrib.adsrvr.org/providerapi/offlineconversion
TTD-Auth: <Data API token>

{"DataProviderId": "<data provider>",
 "Items": [{"TrackingTagId": "abc123x", "TimestampUtc": "2026-09-22T00:13:20Z",
            "TDID": "4d2a9a7e-...", "UID2Token": "...", "OrderId": "ORD-1001",
            "Value": "259.99", "ValueCurrency": "GBP", "EventName": "purchase",
            "LineItems": [{"item_code": "SKU_1", "name": "Parka", "qty": 2, "price": 120, "cat": "Jackets"}]}]}

DataProviderId, and on each item TrackingTagId and TimestampUtc, are required; each item also needs a user ID to match.

Event Mapping

Signal event	Vendor event	Presets
`purchase`	`purchase`	Default, Retail, Insurance
`generate_lead`	`lead`	Insurance

Identity

Items match on the TDID, UID2 or EUID token, or RampID Signal holds for the visitor, or on the impression they clicked through from (ImpressionId, from The Trade Desk’s click-through macros: see Identifiers). No email or phone (raw or hashed) is sent: the API has no field for them, so a record that carries only an email or phone cannot be matched.

The Trade Desk is an advertising destination and requires marketing consent by default.

Troubleshooting

Problem	Solution
`403`	The data provider is not enabled for offline conversions.
`FailedLines` with `MissingOrInvalidTDIDAndImpressionId`	The visitor has no Trade Desk ID; only visitors with a TDID, UID2, EUID or RampID, or a click-through impression ID, can be matched.

Blueprint

The The Trade Desk Offline blueprint version is 0.8.0. It was last reviewed against the vendor’s documentation on 2026-09-22.