> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Zero-Conversion Spend, Criteo > Zero-Conversion Spend 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](/nerve-centre/overview#metrics-types-explained) • **Category:** [Ad Platform](/nerve-centre/connectors#connectors-by-type) ## At a glance > Real-time alert: spend on any Criteo **campaign** that is older than 7 days and has zero attributed conversions in the trailing 30 days. Companion to [Wasted Spend](/nerve-centre/kpi-cards/criteo/wasted-spend) (which surfaces line-item / segment / product-set granularity); this card surfaces campaign-level offenders, the top of the hierarchy. **The 7-day age threshold respects Criteo's view-through lookback**: campaigns younger than 7 days haven't had their attribution window settle, so a "zero" reading is meaningless. Above 7 days, zero conversions is a real signal. | | | | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Sum of `metrics.spend` on Criteo campaigns where (a) campaign age >= 7 days, (b) trailing 30D attributed conversions = 0 (post-click + post-view). Reports the campaign list and total spend in the bucket. | | **Cost basis** | Mostly CPC; sums billable cost. | | **Currency** | Single advertiser-account currency. | | **Conversion attribution** | **30-day post-click + 7-day post-view**. The view-through lookback is why we require >7 days campaign age before this card triggers. | | **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 false-positive risk.** ATT can produce zero-conversion reads on iOS-heavy campaigns where conversions are happening but unmeasurable. Audit Conversions API health before treating any campaign as truly wasted. | | **Catalogue-feed dependency** | Catalogue-driven campaigns can flicker into and out of this bucket as feed health changes. A feed re-sync can rescue a "wasted" campaign within hours. | | **Time window** | Trailing 30 days at any point in time. The card refreshes daily; alert fires the moment a campaign crosses 7 days old with zero conversions. | | **Alert trigger** | `>$0 on any campaign >7D old`. Fires once per qualifying campaign (de-duplicates on the same campaign for a 30-day cooldown). | | **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 6 active Criteo campaigns. Today is 02 May 26. Account currency EUR. | Campaign | Spend (€, trailing 30D) | Days live | Conversions (trailing 30D) | Status | | -------------------------------------------- | ----------------------- | --------- | -------------------------- | ---------------------------- | | Lower-funnel retargeting (PDP visitors) | 14,200 | 412 | 1,420 | Healthy | | Mid-funnel consideration (basket abandoners) | 6,800 | 288 | 510 | Healthy | | Commerce Media (publisher prospecting) | 4,400 | 156 | 124 | Healthy | | Sponsored product (priority SKUs) | 1,600 | 92 | 78 | Healthy | | Spring fashion clearance push | 1,420 | 28 | 0 | **In list** | | New audience test: 365-day lapsed | 320 | 9 | 0 | **In list** (just qualified) | | **Account total in zero-conversion bucket** | **€1,740** | - | **0** | **6.4% of spend** | What the alert is telling you: 1. **Two campaigns are in the bucket.** "Spring fashion clearance push" at €1,420 over 28 days and "New audience test: 365-day lapsed" at €320 over 9 days. Together 6.4% of account spend. 2. **The clearance campaign has had 28 days to convert and produced zero.** This is real waste, not measurement noise. The diagnostic order: (a) is the clearance product-set rendering on the right placements? (b) is the audience definition over-broad (clearance buyers are price-sensitive; if the audience is general retargeting it'll click but not convert)? (c) is the landing page set to a clearance category page or to the storefront homepage (storefront homepage tanks clearance conversion). 3. **The 365-day-lapsed test has only 9 days; the alert just qualified it.** Recommended action: wait another 7 days (cumulative 16 days) to give view-through credit a chance; if still zero, this audience is too cold for retargeting (lapsed users beyond 90 days rarely retarget effectively). 4. **The clearance campaign should be paused or restructured by week 5 (35 days).** Restructure options: tighten audience to "viewed clearance category", switch landing page to the clearance category, A/B test creative against a discount-percentage hero. If after restructure it remains zero, pause. 5. **Compared to the same merchant's [`cri_wasted_spend`](/nerve-centre/kpi-cards/criteo/wasted-spend) which shows €4,260 wasted at line-item / segment / product-set level**, the campaign-level read here (€1,740) is a subset. The difference (€2,520) is line-item / segment / product-set-level waste *within* otherwise-healthy campaigns. Both reads are valuable: this card tells you which campaigns to pause; the line-item card tells you which sub-elements to surgically fix. Action playbook when the alert fires: * **Day 0 (alert fires)**: log it; do not act yet. * **Day 0 to 7**: audit Conversions API health, attribution-tag firings, and catalogue-feed health. False positives are usually visible by day 3. * **Day 7 to 14**: if the campaign is still zero, restructure (audience, landing page, creative, bid strategy). * **Day 14 to 30**: if restructure didn't recover, pause. * **Cooldown**: paused campaigns that previously triggered this alert can be re-launched after 60+ days with new structure; the 30-day deduplication cooldown prevents the alert re-firing the moment a re-launched campaign crosses 7 days old. ## Sibling cards merchants should reference together | Card | Why pair it with Criteo Zero-Conversion Spend | What the combination tells you | | ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | | [Wasted Spend](/nerve-centre/kpi-cards/criteo/wasted-spend) | Line-item / segment / product-set granularity. | This card surfaces campaigns; Wasted Spend surfaces sub-campaign offenders. Pair to see both layers. | | [Total Spend](/nerve-centre/kpi-cards/criteo/total-spend) | Denominator for the percentage. | Whether €1k zero-conversion on a €100k account matters or whether €1k on a €5k account is a fifth of spend. | | [ROAS](/nerve-centre/kpi-cards/criteo/roas) | Account efficiency. | If account ROAS is healthy despite zero-conv campaigns, the working campaigns are subsidising the dead weight. | | [Conversion Lag](/nerve-centre/kpi-cards/criteo/conversion-lag) | Late-arriving conversions can rescue a campaign from this list. | Don't pause until the lookback has settled (allow 7 days minimum, 14 for Commerce Media). | | [Spend by Campaign](/nerve-centre/kpi-cards/criteo/spend-by-campaign) | Full per-campaign view. | Where the alert sits in the broader spend distribution. | | [Conversion Rate Trend](/nerve-centre/kpi-cards/criteo/conversion-rate-trend) | Account-wide CR signal. | If CR collapsed everywhere, the zero-conv campaigns are victims of a measurement issue, not real failures. | | [AdRoll Zero-Conversion Spend](/nerve-centre/kpi-cards/adroll/zero-conversion-spend) | Cross-retargeting peer. | If similar audience definitions are zero on both, the audience is the problem. | | [Google Ads Zero-Conversion Keywords](/nerve-centre/kpi-cards/google-ads/zero-conversion-spend) | Different funnel-position peer. | Google's keyword-level zero-conv is a different shape from Criteo's audience / catalogue-level. | ## Reconciling against the vendor's own dashboard **Where to look in Criteo's own dashboard:** > [Criteo Management Centre → Campaigns → All Campaigns view, sort Conversions ASC](https://commerce.criteo.com), then filter to campaign age >= 7 days. Criteo's UI doesn't badge "zero-conversion campaigns" explicitly; reconcile by sorting the campaign list ascending by conversions. Campaigns with 0 conversions and >7 days live should match this card's list exactly. **Why our number may legitimately differ from Criteo:** | Reason | Direction | Why | | --------------------------- | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Time zone** | Boundary days off | Criteo uses advertiser-account TZ; this card uses UTC. Campaigns that crossed the 7-day age threshold yesterday in advertiser TZ may not have crossed it yet in UTC. | | **View-through lookback** | Ours undercounts on recent days | A 9-day-old campaign with zero conversions may pick up view-through credits over the next 5 days. The 7-day age threshold was set deliberately to match the view-through window; older campaigns are reliable. | | **Conversions API health** | Ours undercounts iOS conversions | If CAPI is broken, iOS conversions silently disappear. The campaign reads zero in both this card and Criteo's UI; the fix is restoring CAPI, not adjusting the threshold. | | **Custom conversion types** | Different scoping | If the merchant added new conversion types (e.g. "newsletter signup") mid-period, the campaign may have those conversions but no purchase conversions. This card sums all conversion types Criteo tracks; the UI breakdown shows per-type. | | **Currency** | None expected | Both use account currency. | | **Archived campaigns** | Same in both | Archived campaigns are excluded from both views. | **Cross-connector reconciliation:** | Source | Expected relationship | What causes legitimate divergence | | ------------------------------------------------------------------------------------------------------ | ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | [`adroll.adr_zero_conversion_spend`](/nerve-centre/kpi-cards/adroll/zero-conversion-spend) | Cross-retargeting peer; campaign-level zero-conv. | If matching audience definitions are zero on both, the audience layer is the issue. | | [`facebook_ads.fac_zero_conversion_spend`](/nerve-centre/kpi-cards/facebook-ads/zero-conversion-spend) | Cross-platform peer; ad-set level zero-conv. | Meta's failure modes are usually creative-fatigue or audience-saturation; Criteo's are catalogue and audience-fit. Different fixes. | | [`google_ads.gads_zero_conversion_spend`](/nerve-centre/kpi-cards/google-ads/zero-conversion-spend) | Cross-platform zero-conv pattern. | Google is keyword-level; Criteo is campaign-level. The shape of "wasted" is different. | | [Shopify / BC / Adobe Out-of-Stock SKU report](/nerve-centre/kpi-cards/shopify/total-revenue) | Catalogue-feed root-cause check. | Many zero-conv Criteo campaigns are catalogue-driven and pointing at out-of-stock SKUs. | ***
Documentation cross-reference (the 7-day rule rationale) The 7-day campaign-age threshold isn't arbitrary. Criteo's default attribution window includes a 7-day post-view lookback, meaning a conversion can credit back to a campaign up to 7 days after the impression. **A campaign that's only 3 days old hasn't had time to settle**, the campaign might already have conversions in flight that haven't yet appeared in the report. Triggering on day 3 produces 30 to 50% false positives. Day 7+ is the lookback floor. From day 8 onward, every conversion that *could* attribute to the campaign already has. A zero reading at that point is real. The trade-off: you're slower to flag genuinely-broken campaigns by 4 to 7 days vs a more aggressive threshold. On most accounts this trade is worth it; the alternative is alert-fatigue from false-positive triggers in the first week. For Commerce Media campaigns specifically (longer consideration windows), consider extending the threshold to 14 days. The 7-day rule is calibrated to retargeting; Commerce Media prospecting users may need 10 to 14 days to convert from first impression. Vortex IQ's default uses 7 days for all campaign types; tune to 14 for Commerce Media via the manifest if your account skews heavily prospecting.
## Known limitations / merchant FAQs **A campaign just qualified for the alert (8 days old, zero conversions); what's the first thing to check?** Conversions API health, in this exact order: (1) is the Criteo CAPI receiving events for this campaign's audience? (2) is the client-side pixel firing? (3) is the catalogue feed serving valid product IDs to this campaign? (4) is the landing page resolving (no 404s, redirects, broken UTMs)? Usually one of these is the cause; about 60% of "zero-conversion" 8-day-old alerts on Criteo turn out to be technical, not strategic. **Why does the alert wait 7 days?** Criteo's view-through window is 7 days. A campaign that's 5 days old may have view-through conversions still backfilling against impressions delivered on day 1. Triggering before day 7 produces frequent false positives, especially on retargeting where view-through credit is a meaningful share of total credit. **Day 7+ is the post-lookback floor**, conversions that could have credited already have. **My new test campaign just qualified; I expected zero conversions during testing. Is this a false positive?** The alert is doing its job: any campaign older than 7 days with zero conversions deserves human attention, even if the merchant intentionally launched it as a low-volume test. **Acknowledge the alert, mark the campaign as "experimental"** if your alert tooling supports tags, and re-evaluate after 30 days. If you don't expect conversions for 60+ days (truly long-cycle B2B-ish use cases), Criteo isn't the right platform; this card's threshold is calibrated to consumer-grade conversion windows. **The same campaign keeps re-entering the alert; how do I stop the noise?** A 30-day deduplication cooldown applies: once a campaign triggers, it won't re-alert for 30 days even if it stays in the bucket. After 30 days without a conversion, the alert refires; this is intentional, the campaign is genuinely stuck and should be paused or restructured. If you've already restructured and are awaiting results, suppress the alert manually for 30 to 60 days via the alert configuration. **Why is the alert spend small (€1,740) but Wasted Spend is much bigger (€4,260)?** Different granularity. This card alerts on whole campaigns where every line item is zero-converting. Wasted Spend reaches into otherwise-healthy campaigns to surface zero-converting line items, audience segments, and catalogue product-sets nested inside them. **Wasted Spend will always be greater than or equal to Zero-Conversion Spend** by definition (it's a strict superset). **Should I just pause every campaign in the alert?** No. The right order: audit (CAPI, tag, feed) → restructure (audience, landing page, creative) → pause as last resort. Pausing loses learning data; restructure preserves it. If a campaign has been in the alert for 60+ days through multiple restructures, pause is appropriate. If 14 days, restructure first. **My Commerce Media campaign just qualified at day 8; should I treat it the same as retargeting?** No. Commerce Media users have longer consideration windows (10 to 14 days from first impression to conversion). For Commerce Media campaigns, treat the day-8 alert as informational and re-evaluate at day 21. If still zero at day 21, then audit and restructure. The default 7-day threshold is calibrated to retargeting; Commerce Media tolerance should extend. **Can I exclude specific campaign types from the alert?** Yes, via the manifest configuration. Common exclusions: brand-defence campaigns (where the goal is impression share, not conversion), creative-test campaigns (where the alert intentionally shouldn't fire during the test), low-stakes evergreen brand campaigns. Exclusions are case-by-case; default is "alert on everything" because most cases benefit from human review. **My iOS-share is 65%; is this alert reliable?** Less reliable than on Android-heavy accounts. ATT post-opt-out users are essentially invisible to Criteo, so a campaign serving disproportionately to opted-out iOS users may have real conversions Criteo can't see. **Two checks before treating as real waste**: (a) is your Conversions API and Identity Graph rollout audited? (b) is the campaign's iOS impression share >70% (vs account average \~65%)? If yes to both, discount the alert by 20 to 30%; the campaign may be working but unmeasurable. **Does Vortex IQ flag campaigns that recover after a restructure?** Yes, the alert auto-clears the next 30D refresh after the campaign records its first conversion. The alert UI shows recovered campaigns with a "recovered" tag for 14 days post-recovery so the merchant can see which restructures worked. *** ### Tracked live in Vortex IQ Nerve Centre *Zero-Conversion Spend* 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.