How to generate a Teads Ad Manager API key for your seat, add it to Medialake, and understand exactly what it is used for.
What to expect
Teads Ad Manager is connected with an API key that you generate in your own Teads seat. There is no Teads sign-in or consent screen during setup: nobody is redirected to Teads to log in. Instead, a Teads user generates the key, a Medialake administrator saves it in Medialake, and Medialake calls the Teads Reporting API server-side from then on.
Teads API keys belong to a user and a seat, and carry the same access as that user has in that seat. Medialake uses the key only to run and read reports. Each sync works like this:
Medialake asks Teads for one report covering the last 12 months, which is the longest period Teads accepts for a single report. The report lists each creative with its advertiser, campaign, line item, format, and size.
Teads builds the report in the background, usually in about twenty seconds, and Medialake waits for it.
Medialake downloads the finished report.
For each creative in the report, Medialake finds the creative's media file through Teads' public ad preview service and downloads it.
The Teads Ad Manager connector only reads: it does not create, edit, pause, or delete campaigns, line items, or creatives.
Teads user Medialake Teads
│ generate an API key │ │
│ in your seat's settings │ │
│──────────────────────────────────────────────────────────▶│
│ │ │
Medialake administrator │ │
│ save the key as an │ │
│ access key │ │
│──────────────────────────────▶│ │
│ │ │
Team member │ │
│ connect and select │ │
│ "Last 12 months" │ │
│──────────────────────────────▶│ run a 12-month report │
│ │──────────────────────────▶│
│ │ report ready │
│ │◀──────────────────────────│
│ │ look up and download │
│ │ each creative's media │
│ │──────────────────────────▶│
Before you begin
You will need:
A Teads Ad Manager user with reporting access to the seat you want to sync
Administrator privileges in Medialake, to add the key to the Teads Ad Manager integration
Because the key has the same access as the user who generates it, generate it as a user whose access in the seat matches what you want in Medialake. To sync more than one seat, generate a key in each seat and add each one to Medialake as a separate access key.
>Keep the key private. Anyone with the key can use the Teads Ad Manager APIs with the same access as the user who generated it. Store it in an approved password manager or secret-management system. Do not email it, paste it into a support ticket, or commit it to source control. Medialake stores the values you enter encrypted.
Step 1: Generate an API key in Teads Ad Manager
Sign in to Teads Ad Manager and make sure you are working in the seat you want to sync.
Open the Settings screen by clicking the gear icon in the header.
In the API Keys section, click Generate API Key.
Optionally, click the edit icon to give the key a recognizable name, such as
Medialake.Copy the key.
Step 2: Add the key to Medialake
You need administrator privileges in Medialake for this step.
In Medialake, open Administration → Integrations from the sidebar.
Open the Teads Ad Manager integration.
In the Access Keys section, click Create New Setting.
In the New access key panel, give the key a Name, such as
Teads main seat. The name is shown in the access key list and next to every account that connects with it.Under Credentials, paste the key into Enter your Teads Ad Manager API key here without any space.
Under Who can use it?, choose which teams can connect Teads Ad Manager with this key, or make it available to all teams.
Click Save access key.
Medialake rejects a key that contains spaces or line breaks. Saving does not contact Teads.
To check the key against Teads, click Test next to it in the Access Keys list. Medialake makes a single call to the Reporting API with the key. It does not run a report, so it does not use your report quota. If Teads accepts the key, you see "The provider accepted these credentials."
Connect Teads Ad Manager and choose what to sync
Any team member who can connect sources (a Team Manager or Write user), on a team that can use the access key, can add Teads Ad Manager as a source.
Open Connections → Catalogue from the side menu.
Find Teads Ad Manager and click Connect.
Under Access key, select the access key from Step 2. You can click Test to check it again.
Click Connect. There is no Teads login page: Medialake connects with the saved key.
Select the Last 12 months folder. It is the only folder, and nothing is synced until you select it.
Set the Frequency. Teads Ad Manager syncs once a week by default. You can change this to once a day or once a month, or choose Manual.
Each creative becomes one file in Medialake, a video or an image depending on whether it is a video or display creative. Each file records its advertiser, campaign, line item, creative, format, and size.
What appears, and what does not
Only creatives that delivered impressions in the last 12 months appear. A creative that was built but never served, or that last ran more than 12 months ago, is not in the report, so it cannot be synced.
Only creatives built in Teads are supported. Creatives trafficked as third-party ad server tags have no media file that Medialake can retrieve, so they are skipped.
Shared artwork is synced once per creative. If several creatives use the same artwork, each one is synced as its own file.
Limiting what Medialake can access
The key's reach is set by the user who generated it: it can report on whatever that user can see in the seat. Selecting the folder in Medialake controls what is synced, but it does not narrow the key itself. For the narrowest connection, generate the key as a user whose access is restricted to the advertisers you want in Medialake. In Teads, an Ad Manager Admin or Reporting Admin can restrict a user to specific advertisers through user management.
What Medialake can and cannot do
With the key, Medialake can:
Run one report per sync on your seat, covering the last 12 months
Read that report's advertiser, campaign, line item, and creative details and impression counts
Retrieve each creative's media through Teads' public ad preview service and download it
Medialake does not:
Create, edit, pause, or delete campaigns, line items, or creatives
Change budgets, bids, targeting, or seat settings
Manage Teads users or API keys
Medialake sends the key only to the Teads Reporting API at ads.teads.tv, as the raw value of the Authorization header that Teads expects. The finished report, the ad previews, and the media files are downloaded without the key.
Staying connected
There is no token to refresh: Medialake uses the same key for every sync. If Teads rejects the key during a sync, Medialake checks it again, and if Teads still rejects it, the connection is marked as unauthorized, for example after the key is removed in Teads.
Teads limits how many reports can be run in each 24-hour period and how often reports can be requested. Its request rate limit applies to the whole seat, so it is shared with any other tool that uses a key on the same seat. Each Medialake sync uses one report, so a daily frequency uses one report a day. When Teads reports that a limit has been reached, Medialake retries a few times. If the limit is still in place, that sync adds nothing, and the next sync tries again.
If Teads takes more than about two minutes to build the report, Medialake stops waiting and that sync adds nothing. The next sync requests a fresh report.
To replace a key, generate a new one in Teads, add it in Medialake as a new access key, and switch the connection to it. To switch, open the source's General tab, click Change Key in its Access Keys section, select the new key, and click Save. You can delete the old access key in Medialake once no connection uses it.
Revoking access
To revoke Medialake's access, open Settings in Teads Ad Manager and manage the key in the API Keys section, or ask your Teads account team to revoke it.
Remove the Teads Ad Manager connection in Medialake as well if it should no longer sync, then delete its access key from the Access Keys list.
Troubleshooting
Symptom | What to check |
"format is invalid" for the API key when saving | The key contains a space or line break. Paste it again without any spaces. |
Test shows "The provider rejected these credentials." | The key is wrong or was removed. Generate a new key and add it as a new access key. |
Test shows "These credentials look right, but the provider couldn't confirm them just now." | Teads could not be reached or was rate-limiting. Try again in a few minutes. |
A sync finishes but adds nothing new | Check that the seat delivered impressions in the last 12 months, and that your Teads report quota for the past 24 hours has not been used up. Teads may also have taken more than about two minutes to build the report. The next sync tries again. |
An expected creative is missing | It had no impressions in the last 12 months, it was trafficked as a third-party ad server tag, or it belongs to a seat or advertiser the key's user cannot see. |
The same artwork appears more than once | Several creatives share that artwork. Each creative is synced as its own file. |
The connection is marked as unauthorized | Teads no longer accepts the key, for example because it was removed. Generate a new key and switch the connection to it. |
If the issue continues, contact [email protected] with your seat name, the creative IDs you expected, and the error message. Do not include the API key.
Further reading
Manage & Generate API Keys: generating a key for a seat
User Management: Teads user roles, and restricting a user to specific advertisers
Reporting API: how API keys are sent and the Reporting API's rate limits
API Quotas: checking how many reports your seat can run per 24 hours
Reporting Glossary: the dimensions and metrics used in reports
Questions about connecting Teads Ad Manager? Contact [email protected].
