Ellipse Gradient for Header

The Trade Desk Integration Guide

Connect The Trade Desk partner APIs with enterprise planning, marketing, finance, and analytics systems through secure, orchestrated workflows.

The Trade Desk integration options at a glance

The Trade Desk provides partner-facing REST APIs for advertisers, campaigns, ad groups, creatives, audience segments, and reporting. OAuth 2.0-style bearer-token authentication controls access according to partner permissions. Reporting is commonly asynchronous: a client submits a report request, stores its identifier, polls for completion, and retrieves the result. General-purpose webhooks, SOAP, GraphQL, direct database access, and broad bulk operations were not confirmed. Martini can consume the REST APIs, manage protected configuration, orchestrate scheduled and multi-step workflows, paginate through resources, transform JSON or report output, and load results into databases, files, analytics platforms, or internal APIs.

Integration pointSupported by The Trade Desk?Common use casesHow Martini supports it
REST APIsYesRetrieve and manage advertisers, campaigns, ad groups, creatives, audience segments, and reporting resources where the partner account has permission.Martini can consume The Trade Desk REST APIs, map responses, paginate through resources, and expose reusable internal APIs or workflows.
AuthenticationYesOAuth 2.0-style access tokens authenticate approved partner API clients and restrict access to permitted advertisers and resources.Martini can keep client credentials in secrets or environment configuration, acquire bearer tokens, and apply authorization headers without embedding secrets in workflows.
Bulk / async / batch APIsLimitedAsynchronous report generation is supported; broad bulk behavior for campaigns, audiences, or other resources must be verified per endpoint and entitlement.Martini can submit report jobs, persist report identifiers, schedule polling, enforce timeouts, and process completed results with retry handling.
File / attachment APIsLimitedReport results may be available as downloadable or structured output, but a general-purpose attachment API was not confirmed.Martini can parse returned JSON or delimited data and write transformed results to files, object storage, databases, or downstream APIs.
Webhooks / outbound callbacksNot confirmedA general-purpose public webhook or callback mechanism for campaign, creative, audience, or delivery changes was not confirmed.Martini should use scheduled retrieval and report polling unless an account-specific callback facility is separately verified.
GraphQL APIsNot confirmedNo official The Trade Desk GraphQL API was confirmed in the reviewed partner documentation.Martini integrations should use the confirmed REST APIs rather than assume GraphQL availability.
SOAP APIsNot confirmedNo official The Trade Desk SOAP API was confirmed.Martini should be designed around REST unless The Trade Desk provides a private or account-specific SOAP interface.
Database / analytics accessNot confirmedNo direct SQL interface or vendor-provided analytics database connection was confirmed.Martini can consume reporting APIs and load normalized results into customer-managed platforms such as Snowflake, BigQuery, Databricks, or relational databases.

How The Trade Desk exposes data and business events

The Trade Desk REST APIs

The Trade Desk’s primary confirmed integration mechanism is its partner-facing REST API. It supports access to advertising resources such as Advertisers, Campaigns, AdGroups, Creatives, AudienceSegments, and Reports, subject to partner permissions and API version.

Martini implementation pattern

Martini implementation pattern: Martini obtains an OAuth 2.0-style bearer token, calls the relevant REST endpoint, follows pagination, validates the response, maps vendor fields to a canonical model, and sends the result to a target system or reusable internal API.

Implementation sequence

Acquire an OAuth access token
Retrieve the permitted Advertisers
Request Campaigns, AdGroups, Creatives, or AudienceSegments
Follow pagination until all pages are processed
Map and validate the response
Upsert the result using stable vendor identifiers

The Trade Desk asynchronous reporting

The Trade Desk supports asynchronous report generation. A client submits a report request and later retrieves the generated result rather than relying on a single synchronous response.

Martini implementation pattern

Martini implementation pattern: a workflow submits the report definition, stores the report identifier and extraction metadata, uses a scheduler or delayed execution to poll status, retrieves the completed report, transforms the output, and persists processing state.

Implementation sequence

Authenticate with The Trade Desk
Submit the report request
Store the report identifier and request parameters
Poll for report completion on a controlled schedule
Retrieve the completed report result
Validate and transform the report data»,

The Trade Desk report result processing

Report results may be returned as structured or downloadable output. A general-purpose file or attachment API was not confirmed, so the result format and retrieval behavior should be verified for the selected report operation.

Martini implementation pattern

Martini implementation pattern: Martini parses the returned JSON or delimited result, validates required dimensions and metrics, partitions data by advertiser and reporting period, and loads it into a warehouse, database, file store, or analytics API.

Implementation sequence

Retrieve the completed report output
Detect and parse the returned format
Validate dimensions, metrics, and reporting period
Apply canonical field mappings
Write the result to the target platform
Store a checksum and completion status

Common The Trade Desk integration patterns

Pattern 1: Synchronize campaigns and ad groups

When to use this pattern

Use this pattern when an internal planning, finance, or campaign-management system needs current The Trade Desk configuration. The workflow can also support approved reverse-direction updates, but create and update operations must be verified for the partner account before implementation.

Integration direction
The Trade Desk
Martini
Campaign management system
Example Mapping
The Trade Desk FieldCanonical FieldTarget Field
AdvertiserIdadvertiserExternalIdadvertiser_id
CampaignIdcampaignExternalIdcampaign_id
CampaignNamecampaignNamename
BudgetcampaignBudgetbudget
Martini implementation pattern

A scheduled Martini workflow authenticates, retrieves permitted Advertisers, follows pagination for Campaigns and AdGroups, maps configuration into a canonical model, validates required fields and status values, and performs idempotent upserts. Transient failures are retried with controlled backoff, while authorization and validation failures are routed for investigation.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination handling
  • data mapping
  • business rules
  • error handling
  • retry processing

Pattern 2: Load advertising performance reports

When to use this pattern

Use this pattern when finance, marketing, or analytics teams need repeatable spend, delivery, and performance data in a warehouse or reporting platform.

Integration direction
The Trade Desk
Martini
Snowflake
Example Mapping
The Trade Desk FieldCanonical FieldTarget Field
ReportIdsourceReportIdreport_id
AdvertiserIdadvertiserExternalIdadvertiser_id
ReportDateactivityDatereport_date
SpendmediaSpendspend
Martini implementation pattern

Martini submits an asynchronous report request, stores the report ID, date range, advertiser scope, and report type, then polls with a scheduler until completion or timeout. The completed result is validated, transformed, partitioned, and loaded using a composite idempotency key such as report ID, period, advertiser, and report type. Failed jobs enter a retry or dead-letter path.

Martini capabilities used
  • workflow orchestration
  • scheduler triggers
  • API consumption
  • state tracking
  • data transformation
  • idempotent loading
  • error handling

Pattern 3: Govern creatives and audience segments

When to use this pattern

Use this pattern when advertising operations teams need to identify missing creative metadata, inactive resources, orphaned objects, or audience usage that violates internal policy.

Integration direction
The Trade Desk
Martini
Governance database
Example Mapping
The Trade Desk FieldCanonical FieldTarget Field
CreativeIdcreativeExternalIdcreative_id
CreativeStatuslifecycleStatusstatus
AudienceSegmentIdaudienceExternalIdaudience_segment_id
CampaignIdrelatedCampaignIdcampaign_id
Martini implementation pattern

A Martini workflow retrieves Creatives and AudienceSegments, enriches them with campaign relationships, applies required metadata and policy rules, and writes compliance findings to a database or internal API. It records source timestamps and avoids modifying vendor resources unless the relevant operation and permissions are confirmed.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • data mapping
  • validation
  • business rules
  • database integration
  • audit logging

Pattern 4: Consolidate media data with business outcomes

When to use this pattern

Use this pattern when organizations need to combine The Trade Desk delivery and spend data with customer, opportunity, revenue, or attribution data from other enterprise applications.

Integration direction
The Trade Desk
Martini
Salesforce
Analytics warehouse
Example Mapping
The Trade Desk FieldCanonical FieldTarget Field
CampaignIdcampaignExternalIdcampaign_id
AdvertiserIdadvertiserExternalIdadvertiser_id
SpendmediaSpendmarketing_spend
ReportDateactivityDatedate
Martini implementation pattern

Martini retrieves completed The Trade Desk reports, retrieves matching campaign or opportunity data from the adjacent system, joins records through governed identifiers or mapping tables, applies reconciliation and null-handling rules, and publishes the combined model. Duplicate loads and partial-source failures are tracked independently so a rerun does not double count results.

Martini capabilities used
  • multi-system orchestration
  • API consumption
  • data mapping
  • business rules
  • record matching
  • idempotency
  • monitoring

Applications commonly integrated with The Trade Desk

The Trade Desk data is commonly combined with marketing, analytics, customer, finance, and cloud data platforms. These integrations should be validated against the customer’s API permissions, reporting entitlements, and target-system requirements; a direct native relationship is not implied unless documented.

Application Scenario Direction Martini Pattern
Salesforce Connect advertising spend and campaign activity with leads, opportunities, and revenue outcomes for attribution and marketing analysis. The Trade Desk → Martini → Salesforce Martini retrieves campaign and report data, maps advertiser and campaign identifiers to Salesforce or an intermediate attribution model, applies reconciliation rules, and writes approved updates through the target system’s API.
Snowflake Centralize The Trade Desk performance, spend, delivery, and audience-related reporting with broader marketing and business data. The Trade Desk → Martini → Snowflake A scheduled Martini workflow submits reports, polls for completion, transforms results into warehouse tables, performs idempotent upserts, and records extraction metadata and failures.
Google BigQuery Store large advertising report datasets for analysis, modeling, and scheduled business reporting. The Trade Desk → Martini → Google BigQuery Martini retrieves completed reports, validates advertiser and date dimensions, partitions transformed output by reporting period, and loads it through the customer’s BigQuery integration.
Databricks Combine media-delivery data with attribution, customer, and machine-learning datasets. The Trade Desk → Martini → Databricks Martini extracts incremental report windows, normalizes metrics and identifiers, applies schema validation, and publishes data to Databricks or an approved cloud-storage landing zone.
Adobe Experience Platform Combine advertising activity with customer profiles, conversions, and activation data. The Trade Desk → Martini → Adobe Experience Platform Martini synchronizes governed campaign and performance data, maps identifiers to the Adobe data model, applies consent and scope rules, and sends accepted payloads to Adobe APIs.
Amazon S3 Land report files or transformed advertising extracts in cloud object storage for downstream processing and retention. The Trade Desk → Martini → Amazon S3 Martini submits and retrieves reports, converts structured or delimited results as required, writes partitioned objects to Amazon S3, and stores checksums and processing status.
NetSuite Reconcile approved advertising spend or campaign costs with finance and accounting processes. The Trade Desk → Martini → NetSuite Martini aggregates validated report data by advertiser and accounting period, applies reconciliation rules, and sends approved summaries to NetSuite through its supported API.

How to build a The Trade Desk integration in Martini

Objective

Establish approved partner access to The Trade Desk and configure OAuth credentials without exposing secrets in workflow definitions or logs.

Instructions in Martini

  • Confirm partner onboarding, advertiser access, API client registration, and permitted operations with The Trade Desk
  • Store client credentials and environment-specific values in Martini secrets or secure configuration
  • Configure token acquisition and bearer-token authorization
  • Separate authentication failures from transient API failures

Objective

Select a schedule or controlled API invocation based on whether the integration synchronizes resources, submits reports, or processes completed report jobs.

Instructions in Martini

  • Use a scheduled workflow for synchronization and report polling
  • Use an API-triggered workflow when an internal application needs controlled access to The Trade Desk operations
  • Avoid assuming campaign or creative webhook events are available
  • Define polling frequency, maximum attempts, and timeout behavior

Objective

Call the appropriate The Trade Desk REST operation and handle resource scope, pagination, and asynchronous report state.

Instructions in Martini

  • Retrieve permitted Advertisers before dependent resources where required
  • Follow pagination for Campaigns, AdGroups, Creatives, and AudienceSegments
  • Submit report requests and persist report identifiers
  • Poll report status until completion, failure, or timeout

Objective

Coordinate authentication, dependent API calls, state management, transformation, destination writes, and failure paths as a maintainable Martini workflow.

Instructions in Martini

  • Separate discovery, retrieval, transformation, and destination stages
  • Persist extraction metadata and report state for restartability
  • Control concurrency and avoid unnecessary polling
  • Route invalid requests, authorization failures, throttling, and destination errors separately

Objective

Convert The Trade Desk resources and report output into a canonical model appropriate for downstream applications and analytics platforms.

Instructions in Martini

  • Map stable vendor identifiers to external keys
  • Normalize dates, metrics, statuses, and advertiser relationships
  • Handle null, absent, unknown, and newly introduced fields deliberately
  • Partition large report outputs by advertiser and reporting period where appropriate

Objective

Validate data quality, governance requirements, reconciliation totals, and write-back permissions before changing downstream or vendor data.

Instructions in Martini

  • Validate required identifiers, dimensions, metrics, and status values
  • Apply creative and audience governance rules
  • Use idempotency keys for resource upserts and report loads
  • Verify create or update permissions before enabling reverse-direction changes

Common The Trade Desk data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
AdvertisersIdentify the advertising accounts and organizational scope available to the authenticated partner.Planning platforms, finance systems, data warehouses, and internal APIsMartini retrieves permitted Advertisers, maps stable identifiers, caches relatively static metadata where appropriate, and uses the identifiers to scope downstream workflows.
CampaignsRepresent campaign-level buying configuration, objectives, budgets, dates, and targeting settings.Campaign-management platforms, Salesforce, data warehouses, and finance systemsMartini retrieves or conditionally updates Campaigns, maps fields to a canonical model, applies permission and validation rules, and performs idempotent upserts.
AdGroupsDefine more granular buying units, including targeting, inventory, pacing, and bid-related configuration.Planning systems, governance databases, analytics platforms, and internal APIsMartini processes AdGroups incrementally, preserves parent Campaign and Advertiser relationships, validates status and targeting values, and routes failures for review.
CreativesStore advertising assets and metadata used by campaigns and ad groups.Creative governance systems, approval workflows, databases, and analytics platformsMartini retrieves Creatives, checks required metadata and policy rules, detects inactive or orphaned items, and publishes exceptions or approved data.
AudienceSegmentsReference audience definitions or segments used for targeting and activation.Audience governance platforms, Adobe Experience Platform, databases, and internal APIsMartini synchronizes permitted AudienceSegments, maps segment identifiers, applies governance rules, and only performs mutations where the API operation and permissions are confirmed.
ReportsRepresent asynchronous report jobs and results containing delivery, spend, performance, and related advertising metrics.Snowflake, Google BigQuery, Databricks, Amazon S3, finance systems, and reporting platformsMartini submits report requests, stores identifiers and parameters, polls for completion, validates output, prevents duplicate loads, and writes normalized results.

Authentication and security considerations

OAuth-based partner access

The Trade Desk APIs use OAuth 2.0-style access tokens for approved API clients. Access is controlled by partner account permissions and may be limited to specific advertisers, resources, and operations.

Credential protection

Store client credentials and tokens in Martini secrets or secure environment configuration. Do not embed credentials in workflow definitions, mappings, source control, or operational logs.

Scope and token handling

  • Confirm client registration, token lifetime, advertiser access, and reporting entitlements with The Trade Desk.
  • Reuse tokens until expiration where appropriate and reacquire them when required.
  • Do not log bearer tokens or sensitive request content.
  • Separate unauthorized responses from transient server and network failures.

Operational considerations for The Trade Desk integrations

Rate limits and concurrency

Quotas may vary by account, endpoint, API version, and partner status. Use controlled concurrency, bounded exponential backoff, retry limits, and scheduling that avoids unnecessary polling.

Pagination and volume

Do not assume that one response contains all Advertisers, Campaigns, AdGroups, Creatives, or AudienceSegments. Preserve page state, process incrementally, and use stable identifiers for restartable upserts.

Asynchronous reporting

Store the report identifier, request parameters, date range, advertiser scope, submission time, poll count, status, and processing result. Add timeout and dead-letter paths for reports that remain incomplete.

Idempotency and schema changes

Use vendor identifiers as external keys and composite keys for report loads. Validate required fields, handle null and absent values, and version mappings when statuses, enumerations, or downstream schemas change.

Testing and observability

Test representative advertisers, resource permissions, pagination, empty results, large reports, throttling, authentication failures, and destination errors. Log correlation identifiers, endpoint names, resource scopes, and report identifiers without exposing secrets.

Why use Martini instead of scripts or point-to-point integrations?

Orchestrated integration logic

Martini coordinates token acquisition, dependent REST calls, pagination, asynchronous report polling, transformation, target writes, and failure paths in workflows rather than scattering behavior across scripts.

Reusable and maintainable assets

Teams can centralize mappings, validation, business rules, authentication configuration, and report-processing logic. Martini can also expose controlled APIs that abstract The Trade Desk operations for internal applications.

Reliable data movement

Scheduled execution, state tracking, idempotent processing, bounded retries, and operational monitoring provide a stronger foundation for campaign synchronization and high-volume reporting than isolated point-to-point scripts.

Flexible enterprise delivery

Martini can transform The Trade Desk data and deliver it to databases, files, warehouses, analytics platforms, or other APIs while preserving the option to add custom logic when vendor-specific rules require it.

Frequently asked questions

How can The Trade Desk be integrated with enterprise systems?

The Trade Desk can be integrated through its partner-facing REST APIs using OAuth 2.0-style bearer-token authentication. Enterprise workflows can retrieve Advertisers, Campaigns, AdGroups, Creatives, AudienceSegments, and Reports, submit asynchronous report jobs, poll for completion, and load transformed results into databases, warehouses, files, analytics platforms, or internal APIs.

Can Martini integrate with The Trade Desk?

Yes. Martini can consume The Trade Desk REST APIs, manage protected OAuth configuration, orchestrate campaign and reporting workflows, paginate through resources, transform results, and synchronize data with enterprise applications. A native Martini connector was not confirmed, so the integration is implemented through the vendor’s confirmed API mechanisms.

Do I need a connector to integrate The Trade Desk with Martini?

No. A dedicated The Trade Desk connector is not required. Martini can integrate using The Trade Desk’s confirmed REST APIs and OAuth-style authentication, with scheduled workflows for synchronization and asynchronous report polling.

Is there any extra Lonti cost to integrate The Trade Desk with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate The Trade Desk. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from The Trade Desk, cloud infrastructure, data warehouses, or other third-party services based on subscription, usage, and deployment model.

Which The Trade Desk integration methods should architects use?

The confirmed primary method is the partner-facing REST API. OAuth 2.0-style bearer tokens should be used for authentication, and asynchronous reporting should be implemented with request submission, stored report identifiers, polling, and result retrieval. GraphQL and SOAP APIs were not confirmed, and broad bulk behavior should be verified per endpoint.

Does The Trade Desk provide webhooks or callbacks for campaign changes?

A general-purpose public webhook or outbound callback mechanism was not confirmed. Integrations should use scheduled REST retrieval and report polling unless The Trade Desk separately verifies an account-specific callback facility.

How does Martini synchronize The Trade Desk data?

Martini can run scheduled workflows that authenticate, retrieve permitted resources, follow pagination, map data to a canonical model, apply validation and governance rules, and perform idempotent writes to target systems. For reports, Martini stores the report request state and polls until the result is complete.

How are errors, retries, and duplicate The Trade Desk loads handled?

Martini can classify authentication, authorization, validation, rate-limit, transient, asynchronous-report, transformation, and destination failures. Workflows can apply bounded retries with backoff for transient conditions, preserve report and page state, use stable vendor identifiers for upserts, and use report ID, period, advertiser, and report type to prevent duplicate loads.

Related Martini documentation

API integration

Workflows

Data processing

Security

Reliability

Connect The Trade Desk with Martini

Use Martini to build secure, maintainable workflows around The Trade Desk REST APIs, asynchronous reporting, campaign data, audience governance, and enterprise analytics delivery.

EXPLORE MARTINI
BOOK A DEMO