Prooflytics
Platform9 min read

Criteo Marketing Analytics: ROAS Tracking and Daily Intelligence Setup

Criteo's 30-day post-click attribution inflates retargeting ROAS by default. Learn which metrics to monitor daily, how to detect attribution inflation without a holdout test, and how to connect Criteo alongside Meta and Google Ads in one unified marketing brief.

Abstract analytics dashboard with data metrics and performance graphs on dark background — criteo marketing analytics

Criteo Marketing Analytics: ROAS Tracking and Daily Intelligence Setup

Prooflytics connects to Criteo's Marketing Solutions API and pulls campaign performance data - impressions, clicks, ROAS variants, cost per order, and audience reach - into your daily marketing brief automatically. Once connected, you see Criteo alongside Meta Ads and Google Ads in the same briefing, without manual exports or CSV reconciliation.

Criteo marketing analytics refers to the systematic tracking of retargeting campaign performance across Criteo's ad network: display ads served to shoppers who previously visited your site, measured against your chosen ROAS attribution model.

The operational problem is specific to how Criteo reports. Criteo uses a 30-day post-click attribution window by default, while Meta defaults to 7-day click and Google Ads to 30-day last-click across the search network. When weekly numbers come in, you are comparing three different counting methodologies from three different dashboards. Teams running Criteo alongside other paid channels typically spend 2-3 hours each Friday pulling platform exports, aligning date ranges, and reconciling why blended ROAS does not match any single platform report. Prooflytics eliminates that ritual by pulling Criteo data through the Marketing Solutions API and normalising it alongside your other channels in one briefing.

Criteo ROAS: The ratio of attributed revenue to Criteo ad spend, calculated within your chosen attribution window. The default is 30-day post-click (RoasPc30d).

Post-click window (Pc30d): A sale is attributed to Criteo if it occurs within 30 days of a shopper clicking your banner. Longer windows inflate apparent ROAS by capturing organic purchases that coincidentally followed an ad click.

View-through attribution (Pv24h): A sale is attributed if it occurs within 24 hours of an ad impression regardless of click. Used for brand awareness campaigns where direct-response measurement is impractical.

Teams that connect Criteo alongside Meta and Google through the Prooflytics integrations hub see all three channels in one briefing with attribution labels visible - so you do not conflate a Criteo 30-day number with a Meta 7-day number and draw the wrong budget conclusion.

Key takeaways

Criteo's 30-day post-click window conflicts with Meta's 7-day and Google's 30-day last-click defaults

Teams running all three simultaneously are comparing three different counting methodologies and calling them the same metric. A side-by-side ROAS comparison across these platforms measures different things with the same label.

Teams running Criteo alongside other paid channels spend two to three hours every Friday reconciling exports

This weekly reconciliation ritual exists because each platform's attribution window produces different conversion counts for the same customer. Prooflytics eliminates this ritual by normalising all channels through the Criteo Marketing Solutions API.

Criteo reports four distinct ROAS variants measuring fundamentally different claims

RoasPc30d, RoasPc1d, RoasPv24h, and RoasClientAttribution each measure a different attribution methodology. Using one without understanding the others produces a ROAS number that cannot be meaningfully compared across channels.

The ratio of 1-day to 30-day post-click ROAS functions as a holdout-test proxy

A ratio below 0.4 indicates Criteo is claiming significant credit for purchases that would have occurred organically without the ad exposure. This ratio is the fastest available signal for whether Criteo's attribution is overstating its incremental contribution.

Criteo's own research found a 428 percent incremental ROI gap between tested and untested campaigns

This gap - the largest documented attribution overstatement in retargeting - compares campaigns with formal incrementality tests against those relying solely on platform attribution. The finding means untested retargeting ROAS numbers are unreliable as planning inputs.

Criteo marketing analytics: what data flows into your briefing

Criteo's Marketing Solutions API exposes over 100 metrics across campaign, ad set, creative, and channel dimensions. Prooflytics pulls the performance subset relevant to daily campaign management.

Campaign performance

  • Displays and ViewableDisplays - impressions served and those meeting the 50% visibility threshold for one second or more
  • Clicks and ClickThroughRate - direct demand signals
  • AdvertiserCost - total spend, the denominator for all ROAS calculations
  • Cpc (cost per click) and ECpm (effective cost per thousand impressions)

Conversion and revenue (with attribution variants)

  • SalesPc30d - sales within 30 days of a click (Criteo's optimisation default)
  • SalesPc1d - sales within 1 day of a click (incremental proxy)
  • SalesPv24h - sales within 24 hours of an impression
  • RevenueGenerated variants paired to each attribution model
  • RoasPc30d, RoasPc1d, RoasPv24h, RoasClientAttribution - ROAS per attribution method
  • CostPerOrder and AverageCart per model

Audience and reach

  • ExposedUsers - unique users who saw your ads within the selected period
  • Reach - estimated total unique audience
  • QualifiedVisits - users with at least two on-site events within one hour of clicking

Omnichannel (if enabled)

  • OmnichannelRoas - online plus in-store revenue divided by spend
  • OmnichannelRevenue and OmnichannelSales
  • RoasOfflinePc30d - offline-only attribution for physical retail measurement

Data is available at ad, ad set, campaign, channel, device, and operating system level, with hourly or daily granularity. Criteo's API delays same-day statistics by up to a few hours; treat intraday data as provisional until the following morning when finalised numbers settle.

Understanding Criteo's attribution variants

Retargeting campaigns have a specific attribution problem that prospecting does not: your ads are shown to people who were already considering a purchase. This makes it structurally difficult to separate Criteo-caused sales from organic purchases that happened near an ad impression.

For cross-channel comparison, the marketing attribution windows guide explains why a Criteo 30-day window is not comparable to Meta's 7-day window - and why blending them into a single ROAS figure produces a number that does not match any platform's native report.

Monitor at minimum two ROAS numbers for every Criteo campaign:

  1. RoasPc30d - the number Criteo optimises toward. Use this for campaign-level decisions: pausing, scaling, budget reallocation.
  2. RoasPc1d - 1-day post-click ROAS. This is the practical proxy for Criteo's immediate incremental contribution without running a holdout test.

If RoasPc30d is 4.2x but RoasPc1d is 1.1x, more than 75% of attributed sales are arriving days after a click - a pattern consistent with organic conversions that Criteo is counting but did not cause. The gap between the two numbers is your attribution inflation estimate.

Prooflytics

Stop stitching platform exports together

Every channel in one brief — plus the memory of what each one actually drove.

14 days free · no credit card

The incrementality gap in Criteo ROAS

The operational problem for in-house performance teams: when Criteo ROAS looks strong on a 30-day window but incremental contribution is unclear, scaling budget is a gamble. You risk overfunding a channel that claims credit for conversions that would have happened regardless.

Criteo's own research, published in their ROAS Trap report, found that brands conducting formal incrementality tests with sponsored product ads witnessed a +428% incremental return on investment compared to what post-click attribution alone implied. The finding works in both directions: some campaigns deliver far more incremental value than their attributed ROAS suggests; others deliver far less.

The practical decision rule without running a full holdout test: compute the ratio of SalesPc1d to SalesPc30d for each ad set. A ratio below 0.25 (fewer than one in four attributed sales arriving within the first day) signals high attribution inflation - the 30-day window is capturing organic demand. A ratio above 0.5 indicates Criteo is generating demand close to the purchase moment and attribution is more defensible.

Prooflytics surfaces both RoasPc1d and RoasPc30d side-by-side in the daily briefing, so the attribution gap is visible without manual cross-referencing. Compare those figures alongside your ROAS benchmarks for each channel and industry segment to calibrate whether a given Criteo ROAS number is strong or suspicious for your category. When the gap between the two variants widens more than 20% week-over-week, the briefing flags it as a confidence signal rather than treating the headline ROAS at face value.

What you can do once Criteo is connected

Spot retargeting fatigue before it hits ROAS

Criteo retargeting campaigns fatigue through audience saturation, not creative wear the way Meta Ads social does. As your retargeted pool sees the same banner seven or more times, CTR drops and CPC rises - but ROAS holds temporarily because the 30-day attribution window still counts purchases from impressions served earlier in the cycle. By the time ROAS actually declines, you have been overpaying for 5-7 days.

Prooflytics compares today's Criteo ClickThroughRate and CPC against a rolling 7-day baseline. A CTR drop exceeding 25% with flat or rising spend is the early saturation signal - visible 5-7 days before it propagates into ROAS.

Align Criteo budget with cross-channel targets

When Criteo and your other paid channels feed the same briefing, you can set ROAS floor targets per channel. If Criteo's 7-day rolling ROAS drops below floor while another channel holds above it, the action queue surfaces a budget shift recommendation. This replaces the manual end-of-week reallocation discussion with a daily data signal.

Track ROAS by device and channel

Criteo's API includes Device and Channel dimensions. Mobile ROAS in retargeting frequently underperforms desktop because mobile add-to-cart rates are lower while CPCs remain comparable. Prooflytics segments the daily ROAS by device so you can apply separate bid rules or shift budget toward the higher-converting device mix without waiting for a monthly device report.

How to connect Criteo to Prooflytics

1. Open Settings to Data Sources

Navigate to Settings to Data Sources in your Prooflytics account. Criteo appears under the Ads category alongside Meta, Google Ads, LinkedIn, and other paid channels.

2. Authenticate with your Criteo account

Click Connect on the Criteo tile. You are redirected to Criteo's OAuth authorisation flow. Log in with your Criteo advertiser credentials. If your account manages multiple advertisers, select the specific advertiser ID you want to sync.

Permissions required: Read access to campaign statistics and advertiser account data. Prooflytics does not request write access and does not modify your campaigns, bids, or budgets.

3. Select sync scope and historical range

After authentication, choose which campaigns and date range to pull. The default is 90 days of historical data with daily forward sync. You can narrow to specific campaigns if you run Criteo for multiple brands from one Criteo account.

4. Data appears in the next briefing

Campaign performance data flows into your briefing the following morning. Criteo's API delays same-day statistics by up to a few hours, so the default sync excludes provisional same-day data. The display ROAS defaults to RoasPc30d; you can switch to RoasPc1d or RoasClientAttribution in briefing settings.

Most common failure mode: If you see "Authentication failed" after the OAuth redirect, your Criteo account likely has multi-factor authentication (MFA) active on the session used for API authorisation. Fix: use a session without MFA active for the initial OAuth handshake, then re-enable it. The token refreshes automatically on subsequent syncs.

Bottom line

  • Criteo's Marketing Solutions API exposes 100+ metrics including multiple ROAS attribution variants. The ratio of RoasPc1d to RoasPc30d is the fastest proxy for incremental versus reported ROAS without running a holdout test.
  • Criteo's default 30-day window structurally inflates retargeting ROAS. Brands running incrementality tests found a +428% gap between incremental ROI and attributed ROAS in sponsored product campaigns - the gap is larger in retargeting than in prospecting.
  • Watch CTR and CPC daily: these metrics lead ROAS by 5-7 days in audience saturation scenarios, giving you time to act before ROAS visibly declines.
  • Connecting Criteo to Prooflytics puts it alongside Meta and Google Ads in one briefing, with attribution windows labelled explicitly - so you stop treating 30-day Criteo ROAS and 7-day Meta ROAS as comparable numbers.

Connect your Criteo account at /integrations/criteo to start the daily intelligence sync, or book a walkthrough if you manage Criteo alongside multiple paid channels.

You can read independent reviews of Prooflytics on G2 and compare it to alternatives in the marketing intelligence category.

Frequently asked questions

How often does Criteo data sync in Prooflytics?+

Data syncs once daily, pulling the previous day's finalised statistics from the Criteo Marketing Solutions API. Same-day data exists in Criteo's system but is marked provisional - it is excluded from the briefing by default to avoid false alerts from incomplete attribution counts. If you need intraday visibility, you can enable same-day preview mode in briefing settings, but treat those numbers as subject to revision.

Which Criteo ROAS metric does Prooflytics use by default?+

The default is RoasPc30d - Criteo's standard 30-day post-click attribution, matching what the Criteo Management Center UI displays. You can switch to RoasPc1d, RoasPv24h, or RoasClientAttribution in briefing configuration. All attribution variants are pulled from the API simultaneously, so switching is a display preference, not a new data fetch.

Can Prooflytics track Criteo marketing analytics alongside Meta and Google Ads in one view?+

Yes. Prooflytics normalises Criteo, Meta, and Google Ads campaign data onto the same date axis in the daily briefing. Because each platform defaults to a different attribution window, the briefing labels attribution models explicitly - Criteo 30-day click, Meta 7-day click, Google 30-day click - so you do not conflate them into a meaningless blended ROAS number.

What is the difference between reported ROAS and incremental ROAS in Criteo?+

Reported ROAS (RoasPc30d) counts all sales that occurred within 30 days of a Criteo ad click, including organic conversions that would have happened without the ad. Incremental ROAS measures only the additional sales caused by the ad. Criteo's ROAS Trap research documented a substantial gap between the two in retargeting campaigns. Comparing RoasPc1d against RoasPc30d is a practical proxy - a ratio below 0.25 suggests high attribution inflation.

Does the Criteo integration support omnichannel ROAS tracking?+

Yes, if your Criteo account has offline sales data sharing enabled. OmnichannelRoas and OmnichannelRevenue pull automatically once the integration is live. If offline data is not configured in your Criteo account, these fields return null and the briefing shows online-only metrics - it does not surface a false zero or inflate the ROAS figure.

Prooflytics

Stop stitching platform exports together

Every channel in one brief — plus the memory of what each one actually drove.

14 days free · no credit card

Continue reading