Skip to main content

Introduction

Criteo is a global commerce-media platform best known for retargeting and performance display advertising across the open web. The connector pulls campaign- and ad-set-level performance from Criteo’s Stats API, with architecture data (ad accounts, campaigns, ad sets, ads) merged from Criteo’s live architecture endpoints and report-derived fallback data so deleted entities still appear in historical reporting. 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 Criteo to Adriel.

Data refresh strategy

Architecture data

Architecture covers ad accounts, campaigns, ad sets, and ads. It refreshes twice daily at 4:00 PM UTC and 5:00 AM UTC. Architecture data is pulled live from Criteo’s API, then supplemented with report-derived entities so deleted or otherwise missing campaigns and ad sets still appear alongside their historical metrics.

Reports data

Reports include daily performance metrics for ad accounts, campaigns, ad sets, and ads. Real-time. Report data is fetched from Criteo’s Stats API on demand when a dashboard loads, so the latest values are always visible. On top of that, scheduled background syncs keep historical data consistent across multiple time windows. Refresh schedule. Reports refresh on three overlapping schedules:
  • 5:00 PM UTC daily — syncs the last 9 days for ad account, campaign, ad set, and ad
  • 11:40 PM and 6:40 AM UTC daily — syncs the last 3 days for ad account, campaign, ad set, and ad
  • 7:30 AM UTC on the 1st and 15th of each month — syncs the last 30 days for ad account, campaign, ad set, and ad

Architecture levels

Ad account → Campaign → Ad set → Ad

Date range limits

A single report query is capped at 365 days; wider ranges are split automatically. Criteo also rejects any query whose start date is more than 2 years in the past.

Metrics

How to read the columnsData type uses Adriel’s vocabulary — Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean. API Key in code style like Displays is the literal Criteo Stats API field; where the same raw field name is shared across objects (Criteo returns attributes.name for the ad, ad set, and campaign), it’s shown qualified as object.field (for example ad.name) so each row stays unique; italic marks a value Adriel computes or derives. Some raw fields back several rows — notably each ad’s landing-page URL, from which Adriel parses every UTM value — so the same key can appear on multiple rows; that’s the shared source field, not a duplicated entry.
Spend and revenue are reported in the currency configured on the Criteo advertiser account. When an ad account’s currency differs from the workspace currency, values are converted using the current day’s exchange rate.

Basic

Campaign Attributes

UTM values are parsed by Adriel, not returned by Criteo. Adriel reads the UTM query parameters from each ad’s landing URL and exposes them as metrics for rollup. Landing URL and all five UTM metrics share the same underlying landing-page-URL field.

Campaign Structure

Computed Metric

These are calculated by Adriel from other metrics; they have no single underlying Criteo field.

Conversion Performance

Creative Attributes

Impression Click Performance

Criteo-specific

These metrics exist only for Criteo and aren’t part of any cross-connector category. Every group above is a standard category shared with other connectors.

Breakdowns

Basic

Campaign Structure

Creatives

Adriel post-processes ad creatives to generate these breakdowns.

Date

Criteo’s API returns daily records; all time-grouping breakdowns are Adriel-side aggregations of the same underlying daily data.

Others

Criteo-specific

These breakdowns exist only for Criteo and aren’t part of any cross-connector category. Every group above is a standard category shared with other connectors.

Limitations

  • Rotating refresh tokens — every Criteo token refresh issues a new refresh token, which the connector persists automatically. If a refresh response omits the new value, the connection becomes unrecoverable until it is reconnected. This is the single most important operational behavior to monitor.
  • Reach summed across days may overcount — Reach is a daily count of unique users. When viewed over a date range longer than one day, the total can overstate true unique reach because the same user may be counted on multiple days.
  • Deleted entities are retained — historical data for deleted campaigns, ad sets, and ads is preserved through the report-derived architecture fallback rather than excluded.
  • Historical start-date cap — Criteo rejects report queries whose start date is more than 2 years in the past, and a single query cannot span more than 365 days.

API references

See also