Data Subject Request API Version 1 and 2
Data Subject Request API Version 3
Platform API Overview
Accounts
Apps
Audiences
Calculated Attributes
Data Points
Feeds
Field Transformations
Services
Users
Workspaces
Warehouse Sync API Overview
Warehouse Sync API Tutorial
Warehouse Sync API Reference
Data Mapping
Warehouse Sync SQL Reference
Warehouse Sync Troubleshooting Guide
ComposeID
Warehouse Sync API v2 Migration
Bulk Profile Deletion API Reference
Calculated Attributes Seeding API
Custom Access Roles API
Data Planning API
Group Identity API Reference
Pixel Service
Profile API
Events API
mParticle JSON Schema Reference
IDSync
AMP SDK
Initialization
Configuration
Network Security Configuration
Event Tracking
User Attributes
IDSync
Screen Events
Commerce Events
Location Tracking
Media
Kits
Application State and Session Management
Data Privacy Controls
Error Tracking
Opt Out
Push Notifications
WebView Integration
Logger
Preventing Blocked HTTP Traffic with CNAME
Linting Data Plans
Troubleshooting the Android SDK
API Reference
Upgrade to Version 5
Direct URL Routing FAQ
Web
Android
iOS
Cordova Plugin
Identity
Initialization
Configuration
Event Tracking
User Attributes
IDSync
Screen Tracking
Commerce Events
Location Tracking
Media
Kits
Application State and Session Management
Data Privacy Controls
Error Tracking
Opt Out
Push Notifications
Webview Integration
Upload Frequency
App Extensions
Preventing Blocked HTTP Traffic with CNAME
Linting Data Plans
Troubleshooting iOS SDK
Social Networks
iOS 14 Guide
iOS 15 FAQ
iOS 16 FAQ
iOS 17 FAQ
iOS 18 FAQ
API Reference
Upgrade to Version 7
Getting Started
Identity
Upload Frequency
Getting Started
Opt Out
Initialize the SDK
Event Tracking
Commerce Tracking
Error Tracking
Screen Tracking
Identity
Location Tracking
Session Management
Getting Started
Identity
Initialization
Configuration
Content Security Policy
Event Tracking
User Attributes
IDSync
Page View Tracking
Commerce Events
Location Tracking
Media
Kits
Application State and Session Management
Data Privacy Controls
Error Tracking
Opt Out
Custom Logger
Persistence
Native Web Views
Self-Hosting
Multiple Instances
Web SDK via Google Tag Manager
Preventing Blocked HTTP Traffic with CNAME
Facebook Instant Articles
Troubleshooting the Web SDK
Browser Compatibility
Linting Data Plans
API Reference
Upgrade to Version 2 of the SDK
Web
Alexa
Overview
Step 1. Create an input
Step 2. Verify your input
Step 3. Set up your output
Step 4. Create a connection
Step 5. Verify your connection
Step 6. Track events
Step 7. Track user data
Step 8. Create a data plan
Step 9. Test your local app
Overview
Step 1. Create an input
Step 2. Verify your input
Step 3. Set up your output
Step 4. Create a connection
Step 5. Verify your connection
Step 6. Track events
Step 7. Track user data
Step 8. Create a data plan
Step 1. Create an input
Step 2. Create an output
Step 3. Verify output
Node SDK
Go SDK
Python SDK
Ruby SDK
Java SDK
Introduction
Outbound Integrations
Firehose Java SDK
Inbound Integrations
Compose ID
Data Hosting Locations
Glossary
Migrate from Segment to mParticle
Migrate from Segment to Client-side mParticle
Migrate from Segment to Server-side mParticle
Segment-to-mParticle Migration Reference
Rules Developer Guide
API Credential Management
The Developer's Guided Journey to mParticle
Create an Input
Start capturing data
Connect an Event Output
Create an Audience
Connect an Audience Output
Transform and Enhance Your Data
The new mParticle Experience
The Overview Map
Introduction
Data Retention
Connections
Activity
Live Stream
Data Filter
Rules
Tiered Events
mParticle Users and Roles
Analytics Free Trial
Troubleshooting mParticle
Usage metering for value-based pricing (VBP)
Introduction
Sync and Activate Analytics User Segments in mParticle
User Segment Activation
Welcome Page Announcements
Project Settings
Roles and Teammates
Organization Settings
Global Project Filters
Portfolio Analytics
Analytics Data Manager Overview
Events
Event Properties
User Properties
Revenue Mapping
Export Data
UTM Guide
Data Dictionary
Query Builder Overview
Modify Filters With And/Or Clauses
Query-time Sampling
Query Notes
Filter Where Clauses
Event vs. User Properties
Group By Clauses
Annotations
Cross-tool Compatibility
Apply All for Filter Where Clauses
Date Range and Time Settings Overview
Understanding the Screen View Event
Analyses Introduction
Getting Started
Visualization Options
For Clauses
Date Range and Time Settings
Calculator
Numerical Settings
Assisted Analysis
Properties Explorer
Frequency in Segmentation
Trends in Segmentation
Did [not] Perform Clauses
Cumulative vs. Non-Cumulative Analysis in Segmentation
Total Count of vs. Users Who Performed
Save Your Segmentation Analysis
Export Results in Segmentation
Explore Users from Segmentation
Getting Started with Funnels
Group By Settings
Conversion Window
Tracking Properties
Date Range and Time Settings
Visualization Options
Interpreting a Funnel Analysis
Group By
Filters
Conversion over Time
Conversion Order
Trends
Funnel Direction
Multi-path Funnels
Analyze as Cohort from Funnel
Save a Funnel Analysis
Explore Users from a Funnel
Export Results from a Funnel
Saved Analyses
Manage Analyses in Dashboards
Dashboards––Getting Started
Manage Dashboards
Organize Dashboards
Dashboard Filters
Scheduled Reports
Favorites
Time and Interval Settings in Dashboards
Query Notes in Dashboards
User Aliasing
The Demo Environment
Keyboard Shortcuts
Analytics for Marketers
Analytics for Product Managers
Compare Conversion Across Acquisition Sources
Analyze Product Feature Usage
Identify Points of User Friction
Time-based Subscription Analysis
Dashboard Tips and Tricks
Understand Product Stickiness
Optimize User Flow with A/B Testing
User Segments
IDSync Overview
Use Cases for IDSync
Components of IDSync
Store and Organize User Data
Identify Users
Default IDSync Configuration
Profile Conversion Strategy
Profile Link Strategy
Profile Isolation Strategy
Best Match Strategy
Aliasing
Overview
Create and Manage Group Definitions
Introduction
Catalog
Live Stream
Data Plans
Blocked Data Backfill Guide
Predictive Audiences Overview
Using Predictive Audiences
Predictive Attributes Overview
Create Predictive Attributes
Assess and Troubleshoot Predictions
Use Predictive Attributes in Campaigns
Introduction
Profiles
Warehouse Sync
Data Privacy Controls
Data Subject Requests
Default Service Limits
Feeds
Cross-Account Audience Sharing
Approved Sub-Processors
Import Data with CSV Files
CSV File Reference
Glossary
Video Index
Single Sign-On (SSO)
Setup Examples
Introduction
Introduction
Introduction
Rudderstack
Google Tag Manager
Segment
Advanced Data Warehouse Settings
AWS Kinesis (Snowplow)
AWS Redshift (Define Your Own Schema)
AWS S3 Integration (Define Your Own Schema)
AWS S3 (Snowplow Schema)
BigQuery (Snowplow Schema)
BigQuery Firebase Schema
BigQuery (Define Your Own Schema)
GCP BigQuery Export
Snowplow Schema Overview
Snowflake (Snowplow Schema)
Snowflake (Define Your Own Schema)
Aliasing
Event
Audience
Event
Audience
Feed
Event
Audience
Cookie Sync
Event
Audience
Audience
Audience
Feed
Event
Event
Event
Event
Audience
Event
Data Warehouse
Event
Event
Event
Audience
Event
Feed
Event
Event
Event
Event
Audience
Event
Event
Event
Feed
Event
Event
Audience
Feed
Event
Event
Custom Feed
Event
Data Warehouse
Event
Event
Audience
Audience
Audience
Event
Audience
Event
Event
Event
Event
Event
Audience
Audience
Event
Event
Audience
Data Warehouse
Event
Cookie Sync
Audience
Event
Event
Event
Event
Event
Feed
Feed
Event
Event
Event
Audience
Event
Event
Audience
Event
Event
Event
Feed
Audience
Event
Audience
Event
Audience
Event
Audience
Audience
Audience
Audience
Event
Event
Event
Event
Event
Feed
Event
Event
Event
Event
Event
Feed
Audience
Event
Event
Event
Event
Event
Event
Feed
Event
Audience
Event
Event
Event
Custom Pixel
Feed
Event
Event
Event
Audience
Event
Event
Event
Data Warehouse
Event
Event
Audience
Audience
Audience
Event
Audience
Audience
Audience
Cookie Sync
Event
Feed
Audience
Event
Event
Audience
Audience
Event
Event
Event
Event
Audience
Cookie Sync
Audience
Cookie Sync
Feed
Audience
Event
The Trade Desk provides a self-service platform that enables ad buyers to manage data-driven digital advertising campaigns across various advertising formats, including display, video, and social, across devices.
The The Trade Desk Offline Measurement integration provides an opportunity for advertisers and trusted providers to send offline
conversion events to be used for attribution. Offline conversion events cover a range of use cases like attributing in-store sales or place visits.
To use this integration, you must be sending Commerce or Custom events to an “unbound” feed that you can then connect to The Trade Desk. Learn more about unbound vs. “act-as” feeds here.
Additionally, the following steps must be followed:
The Trade Desk output configuration within mParticle. The only required field is the Advertiser ID.Tracking Tag Id during the connection process, to associate data with your Advertiser ID and the “mparticle” Data Provider. See Tracking Tag Id Generation for more information.Please work with your The Trade Desk Account Manager throughout the set-up process.
For a complete guide on setting up an offline measurement integration, reference The Trade Desk’s documentation.
Data can only be forwarded to The Trade Desk provided at least one of the following identities is present for the given user:
Note: The Trade Desk Cookie Sync IDs are only available if the The Trade Desk Cookie Sync integration has also been set-up.
In order to forward information regarding location, several reserved user attributes are also captured, if present.
An additional connection setting has also been exposed to convey The Trade Desk’s notion of Metro area.
| mParticle Field | The Trade Desk Field | Data Type | Required | Description | Example |
|---|---|---|---|---|---|
| $Country | Country | string |
No | Country. | USA |
| $State | Region | string |
No | Region. | NY |
| $City | City | string |
No | City. | Brooklyn |
| $Zip | PostalCode | string |
No | PostalCode. | 10016 |
| Metro Area Mapping | Metro | string |
No | The user’s metro area. | 501 |
The Trade Desk supports up to 10 attributes per event (TD1 to TD10). These can be mapped from mParticle event or user attributes during connection set-up.
In order for mParticle to forward data to the corresponding Advertiser in The Trade Desk, a unique Tracking Tag ID value is required. It is used to associate incoming data both with the "mparticle" Data Provider, as well as the given Advertiser.
Since it can only be created via API call, a custom UI component exists to create one within the Connection Settings.
To successfully create a new Tracking Tag ID, a unique Tracking Tag Name must be specified.
Once created, the same Tracking Tag ID can be used for connecting the same Output Configuration to other custom feeds.
You can add the following Custom Flag to your events, which will be mapped to The Trade Desk as described below.
| Custom Flag Name | Data Type | Required | Description |
|---|---|---|---|
| TheTradeDesk.ImpressionId | string |
No | This is a valid 360-character GUID for the relevant impression. |
For incoming commerce events, the following additional information is extracted and forwarded to The Trade Desk:
| mParticle Commerce Event Field | The Trade Desk Field | Data Type | Required | Description | Example |
|---|---|---|---|---|---|
ProductAction.TotalAmount |
Value | string |
No | The monetary value associated with this event. | 0.02 |
CurrencyCode |
ValueCurrency | string |
No | The currency associated with the given value. | USD |
The Trade Desk Event Integration uses bulk forwarding. Instead of uploading events in real time, mParticle compiles updates into a queue until a given threshold is reached.
By default, mParticle uploads to The Trade Desk whenever at least one of the following conditions is met:
Upload frequency can be adjusted. Reach out to your mParticle Customer Success Manager if you need to discuss upload frequency.
| Setting Name | Data Type | Default Value | Required | Description |
|---|---|---|---|---|
| Advertiser ID | string |
Yes | The Trade Desk Advertiser ID available on your dashboard. |
| Setting Name | Data Type | Default Value | Platform | Required | Description |
|---|---|---|---|---|---|
| Metro Area Mapping | string |
All | No | Map a mParticle User attribute to the “Metro” area value in The Trade Desk. | |
| Custom Attribute Mapping | string |
All | No | Map mParticle Event or User attributes to attributes within The Trade Desk, with values from “TD1” to “TD10”. | |
| Tracking Tag ID | string |
All | Yes | The Tracking Tag Id allows mParticle to upload data to the given advertiser. It can be generated by clicking on “Create Tracking Tag Id” and entering in a unique Tracking Tag Name. Note: the “mparticle” Data Provider Id must be granted appropriate access within TheTradeDesk. | |
| Tracking Tag Name | string |
All | Required when creating a new Tracking Tag ID. | A unique name which, together with the Advertiser ID and the “mparticle” Data Provider, is used to generate an associated Tracking Tag ID. |