Which connector? Adform

Summary

The Adform connector (Lite) syncs only metadata and entity tables. It provides no way to define a report against Adform's Reporting Stats API, so there is no path to bring campaign delivery metrics into the destination. We're requesting custom report functionality for Adform, matching what the Google Ads, Meta Ads, and TikTok Ads connectors already provide.

Problem

Adform's Reporting Stats API is a query-based reporting layer, not a set of static tables. You specify dimensions and metrics, and Adform's engine generates the aggregated result on demand as an asynchronous report operation. This is the same model as the Google Ads, Meta, and TikTok reporting APIs.

For those three platforms, the Fivetran connector lets us define custom reports by choosing dimensions and metrics, and that is the primary way we extract reporting data from them. The Adform connector has no equivalent. It replicates Adform's metadata catalog (available metrics and dimensions, e.g. the buyer_stats_metadata_* tables) and entity tables (campaigns, orders, placements), but it lands no delivery fact table. There is no table containing a date alongside metrics such as impressions, clicks, or cost, and no way to request one.

As a result, the connector cannot produce even a basic campaign performance report. Our required grain is date x campaign, with spend, impressions, clicks, conversions, and conversion value. None of this is reachable through the connector today.

Requested capability

Custom report definitions for the Adform connector, consistent with the Google Ads / Meta Ads / TikTok Ads connectors: the ability to specify dimensions and metrics, have the connector issue the corresponding asynchronous report request to Adform's Reporting Stats API, poll the operation, and land the result as a table at the chosen grain.

This is a wrapper around an API capability that already exists. Adform's Reporting Stats API supports exactly this create-operation, poll-status, retrieve-result workflow, and the connector's own setup already requires the buyer.stats and buyer.stats.metadata OAuth scopes. So the reporting engine and the access are already in place; what's missing is the connector-side report builder.

Impact

Without this, the Adform connector cannot deliver advertising performance data, which is the primary reason we would use it. We currently have no supported path to bring Adform reporting into our warehouse through Fivetran, and are having to build a direct extraction against Adform's Stats API as a workaround.