This article outlines recommendations and notes certain limitations imposed by the data source API, which you may need to consider when building your queries.
If you’re connecting to The Trade Desk, follow the instructions in our connection guide. See The Trade Desk metrics and dimensions for the fields available in this data source.
Request limits and recommended refresh window
Request limit: See The Trade Desk documentation.
Recommended refresh window: 2-3 days
Historical range
Supermetrics supports the last 180 days from the first client login. For example, if you connect The Trade Desk to Supermetrics for the first time on January 1, 2022, the oldest date you can pull data from is 180 days before that. This will stay the same for as long as you use this connector. Note that The Trade Desk API can only pull data created on or after June 20, 2017.
Accounts in The Trade Desk
In the The Trade Desk connector, each Advertiser account is considered a separate account within the connection.
Your Supermetrics subscription determines how many data source accounts you can use simultaneously.
Things to consider
Slow performance on large reports
The Trade Desk APIs are slow to generate client reports. In some cases, if you have a large number of active advertisers generating data, The Trade Desk may be unable to generate reports at all.
Report preparation delays
Supermetrics imports the reports from The Trade Desk. The time required to prepare different reports may vary. It requires some time to wait for imports to be ready for the whole possible period. Estimated preparation time is 1 day per user.
Excluded reports and metrics
Some of The Trade Desk reports don’t support date ranges older than 90 days. To avoid struggles to find the correct combination of metrics and dimensions for the time range, we exclude many of the default available templates and include only metrics that safely work with the full date range. This is to ensure that your queries don’t fail because of one metric that doesn’t support the date range.
Time zone errors
You may see an error like:
Error: Failed to fetch the reports. Most likely you have not logged in with the requested time zone. Time zones imported for this partner: UTC. Please try to re-authenticate. If the problem remains, please contact our support.
This means that one or more of the advertiser accounts uses a different time zone than the one they originally set during the login process.
To fix this, you need to go through the login process again and select the correct time zone for the advertiser.
If you have multiple advertisers in different time zones, you need to repeat the login process for each time zone used.
For example, if you have 3 advertisers, each in their own time zone, under the same user login, you need to log in 3 separate times, selecting the needed time zone each time until all have been covered.
Today’s data and historical range
Today’s data isn’t available in the connector. No data is returned for today, but there is no error, as it’s expected behavior. New data is fetched daily when a new day starts. Note that the "new day" is based on the time zone selected at user login.
You can’t request data that’s older than 180 days from the initial login date.
This means that after about 6 months since the first use of the connector, you can fetch 1 year of data.