Why isn’t my Criteo Retail Media data live?
Criteo Retail Media report data is served from a cache of daily performance snapshots rather than fetched live from Criteo on each dashboard load. When a dashboard opens, values are aggregated from the most recent snapshot, so a change made in Criteo does not appear immediately. It shows up after the next sync brings the updated snapshot into the cache. For the sync schedule and the historical window, see the Criteo Retail Media data reference.Why do Unique visitors and Frequency look too high over a long date range?
Unique visitors and Frequency are counted per day. Adriel stores one value per day and sums the daily values when a widget spans several days, so the same person seen on more than one day is counted once for each of those days. Over a multi-day range this overstates true unique reach and inflates the derived frequency. For a figure that reflects distinct users, view Unique visitors over a single day, or use the daily breakdown to read each day’s value on its own rather than the range total.Why can’t I see Unique visitors or Frequency at the product or keyword level?
Criteo Retail Media returns Unique visitors and Frequency only at the campaign and line-item (ad set) levels. They are not returned for promoted products (individual SKUs) or for keywords, so a widget broken down by promoted product or keyword shows no value for these two metrics. Delivery, cost, and conversion metrics such as Impressions, Clicks, Ad spend, Attributed sales, Attributed units, Attributed orders, Assisted sales, and Assisted units are available at all four levels. To report reach, keep the widget at the campaign or line-item level.Why are CTR, CPC, CPM, and ROAS missing?
Criteo Retail Media does not provide rate metrics such as CTR, CPC, CPM, CPO, and ROAS. Adriel does not request them from the Criteo Retail Media API at any level, so they do not appear in the field list. The underlying inputs are available, so these rates can be built as custom metrics from the metrics that are returned. For example, CTR isclicks divided by impressions, and ROAS is attributedSales divided by spend. See the Criteo Retail Media data reference for the full metric list.
Why does an ad-account widget show campaign-level figures?
The ad account is used for navigation only and is not a reporting level for Criteo Retail Media. A report requested at the ad-account level is served at the campaign level instead, so an ad-account row reflects campaign-level data rather than a separate ad-account rollup. To compare across the account, break the widget down by campaign, or aggregate campaigns with a widget that rolls them up.How is Criteo Retail Media different from the standard Criteo data source?
Criteo Retail Media reports on sponsored product ads that run on retailers’ own websites and apps, down to the individual promoted product (SKU) and the keywords that trigger it, with retail outcomes such as attributed and assisted sales, units, and orders. The standard Criteo data source covers open-web retargeting and display. The two are separate data sources with separate credentials and separate metric sets. For the open-web retargeting connector, see the Criteo data reference.Related
Criteo Retail Media data reference
Metrics, breakdowns, refresh cadence, and limits for this data source.
Connect Criteo Retail Media
Steps to connect the Criteo Retail Media data source to Adriel.
Criteo data reference
The separate standard Criteo connector for open-web retargeting and display.