Skip to main content

​
Introduction

The Trade Desk: My Report is a custom-report variant of The Trade Desk connector. Instead of running live GraphQL queries, it ingests the CSV exports produced by The Trade Desk’s built-in MyReports scheduler. Whatever columns are configured in the linked report are surfaced in Adriel, including ad-level (creative) data and custom-conversion metrics that the standard Trade Desk connector cannot expose. Because the data shape comes from the report itself, this connector has no fixed catalog of metrics or breakdowns. The report is scheduled inside The Trade Desk, the schedule is linked to Adriel, and the report’s columns become the available fields after each sync. This connector is currently in beta. As a marketing connector, metrics, breakdowns, and currency are standardized so widgets can aggregate alongside other ad-platform sources without additional configuration. To connect this data source, see How to connect The Trade Desk: My Report to Adriel.

​
Data refresh strategy

​
Architecture data

There is no fixed hierarchy or architecture tree to refresh. Account selection at connection time delegates to the standard Trade Desk connector’s advertiser lookup, so the same authorized advertiser list is available. Everything below that level is driven by the report’s own columns.

​
Reports data

This is a simple-file-cache connector backed by CSV exports. Dashboard queries are served from a per-asset cache rather than fetched live on each load.
  • Latest export only (default) — on each refresh, the newest completed export for the linked schedule is imported and replaces the previously cached rows. The data in Adriel therefore covers the date range of the latest export, including on first connection.
  • Keep All Executions — when this option is turned on at connection time, every downloadable export for the schedule is imported and kept. If the exports’ date ranges overlap, the same rows can appear more than once, so this option works best when each export covers a separate period, such as a report that exports the previous day.
  • Refresh schedule — the scheduler is checked twice daily at 06:00 UTC and 13:00 UTC. Workers run one job at a time.

​
Architecture levels

The My Report connector has no fixed hierarchy. The data shape comes from the columns selected in the report itself: adding a column in The Trade Desk makes the corresponding field appear in dashboards after the next sync, and removing a column empties the corresponding field. Account-list resolution delegates to the standard Trade Desk connector’s advertiser lookup.

​
Metrics

How to read the columns Data type uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean. API Key in code style like impressions is a literal platform field name. Italic text describes how a value is produced when it does not map to a single fixed field — for the My Report connector, most fields are discovered from the report’s own columns.
The metric set is not fixed. Every numeric column included in the linked report is exposed as a metric, and field names mirror the report’s column names. Adding or removing a column in The Trade Desk is the supported way to change the available metrics; the change takes effect after the next sync.

​
Breakdowns

​
Report-defined breakdowns

The breakdown set is not fixed. Every grouping column included in the linked report — such as campaign, ad group, creative, or a custom segment — is exposed as a breakdown, and field names mirror the report’s column names.

​
Limitations

  • Schema follows the report, not the connector — the metric and breakdown set are read from the columns of the linked report. Adding or removing a column in The Trade Desk is the supported way to evolve the schema, and changes take effect only after the next sync.
  • A date column is required — the report must include a date column, even though the connector does not partition data by date. A report without one fails to import.
  • No date-range grouping — the connector does not partition by date (hasDateBreakdown is false), so Adriel time-grouping views such as daily, weekly, or monthly are not applied to this source. Date behavior depends on the report’s own date column.
  • Date range follows the exports — Adriel does not cap the date range. By default, the data covers only the date range of the latest export, so a report scheduled with a short range, such as the previous day, shows only that period. To keep a longer history, widen the report’s date range in The Trade Desk, for example to the last 90 days, or turn on Keep All Executions when connecting.
  • Single-export size limit — a single export larger than approximately 400 MB may fail to import. Splitting one large schedule into narrower schedules, for example by date or advertiser, is the recommended workaround.
  • CSV exports only — the connector imports CSV exports only. Other formats, such as Excel (.xlsx or .xls), are not supported at any file size, and schedules that export in a non-CSV format cannot be selected when connecting. After the report’s file format is changed to CSV in The Trade Desk, the schedule becomes selectable once a CSV export has been generated. A data source already linked to a non-CSV schedule imports no data; after switching the report to CSV, connect the schedule again as a new data source.
  • Account list shared with the standard connector — advertiser selection delegates to the standard Trade Desk connector’s advertiser lookup, so the same authorized advertisers appear in both connectors.

​
API references

  • The Trade Desk MyReports — programmatic DSP; reports are scheduled in the MyReports interface
  • The Trade Desk MyReports REST API base URL: https://api.thetradedesk.com/v3/myreports (authenticated with the TTD-Auth header, the same API token as the standard Trade Desk connector)

​
See also