Teads API

Description

‍Teads combines the strength of quality media, data, and creativity to deliver sustainable business outcomes.

Setup guide

Follow our setup guide to connect Teads to Improvado.

1‍Step 1. Click the Make a new Connection on the Connections page.
Categories on the Data sources page group all available platforms. Use a search to find the required one.

2‍Step 2. Click on the Teads API tile.

3To authorize your account you need to fill in the required fields below following steps 3.1 - 3.5:

• API key
• Name
• Timezone

3.1Log in to Teads platform.

3.2‍Step 3.2. Select the Seat you wish to generate an API key for.

3.3‍Step 3.3. Open Settings.

3.4‍Step 3.4. Go to Manage API keys and click Generate API key.

3.5Enter copied values into the Improvado authorization form.

4‍Step 4. After the connection process is completed successfully, the Teads API connection will appear in your Connected sources list.

5‍Step 5. When the connection status is Active, and the account status column shows a number of accounts, you can move on to data extraction.

6To extract data from the connected sources, check the instruction on how to set up data extraction.

Schema information

The schema information shows all report types you can use to extract data from Teads API.

Limits

75 report runs per 24 hours

Teads caps report generation at 75 runs in any 24-hour period, counted at the Teads account level, not per extraction order. Improvado submits one run per report request, so several orders extracting in parallel on the same Teads credential, or a wide backfill split into chunks, draw on one allowance.

This is the usual explanation for a Teads backfill that starts briskly and then stops. Once the allowance is gone Teads refuses further report runs, and an extraction that keeps meeting that refusal retries a few times and then ends with a quota error rather than waiting for the window to roll forward. Historical loads are best done in stages, and it is worth keeping a large backfill off the same day as the scheduled extractions on the same connection.

Extract reach at the granularity you report on

Teads Reports supports day, week, month and quarter granularity. For ordinary metrics the choice is a convenience — impressions and spend add up the same way whichever you pick.

Reach metrics such as Unique Viewers do not behave that way. They count people, and the same person reached on two days is one unique viewer, not two. Summing daily unique viewers into a month or a quarter overstates reach, sometimes badly, and there is no way to correct it afterwards because the overlap is not in the data.

So if you report reach quarterly, extract it at quarter granularity. If you need both daily delivery and quarterly reach, that is two extractions at two granularities rather than one that gets rolled up.

Release notes

You can find information about the latest API changes in the official Release notes.