Skip to main content

Introduction

Teads Ad Manager is an outstream video and native advertising platform. The connector pulls campaign performance from the Teads Ads API, including video engagement (impressions, video views, quartile completions), spend, viewability, attention, and conversion metrics. Reports are retrieved through an asynchronous create-and-poll flow, normalized from CSV, and written into a daily cache. Dashboards read from this cache, not from the live API, so widget queries are bounded by the cached window rather than the live reporting API. As a marketing connector, metrics, breakdowns, and currencies are standardized so widgets can aggregate across sources without additional configuration. To connect this data source, see How to connect Teads to Adriel.

Data refresh strategy

Architecture data

The ad account and the campaigns, ad sets, and ads available under it are refreshed alongside the report cache. New campaigns appear after the next scheduled refresh.

Reports data

This is a daily-cache connector.
  • Initial fetch. After connection, the last 90 days of daily data are retrieved.
  • Refresh schedule. At 8:00 AM UTC every day, the latest 14 days of data are refreshed in place. The rolling 14-day window covers late-arriving conversions and any restatements Teads issues within that period without a manual reconnection.

Architecture levels

Ad account → Campaign → Ad set → Ad

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 impression is the literal Teads API field name. Italic text describes how a value is produced when it doesn’t map cleanly to a single API field.

Spend & cost

Currency values are reported in each ad account’s configured currency. Spend is reported through turnover-based metrics; budget-delivered variants are not available (see Limitations).

Delivery & clicks

Video completion funnel

Viewability (MOAT)

Attention (Lumen)

Reach & conversions

Unique impressions are estimated and only compatible with specific breakdown and metric combinations; some groupings will not return a value.

Breakdowns

Every column present in the cached data can be used as a breakdown; there is no fixed allowlist. The groupings below are the standard ones exposed for Teads.

Standard hierarchy

Time & date grouping

Teads returns daily records; Adriel aggregates them into these views for reporting.

Limitations

  • Daily cache, not live. Dashboards read from the daily cache rather than the live Teads API, so widget queries are bounded by the cached window. Report data is written into the cache through an asynchronous create-and-poll flow and normalized from CSV.
  • Generic table compatibility. Teads data appears as a generic table and does not natively combine with other connector types unless they share identical breakdowns. Cross-connector analysis requires blend data configuration.
  • Spend is turnover-based only. All budget-delivered spend variants (for example budget_delivered_value and its averages) are excluded from the API request due to API incompatibility; only the six turnover-based spend metrics are available.
  • Unique-reach compatibility. Unique impressions (uv_impression) is only compatible with specific breakdown and metric combinations.
  • Restatements outside the refresh window. Only the trailing 14 days are re-fetched on each refresh; corrections Teads issues to data older than that window are not picked up automatically.
  • API key rotation. Authentication is a single static API key. Rotating the key on the Teads side requires re-entering it in the connector settings.

API references

  • Teads Ads API — reports are created and polled asynchronously against the host ads.teads.tv, then normalized from CSV. Requests authenticate with a single API key sent as the value of the Authorization header.

See also