Which connector?

Teads

Additional details:

The Teads connector syncs its report tables at a fixed, very fine grain. report_budget and report_video hold one row per combination of day, hour, website domain, website or app, browser, browser version, device, country, creative and line item. Teads serves across thousands of publisher domains, so a single advertiser account produces millions of rows.

Most analytics and marketing measurement use cases only need daily totals. Blocking the unneeded grain columns hides them but does not reduce MAR, because each row keeps its own primary key. Row filtering helps only to exclude other advertisers; it does not aggregate the rows of the advertiser you keep. As a result, there is currently no way to make the connector cost efficient for daily reporting.

Requested: either of the following.

1. A new aggregated report table at day, campaign, line item and country level.
2. An option in the connector setup to choose the report dimensions, so the connector requests a report at that grain from the Teads Reporting API, which already supports custom dimensions.

Dimensions needed: day, campaign ID and name, line item ID and name, country, advertiser ID and name, currency.

Metrics needed: spend (budget spent), impressions, clicks, conversions, conversion value.

Why it matters: we use Teads data for marketing mix modelling, which runs on daily spend and outcome data. With the current grain, the MAR cost of the Teads connector is far out of proportion to the data we actually need.