Upload offline conversion events

Offline conversions are late, batched conversion data, such as in-store sales, place visits, or custom events. If your conversion data lives in Snowflake or Databricks, use the respective TTD Connector. Otherwise, send data through the Data API SDK (recommended) or directly with the Offline Conversion Events API.

NOTE: If you are a location data provider, see Product catalog for location data providers. Location-based catalogs use the SKU ID, product name, brand, description, and category fields to represent locations and geographic groups.

Use Snowflake connector

/doc/DataSnowflakeNativeAppConversions

Send batched conversion data from Snowflake. No custom pipeline needed.

Method: Snowflake connector

Use this when: Your offline conversion data lives in Snowflake.

Use Databricks connector

/doc/DataDatabricksConnectors

Send batched conversion data from Databricks. No custom pipeline needed.

Method: Databricks connector

Use this when: Your offline conversion data lives in Databricks.

Use Data API SDK

/doc/DataAPISDK

Send offline conversion data through a simplified Python SDK.

Method: Data API SDK

Use this when: You want to reduce the time, effort, and complexity of integrating with The Trade Desk.

Use the API

/doc/DataOfflineMeasurement

Send batched conversion data through the Offline Conversions Events API.

Method: Offline CAPI · REST

Use this when: Your offline data is stored outside Snowflake or Databricks.