Skip to main content
Card class: HeroCategory: Ad Platform

At a glance

Sum of spend on Meta adsets that produced zero attributed purchase conversions in the period. The “where the budget bled with nothing to show” card. Note: Meta is not a keyword-driven platform like Google Search; the unit of “wasted spend” here is the adset (or ad), not the keyword.
What it countsSUM(spend) for every adset whose actions[purchase] count was zero in the period, account-level. Adsets with non-purchase conversions (engagement, video views, traffic) but zero purchases are still flagged if your account objective is Sales.
Insights API levelAdset-level. The card aggregates wasted-spend across all zero-conversion adsets to a single account total. Drill-down by adset is in Zero-Conversion Spend.
CurrencyAccount currency.
Attribution modelWhatever the account is configured for (default 7d/1d post-iOS 14.5). An adset reads as “zero-conversion” if no purchase was attributed within that window.
iOS 14.5+ ATT impactSignificant. ATT-blocked iOS conversions don’t appear in actions[purchase] for Pixel-only accounts. An adset that “really” converted on iOS but lost the attribution gets flagged here as wasted. Without CAPI, this card over-states wasted spend by 15, 30%. With CAPI live, the gap narrows.
CAPI vs Pixel-onlyPixel-only: false-positives common (real iOS conversions invisible). CAPI live: closer to truth but still some modeled-conversion noise.
Conversions vs all-conversionsThis card uses purchase conversions only. An adset with zero purchases but lots of add-to-carts will still flag as wasted. Use All Conversions for the broader view.
Frequency cap relevanceAdsets capped early in the period may show low spend AND low conversions, mathematically zero-conversion, practically just throttled. Audit before pausing.
Time window30D (last 30 days; not vs prior).
Alert trigger>$0 (any zero-conv adset over the threshold). The default threshold is “any spend on any zero-conversion adset”. Tightening the threshold (e.g. “spend >$100 on zero-conversion adset”) reduces noise.
Rolesowner, marketing, finance

Calculation

Calculated automatically from your Meta Ads (Facebook) 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 US activewear merchant. 30-day window 02 Apr 26 to 01 May 26. Sales-objective account, Pixel-only (CAPI rollout planned for 15 May 26). iOS share 58%.
AdsetCampaignSpend ($)Purchases (Meta-attributed)Wasted?
LAL 1% (purchasers)Advantage+ Shopping (cold)4,20038No
LAL 3% (engagers)Advantage+ Shopping (cold)2,1005No
LAL 5% (video viewers)Advantage+ Shopping (cold)1,8000Yes (false positive risk)
Interest: yoga + 30-45 + femaleManual broad1,40011No
Interest: pilates + 25-40 + femaleManual broad1,1000Yes
Interest: gym-equipment + 25-50 + maleManual broad8000Yes
Custom audience: cart-abandoners 7dRetargeting48022No
Custom audience: site-visitors 90dRetargeting3208No
Account total$12,20084$3,700 wasted (30.3%)
What this is telling you:
  1. 3,700of3,700 of 12,200 spend (30%) produced zero attributed purchases. That’s the headline. But on a Pixel-only account with 58% iOS share, expect 15, 25% of “wasted” spend to be false positives, real iOS conversions that didn’t make it through ATT. The “real” wasted spend is probably $2,500, 2,900.
  2. The “LAL 5% video viewers” adset is borderline. $1,800 spent, zero attributed purchases. Two reads: (a) genuinely the wrong audience (LAL based on video views is a weak signal for purchase intent) → pause. (b) iOS conversions invisible without CAPI → wait for CAPI rollout 15 May, re-evaluate. Pragmatic choice: pause now, re-test post-CAPI.
  3. The two interest-based broad adsets (1,100+1,100 + 800 = $1,900) are clearer waste. Interest targeting on cold audiences is noisy at the best of times; for a Sales objective, lookalikes outperform interest targeting 70% of the time. Pause both, redirect spend to the LAL 1% adset (already at 9× ROAS).
  4. Retargeting custom audiences performed strongly ($800 spend, 30 conversions, 26.7× ROAS on the headline). Retargeting is iOS-resilient because the audience is already in the Pixel cookie pool from prior site visits. If anything, scale these up (within frequency limits, current freq is 3.2 in 7 days, room to push to 4-4.5).
  5. Action priority: (a) pause “Interest: gym-equipment” immediately (clearest waste), (b) pause “Interest: pilates” today, (c) put “LAL 5% video viewers” on watch until CAPI is live, (d) reallocate the freed-up $2,300 to LAL 1% and retargeting audiences. Expected ROAS lift: 8, 14% on the account.
Quick sanity tests:
  • Wasted spend rising while ROAS holding = budget being spread to too many adsets (consolidate).
  • Wasted spend rising while ROAS dropping = audience saturation (refresh creative or expand).
  • Wasted spend constant while ROAS rising = healthy mix (the wasted bucket is just the experimentation cost).
  • Wasted spend = 0 while ROAS = 4× = excellent OR you’ve stopped testing (no new audiences). Test something new.

Sibling cards merchants should reference together

CardWhy pair it with Wasted SpendWhat the combination tells you
Zero-Conversion SpendThe per-adset drill-down. This card sums; that card lists.Which specific adsets to pause.
Total SpendThe denominator for a wasted-spend percentage.Whether 30% wasted is a small problem (1k)orlarge(1k) or large (30k).
Spend by CampaignCampaign-level view of where waste clusters.Whether wasted spend is concentrated in one campaign (easy fix) or spread (creative or audience issue).
Conversions by CampaignThe numerator side.Identify which campaigns convert vs which don’t.
Conversion Rate TrendIf wasted spend is rising AND CR is dropping, the issue is post-click (landing page, stockouts, pricing).Diagnose whether waste is upstream (wrong audience) or downstream (broken funnel).
Frequency / Impressions TrendA high-frequency wasted adset is creative-fatigue waste; a low-frequency wasted adset is audience-quality waste.Different fixes for different shapes.
Google Ads Wasted SpendCross-platform wasted-spend peer (keyword-driven).Compare share-of-waste across platforms.
GA4 Paid Social SessionsIndependent attribution check. If GA4 shows the “wasted” adset DID drive sessions and conversions, it’s an iOS attribution gap, not real waste.Distinguish false-positive waste from real waste before pausing.

Reconciling against the vendor’s own dashboard

Where to look in Meta Ads Manager: Meta Ads Manager → Ad Sets → sort by “Purchases” ascending, filter Spend > 0. Adsets at the top of the sorted list with non-zero spend and zero purchases are the wasted-spend bucket. Sum their “Amount Spent” column to reconcile against this card. Other Ads Manager views relevant to wasted spend:
  • Reports → Predefined → Adset Performance: same data in a downloadable report.
  • Audience Insights: helps diagnose why an adset wasted, audience saturation, frequency cap, mismatched intent.
  • Delivery → Learning Phase status: adsets stuck in Learning often spend without converting. Different cause, same symptom.
Why our number may legitimately differ from Meta:
ReasonDirectionWhy
Time zoneBoundary days offMeta uses ad-account TZ for purchase counting; this card uses UTC. An adset that converted just after midnight TZ may register as “zero conversion” in this card’s window.
Attribution window changesDirection dependsA 28d→7d switch hides longer-cycle conversions, more adsets read as “wasted” under tighter windows.
Modeled conversions inclusionLower waste in our cardModeled conversions count toward actions[purchase]. Pixel-only accounts get modeled fill that Meta credits to specific adsets, reducing the “zero-conversion” pool.
Ingest lagOurs higher waste for “today”Recent (1, 4h) conversions may not be in yet; an adset that converted in the last hour reads as zero-conv. Yesterday and earlier are stable.
Advantage+ opacitySame on the headlineAdvantage+ Shopping internally allocates spend across audiences invisibly; the per-adset purchase count rolls up cleanly.
Cross-connector reconciliation:
CardExpected relationshipWhat causes legitimate divergence
google_analytics.ga_revenue_by_channelIf GA4 attributes Paid Social revenue to a campaign that this card flags as wasted, the iOS attribution gap is the cause.Real iOS conversions invisible to Pixel show up in GA4 (with Consent Mode v2) but not in Meta.
shopify.total_revenueUTM-tagged Meta-source revenue should account for any “real” conversion the wasted adset drove.Without UTM tags, Shopify can’t attribute back to specific adsets.
google_ads.gads_wasted_spendIndependent paid platform.Google Ads waste is keyword-driven (zero-conversion search terms); Meta waste is adset-driven (zero-conversion audiences). Different mechanics.

Known limitations / merchant FAQs

iOS 14.5 ATT and wasted-spend, the structural answer: ATT-blocked iOS users still convert; their conversions just don’t reach Pixel. Without CAPI, adsets serving heavily to iOS audiences look “wasted” because attributed purchases are below the actual purchases. Expect 15, 30% false-positive rate on this card for Pixel-only DTC accounts. Wait for CAPI before pausing iOS-heavy adsets. What’s the practical CAPI rollout playbook for this card? The standard playbook (see ROAS card) applies. Specifically for wasted-spend reduction:
  1. Roll out CAPI for purchase events first, that’s what this card counts.
  2. Verify Meta’s Events Manager shows the deduplicated event volume rising 20, 40% post-rollout.
  3. Wait 14 days for Meta’s attribution model to stabilise.
  4. Re-read this card. Wasted-spend total typically drops 15, 30%.
  5. Now pause whatever still flags as wasted, those are real losers.
How do I interpret modeled conversions for wasted-spend? Meta’s modeling can claim conversions for specific adsets that “should have” converted on iOS based on similarity to other audiences. Modeled conversions reduce the wasted-spend pool but can be wrong (model claims a conversion that didn’t really happen for that adset). On Pixel-only accounts, you get under-counting in raw Pixel + over-counting in modeling, the two roughly cancel. On CAPI-live accounts, modeling drops to 5, 12% and the wasted-spend reading is more accurate. Why is Advantage+ Shopping never on the wasted list? Advantage+ campaigns aggregate spend internally across audiences and placements. Even if some internal segment is wasting, the campaign-level (or single-adset) total reads as having conversions. You can’t see waste inside Advantage+ without breaking out audience signals via separate manual campaigns. This is the same opacity trade-off as Google PMax. Meta-vs-Google-Ads attribution differences for wasted spend: Google Ads waste is keyword-driven: search terms that triggered ads but produced zero conversions. Granular and easy to actuate (add as negative keywords). Meta waste is audience-driven: adsets where the audience signal didn’t lead to purchase. Coarser; the fix is pausing or reframing the audience, not adding negatives. Both platforms typically run 10, 30% wasted spend on a healthy account. Below 10% you’re not testing enough; above 30% you’re not pruning enough. Can I trust today’s wasted-spend figure? No, today’s reading is unreliable. Recent conversions (last 1, 4 hours) haven’t ingested. Adsets that converted in the morning may still read as zero-conversion this afternoon. Read the rolling 7-day or 30-day figure, not today’s. Multi-account aggregation, how does wasted-spend roll up? Sum the wasted-spend dollar amount across accounts; don’t sum percentages. A 500wastedspendaccountat50500 wasted-spend account at 50% waste is meaningfully smaller than a 50,000 account at 8% waste, even though 50 > 8. Why does Meta say 15× ROAS but Shopify says 3×, AND I have $5k of “wasted” spend? The wasted-spend headline is consistent with the iOS gap. iOS users converted, Meta didn’t see it via Pixel, the adsets serving iOS look wasted. Meanwhile Meta’s modeling on the OTHER (converting) adsets inflates them, hence the 15× ROAS. Both phenomena have the same cause: ATT broke the Pixel-attribution chain. CAPI partially fixes both. Pixel vs CAPI dual-implementation impact on this card: If Pixel and CAPI both fire properly with deduplication, an adset that converted on iOS will register the conversion via CAPI (server-side, ATT-immune). The adset doesn’t read as wasted. If Pixel + CAPI dedup is broken, you can double-count conversions, which makes some adsets read with inflated conversion counts and the card under-states wasted spend. Test dedup before trusting either direction of this card’s reading.

Tracked live in Vortex IQ Nerve Centre

Wasted Spend is one of hundreds of KPI pulses Vortex IQ tracks across Meta Ads (Facebook) 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.