At a glance
Spend on Criteo line items, audience segments, and catalogue product-sets that produced zero attributed conversions in the trailing 30 days despite receiving meaningful spend (>3 days live, >€100 spend threshold). On Criteo this surfaces (a) audience pools that match poorly to converting users (often iOS-attribution-stress fallout), (b) catalogue product-sets that render dynamic ads but never convert (low-margin or out-of-fashion SKUs), (c) Commerce Media publisher placements with no buy-intent traffic. Typical “healthy” Criteo accounts have 5 to 12% of spend in this bucket; >15% is a signal to audit the audience and catalogue layers.
| What it counts | Sum of metrics.spend on line items / audience segments / catalogue product-sets where attributed conversions over the 30-day window are zero (post-click + post-view), excluding line items live for fewer than 3 days (still in learning) and excluding line items with sub-€100 cumulative spend (statistical noise). |
| Cost basis | Mostly CPC, sums billable cost regardless of bid type. |
| Currency | Single advertiser-account currency. |
| Conversion attribution | 30-day post-click + 7-day post-view default. Generous attribution makes “zero conversions” a strong signal, if Criteo can’t even claim view-through credit, the line item really isn’t working. |
| Attribution window | 30D click + 7D view default. |
| Bot / invalid traffic | Excluded from numerator (filtered pre-billing). |
| iOS 14.5+ ATT impact on the card | Material. ATT can produce false-positive zero-conversion reads on iOS-heavy line items, conversions are happening but Criteo can’t attribute them. Rule of thumb: discount the wasted-spend number by 15 to 25% on iOS-heavy accounts to account for under-measurement. |
| Catalogue-feed dependency | Wasted spend often clusters on catalogue product-sets where the SKU has gone out-of-stock, image-quality dropped, or pricing went out-of-date. Audit the feed before pausing line items. |
| Time window | 30D (rolling 30 days). The lookback is long enough to filter out short-term noise but recent enough to catch active issues. |
| Alert trigger | >$0 (any zero-conv keyword), fires the moment any qualifying line item / segment / product-set hits zero conversions in the trailing 30 days with >€100 spend. The card lists every offender and its spend; the alert fires once when a new line item enters the bucket. |
| 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 French electronics DTC retailer running 14 active Criteo line items. The 30-day window is 02 Apr 26 to 01 May 26. Account currency EUR. Total Criteo spend €27,000.| Wasted line item | Spend (€) | Days live | Conversions | Reason (best guess) |
|---|---|---|---|---|
| Catalogue product-set: clearance accessories | 1,420 | 30 | 0 | Out-of-fashion SKUs; users click but don’t convert |
| Audience segment: lapsed-365-days visitors | 980 | 30 | 0 | Audience too cold for retargeting; convert via prospecting |
| Commerce Media: tech-news vertical | 720 | 30 | 0 | Wrong context; readers are research-stage, not buy-intent |
| Catalogue product-set: refurbished items | 540 | 30 | 0 | Image quality flagged; ads render but trust signal is low |
| Audience segment: cart abandoner >14 days | 380 | 30 | 0 | Cart-abandoner intent decays; >14 days is too late |
| Sponsored product: low-margin earphones | 220 | 21 | 0 | Marginal SKU; click-through happens but checkout drops |
| Total wasted (this card) | €4,260 | - | 0 | 15.8% of account spend |
- 15.8% of Criteo spend is in the wasted bucket, above the 5 to 12% healthy band. On a €27k monthly spend, this is €4,260 / month, €51,000 / year, that’s a real number. The first action is to pause or restructure the offenders, not to defend them.
- The clearance-accessories product-set is the biggest single offender. Two routes: (a) pause it entirely and reallocate budget to the converting product-sets, or (b) audit catalogue freshness (out-of-stock SKUs, image quality, pricing) before pausing. Most catalogue-driven wasted spend is fixable at the feed level, not by pausing the line item.
- Lapsed-365-days audience is structurally a poor fit for retargeting. Users who haven’t visited in 365 days are not retargetable in Criteo’s strongest sense; they’re effectively prospecting. Either move them into a Commerce Media prospecting campaign with proper prospecting bid strategy, or exclude them entirely.
- Commerce Media tech-news vertical is a context fit issue. Tech-news readers are in research mode, not buy-intent. Try a different vertical (review sites, comparison shopping content) or move spend to lower-funnel campaigns.
- Cart abandoner >14 days is past the recoverable window. Cart-abandoner intent decays fast: 80% of recovered carts close within 7 days. Beyond 14 days, the audience has either purchased elsewhere or abandoned the consideration entirely. Tighten the window to 7 days.
- The refurbished-items product-set is an image-quality problem. Criteo’s image-quality filter flagged the SKUs but didn’t fully block them; the ads serve at lower priority and against poorer placements, conversion rate collapses. Re-shoot the product images or escalate to Criteo client services to lift the flag.
- Cross-checking against
cri_total_spend: account ROAS would lift from 7.8× to ~9.2× if all €4,260 was reallocated to the converting line items at average ROAS.
- Catalogue-driven (product-sets): audit feed first; pause as last resort. Most product-set waste is fixable.
- Audience-driven (segments): audit definition first; tighten or exclude. Pause is acceptable for clearly-cold audiences.
- Commerce Media-driven: audit context fit first; reassign to better-fit verticals. Pause if no fit found in 14 days.
- Sponsored product (retail-media): audit margin and pricing first; the SKU may need a price adjustment, not a campaign pause.
Sibling cards merchants should reference together
| Card | Why pair it with Criteo Wasted Spend | What the combination tells you |
|---|---|---|
| Total Spend | Denominator for the waste percentage. | Whether 5% wasted on a €100k account is meaningful (€5k) or whether 15% wasted on a €5k account is noise. |
| Zero-Conversion Spend | Companion alert card; campaign-level granularity. | Wasted Spend rolls up across line items; Zero-Conversion shows individual offenders. |
| ROAS | Pausing wasted line items mechanically lifts ROAS. | Sets the expected ROAS gain after cleanup. |
| Spend by Campaign | Per-campaign breakdown. | Confirms whether wasted spend is concentrated in one campaign group or spread across many. |
| Conversion Lag | Late-arriving conversions can rescue line items from the bucket. | Don’t pause until conversion lag has settled (allow 7 days). |
| Conversion Rate Trend | The conversion-engine signal. | If account-wide CR dropped, “wasted” line items may just be victims of a measurement issue, not real failures. |
| AdRoll Wasted Spend | Cross-retargeting peer. | Cross-platform waste comparison; if both have similar zero-conversion line items targeting the same audiences, the audience is the problem, not the platform. |
| Google Ads Wasted Spend | Different funnel position; cross-channel waste check. | Google Ads waste is keyword-driven; Criteo waste is audience and catalogue-driven. Different fixes. |
Reconciling against the vendor’s own dashboard
Where to look in Criteo’s own dashboard:Criteo Management Centre → Reporting → Custom Report → Group by Line Item or Audience Segment, sort Conversions ASC.Criteo doesn’t surface “wasted spend” as a dedicated UI; reconcile by sorting the Custom Report ascending by conversions and filtering to spend > €100. The bottom rows match this card’s wasted-spend list. For catalogue product-sets specifically, Reporting → Catalogue Performance → Sort by Conversions ASC shows under-performing product-sets. Why our number may legitimately differ from Criteo:
| Reason | Direction | Why |
|---|---|---|
| Threshold definition | This card stricter | We exclude line items with <3 days live or <€100 spend (statistical noise). Criteo’s UI shows all line items regardless. |
| Time zone | Boundary days off | Criteo uses advertiser-account TZ; this card uses UTC. The 30-day window can shift by 1 day. |
| View-through lookback | Ours undercounts conversions for recent days | Criteo’s 7-day view-through means a “zero-conversion” line item in this card may pick up conversions in the next 7 days. Always wait 7 days after a line item enters this list before pausing, the conversions might just be lagging. |
| Conversions API health | Ours undercounts on iOS | If CAPI is down, iOS and Safari conversions disappear; line items reading “zero” may actually have iOS conversions. Audit CAPI before pausing. |
| Currency | None expected | Both use account currency. |
| Source | Expected relationship | What causes legitimate divergence |
|---|---|---|
adroll.adr_wasted_spend | Cross-retargeting peer. | If the same audience definition (e.g. cart-abandoner-30d) is wasted on both platforms, the audience is the problem. If wasted only on Criteo, the catalogue / inventory-fit is the issue. |
facebook_ads.fac_wasted_spend | Cross-platform waste benchmark. | Meta wasted spend often concentrates on prospecting audiences; Criteo on retargeting and Commerce Media. Pattern differences inform allocation, not 1:1 reconciliation. |
google_ads.gads_wasted_spend | Cross-channel waste pattern. | Google waste is keyword-level; Criteo is audience and catalogue-level. Different shapes. |
| Shopify / BC / Adobe Out-of-Stock SKU report | Catalogue-feed root-cause check. | Many Criteo product-sets in the wasted bucket are out-of-stock or low-stock SKUs the feed still pushes. Cross-reference to the inventory side. |
Known limitations / merchant FAQs
A line item is in the “wasted” list but I think it’s working; what’s wrong? Three usual causes for a false positive on Criteo:- Conversions API outage, iOS / Safari conversions silently dropped. Audit Criteo Pixel & Tag Manager for CAPI errors; restore the feed and the line item recovers in 7 days.
- View-through lookback hasn’t settled, the line item just hit the 30-day spend threshold and view-through hasn’t credited yet. Wait 7 days.
- Conversion-tag misfire, the storefront’s Criteo pixel has a CSP block, GDPR-consent regression, or a script-loader race. Check tag-firing rate in Criteo Tag Manager.