Retargeting ROAS Dropped Below Threshold, Criteo

Retargeting ROAS Dropped Below Threshold for Criteo stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

Metrics type: Key Metrics • Category: Ad Platform

At a glance

A real-time alert that fires when Criteo’s defensive retargeting ROAS falls more than a set margin below the same day-of-week reading from the prior week. Criteo’s retargeting line items (product-detail-page visitors, basket abandoners) are the warmest, highest-ROAS part of the account, so a sharp drop here is usually the first visible symptom of something structural: cookie deprecation tightening, Safari ITP or iOS ATT enforcement getting stricter, a catalogue-feed gap pulling dynamic creative, or an audience-match collapse in the next identity sync. This is an early-warning card, not a reporting card. It exists to catch the slide before a full reporting period bakes the loss in.

What it counts	The trailing-window return on ad spend for Criteo’s retargeting line items only (lower-funnel PDP-visitor and basket-abandoner audiences), compared against the equivalent reading from the prior 7-day same-day-of-week baseline. The alert is the boolean breach state; the displayed value is the current retargeting ROAS and the percentage gap to baseline.
Cost basis	CPC-dominant. Retargeting auctions are warmer, so Criteo bids more aggressively for users carrying PDP-view signal. The ROAS numerator is Criteo-attributed conversion value; the denominator is retargeting-line-item spend.
Currency	Advertiser-account currency. ROAS itself is a ratio, so it is currency-neutral; the underlying spend and revenue are in account currency.
Conversion attribution	Criteo defaults to 30-day post-click + 7-day post-view attribution, configurable per advertiser. Retargeting leans heavily on post-view credit, so this card is sensitive to view-attribution loss on iOS / Safari.
Attribution window	30-day click + 7-day view default. A genuine drop and an attribution-measurement drop can look identical here; pair with the tracking-decay card to tell them apart.
Bot / invalid traffic	Filtered pre-billing on Criteo owned-and-operated supply. IVT slippage is generally low on retargeting line items because the audience is known.
iOS 14.5+ ATT impact on the card	High. Retargeting is the line item most exposed to identity loss. When Safari ITP or iOS ATT enforcement tightens, the matchable audience shrinks and post-view credit evaporates, so this is often the first card to breach after a platform identity change.
Catalogue-feed dependency	Indirect but strong. A feed gap forces dynamic creative to fall back to generic, conversion rate collapses, and retargeting ROAS drops even though spend holds. Always check feed health when this alert fires.
Time window	RT (real-time evaluation) against a prior 7-day same-day-of-week baseline. Same-DOW comparison removes the weekly seasonality that would otherwise produce false alerts on, for example, weekend apparel spikes.
Alert trigger	retargeting ROAS drop >25% vs prior 7D same-DOW. An illustrative threshold; the breach fires when current retargeting ROAS is more than a quarter below the same weekday a week earlier.
Roles	owner, marketing, finance

Calculation

Calculated automatically from your Criteo data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A UK home-and-garden DTC retailer running Criteo retargeting plus a small Commerce Media prospecting layer. The alert evaluates retargeting ROAS each day against the same weekday a week prior. Account currency GBP.

Day	Retargeting spend (£)	Criteo-attributed revenue (£)	Retargeting ROAS	Same-DOW baseline	Gap	State
Mon 01 Jun 26	1,180	9,900	8.4x	8.6x	-2%	OK
Tue 02 Jun 26	1,210	10,200	8.4x	8.3x	+1%	OK
Wed 03 Jun 26	1,240	7,100	5.7x	8.5x	-33%	BREACH
Thu 04 Jun 26	1,260	5,800	4.6x	8.4x	-45%	BREACH

What the pattern tells you:

1. The breach on Wed 03 Jun 26 is the signal, not the Thursday number. By Thursday the loss is obvious to anyone watching the weekly report. The point of this card is that it fired on Wednesday, roughly 24 hours earlier, before a reporting period closed.
2. Spend held while ROAS fell. This is the classic identity-loss or feed-gap fingerprint. The auto-bidder is still pacing, still buying impressions, but each impression now lands on a worse-matched user or renders generic fallback creative. Flat spend masking falling efficiency is the most dangerous failure mode on Criteo.
3. A 33% then 45% slide over two days points at a structural cause, not auction noise. Auction-heat wobble produces single-day dips that recover. A two-day deepening slide usually means a feed rejection, an ITP enforcement step, or a top-seller going out of stock.
4. First diagnostic stop is the catalogue feed. Open Criteo Feed Manager Diagnostics. If active SKU count dropped, dynamic creative is falling back to generic and conversion rate has collapsed, fix the feed and ROAS recovers within 24 to 72 hours.
5. Second stop is the tracking layer. If the feed is healthy, check whether the Criteo One Tag is firing without setting a cookie on a rising share of sessions, that is ITP catching up and the next audience sync will shrink. See the tracking-decay card.
6. Third stop is competitive heat. If feed and tracking are both clean, a competitor may have entered the retargeting auction or Criteo’s bid floor moved. CPC will be rising in that case.

Quick sanity tests:

• ROAS down + spend flat + feed healthy = check tracking and identity match.
• ROAS down + spend flat + active SKU count dropped = feed gap, fix the feed first.
• ROAS down + CPC up = competitive auction heat eating efficiency.
• ROAS down only on iOS / Safari split = attribution measurement loss, not necessarily real revenue loss.
• ROAS recovered same week after a feed re-sync = confirmed feed-driven, no further action.

Sibling cards merchants should reference together

Card	Why it matters next to Retargeting ROAS Dropped Below Threshold	What the combination tells you
ROAS	The headline account-level efficiency reading.	If account ROAS is steady but retargeting ROAS breached, the problem is isolated to retargeting line items, usually identity or feed.
ROAS Trend	The longer-arc view of the same ratio.	Confirms whether the breach is a one-off dip or the latest point on a sustained decline.
Conversion Rate Trend	The conversion side of the ratio.	A falling conversion rate alongside the ROAS breach points at generic-fallback creative or a poorly matched audience.
Conversion Lag	View-through latency, critical for retargeting.	Some apparent ROAS drop is just lagged credit that has not landed yet; rising lag softens the alarm.
Conversion Drop Alert	The conversions-volume counterpart alert.	Both firing together = real demand loss; only ROAS firing = efficiency or attribution issue with volume intact.
Total Revenue	The numerator in absolute terms.	Cross-check whether the ratio fell because revenue fell or because spend rose.
Total Spend	The denominator in absolute terms.	Spend flat through a ROAS breach is the dangerous case; spend rising is at least a controllable cause.

Reconciling against Criteo

Where to look in Criteo’s own dashboard:

Criteo Management Centre → Reporting → Performance Report, filtered to retargeting campaign types and grouped by day, then compare the “Revenue” and “Spend” columns against the same advertiser-account and date range used in this card.

Criteo does not surface a same-day-of-week retargeting-ROAS breach alert natively, the Performance Report shows raw ROAS per period. To reconcile, divide the retargeting “Revenue” column by the retargeting “Spend” column for the breach day and for the same weekday a week earlier; the percentage gap should match this card within rounding. The Home dashboard tile shows account-level ROAS, which blends prospecting and Commerce Media, so it will read higher and steadier than this retargeting-only card. Always isolate to retargeting campaign types in the Performance Report when reconciling.

Why our number may legitimately differ from Criteo itself:

A small gap is normal. Usual suspects:

Reason	Direction	Why
Time zone	Boundary days off	Criteo reports in advertiser-account time zone; Vortex IQ uses UTC for period boundaries. Same-DOW comparison can shift by one calendar day at the boundary.
Ingest lag	Ours lower for “today”	Criteo Management API has a 2 to 4 hour lag on spend and conversions. A fresh breach can soften once catchup revenue lands.
Attribution restatement	Ours marginally lower at first	Post-view conversions credit retroactively; a same-day ROAS reading rises as view-through credit accrues over the following days.
Campaign-type filter	Theirs higher if unfiltered	The account-level ROAS tile blends prospecting and Commerce Media; this card is retargeting-only, so a clean reconcile requires filtering to retargeting line items.
Currency	None expected	Both views use advertiser currency; ROAS is a ratio.

Cross-connector reconciliation:

This card is Criteo-only. The retargeting-ROAS breach concept has no direct counterpart on other platforms, but for merchants running parallel retargeting the reasonable comparison set is:

Card	Expected relationship	What causes legitimate divergence
facebook_ads.fac_total_revenue	Different retargeting inventory and identity graph; useful as a cross-vendor efficiency benchmark, not a reconciliation.	Meta’s closed identity graph degrades differently under ATT than Criteo’s open-exchange catalogue retargeting.
shopify.total_revenue / bigcommerce.total_revenue	Commerce-platform realised revenue is the source of truth for the ROAS numerator.	Criteo attributes generously; a 30 to 50% over-state versus store UTM truth is normal, so a Criteo ROAS breach should be sanity-checked against the store ledger before reallocating budget.

Known limitations / merchant FAQs

My retargeting ROAS breached but my account ROAS looks fine, which do I trust? Both, they answer different questions. Account ROAS blends retargeting, prospecting, and Commerce Media, so a retargeting slide can be masked by steady prospecting. This card isolates retargeting precisely because it is the warmest, most valuable, and most identity-exposed part of the account. A retargeting-only breach is a real early warning even when the blended number looks healthy.

The alert fired then cleared by itself the next day, was it a false alarm? Usually not. Two common benign causes: post-view conversion credit landing late and pulling ROAS back up, or a single-day auction-heat wobble that recovered. A breach that self-clears within 24 hours and does not recur is low priority. A breach that deepens over two or more days is structural, treat it as real.

How do I tell a real ROAS drop from an attribution-measurement drop? Check the tracking-decay card. If the Criteo One Tag is firing without setting a cookie on a rising share of sessions, you are losing measurement, not necessarily revenue. Cross-check the store ledger: if realised orders held while Criteo-attributed ROAS fell, it is a measurement problem and the fix is server-side conversion signal, not budget cuts.

Why same-day-of-week instead of a simple prior-7-day average? Retargeting has strong weekly seasonality, weekends and Sunday evenings convert differently from midweek on most DTC accounts. Comparing a Wednesday to the previous Wednesday removes that seasonality and cuts false alerts that a flat 7-day average would generate every Monday and Saturday.

Should I cut budget the moment this fires? No. The first action is diagnosis, not budget. Check the catalogue feed, then the tracking layer, then competitive heat. Cutting retargeting budget on a feed-driven dip throws away your most efficient line item right when a feed fix would have restored it. Cut budget only once you have confirmed the cause is genuine demand loss, not a fixable feed or tracking fault.

Does this card account for Criteo’s generous attribution? The card reports Criteo’s own attributed ROAS, which over-states versus store UTM truth by a typical 30 to 50%. That is fine for in-platform breach detection because the comparison is Criteo-to-Criteo (this week’s reading versus last week’s, same measurement basis). For absolute ROAS truth, reconcile against the commerce-platform revenue line.

---

Tracked live in Vortex IQ Nerve Centre

Retargeting ROAS Dropped Below Threshold is one of hundreds of KPI pulses Vortex IQ tracks across Criteo and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.