At a glance
The alert that catches runaway budget on a broken or fatigued creative before it eats the week. It watches each ad set for a burst of zero-conversion spend over a rolling 72-hour window and fires when that spend crosses a configured floor. Where the steady-state Wasted Spend card reports the cumulative total, this card is the early-warning version: it fires on the recent spike, not the long tail, so the team can pause the offending ad set the same day. Caveat: a burst of zero-conversion spend can be a tracking break rather than a genuinely failing creative, so confirm against CAPI/Pixel Tracking Broken before pausing.
| What it counts | Spend on an ad set in the last 72 hours that produced no attributed conversions, evaluated per ad set rather than at the account total. |
| Why 72 hours | A single bad day can be noise; a three-day run of zero-conversion spend is a pattern. The 72-hour window separates a genuine burst from one slow day. |
| Alert trigger | Zero-conversion spend above a configured floor in the last 72 hours on any ad set. The floor is tunable per profile in the Sensitivity tab so it matches the spend level you consider material. |
| Why per ad set | Wasted spend hides at the ad-set level. An account total can look fine while one ad set quietly burns budget on a dead creative. Watching each ad set surfaces the culprit. |
| Attribution model | ”Zero conversions” is measured on the ad account’s configured attribution window, typically 7-day click + 1-day view. An ad set with conversions outside that window still counts as zero here. |
| iOS 14.5+ ATT impact | Some apparent zero-conversion spend is really unmeasured conversion (Pixel or CAPI not capturing iOS purchases). Pair with the tracking-health card to avoid pausing an ad set that is actually converting but not reporting. |
| Chart type | Alert list. Each row names the ad set, its 72-hour spend, and confirms zero attributed conversions. |
| Currency | Account currency. Single currency per ad account. |
| Time window | RT (real-time, rolling last 72 hours, recomputed on the standard refresh). |
| Roles | owner, 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 UK skincare brand running several ad sets under one Advantage+ campaign. Reading taken at 14:00 on 14 Mar 26. Account currency GBP. The configured 72-hour floor is illustrative.| Ad set | Spend last 72h (£) | Attributed conversions | Flagged | Likely cause |
|---|---|---|---|---|
| Cold prospecting, video A | 1,920 | 38 | No | Healthy |
| Cold prospecting, video B (new) | 760 | 0 | Yes | Broken landing link in the creative |
| Retargeting, carousel | 540 | 22 | No | Healthy |
| Lookalike 2%, static | 410 | 0 | Yes | Creative fatigue, no clicks converting |
| Test ad set, low budget | 70 | 0 | No (below floor) | Too small to matter |
- Two ad sets fire. Video B and the Lookalike static each ran three days of spend with zero attributed conversions above the floor. The test ad set also has zero, but its £70 is below the floor and is suppressed as expected noise.
- The two fires have different causes. Video B is a brand-new creative that never converted from day one, which usually means a broken or mis-targeted landing link in the ad. The Lookalike static converted last week and stopped, which is the fatigue pattern. Same alert, different fix.
- Confirm it is not a tracking break first. If CAPI/Pixel Tracking Broken is also firing, the zero conversions may be unmeasured rather than absent. Check that before pausing, otherwise you pause an ad set that is actually working.
- The cost of waiting is the whole week. £760 plus £410 over three days projects to roughly £2,700 a week if left running. That is budget that could move to the healthy cold-video-A ad set.
- The action is a pause, then a diagnosis. Pause both flagged ad sets to stop the bleed, then fix Video B’s link and refresh or retire the fatigued Lookalike creative. Reactivate once corrected.
- New ad set + zero conversions from day one = broken link or mis-targeting. Check the destination URL.
- Established ad set + conversions stopped = fatigue. Refresh the creative.
- Zero conversions + tracking alert also firing = suspect measurement, not the creative.
- Below floor = ignore. It is test-budget noise by design.
Sibling cards merchants should reference together
| Card | Why pair it with Wasted-Spend Burst | What the combination tells you |
|---|---|---|
| Wasted Spend | The cumulative total this burst feeds into. | Whether the burst is a one-off spike or part of a chronic waste pattern. |
| Zero-Conversion Spend | The steady-state version of the same idea. | Which ad sets persistently fail to convert, beyond the recent burst. |
| CAPI/Pixel Tracking Broken | The false-positive check. | Whether the zero conversions are real or just unmeasured. |
| Overspending Campaigns | The budget-pacing view. | Whether the burst is also pacing ahead of plan, compounding the waste. |
| CTR Trend | Leading indicator of fatigue. | A CTR decline before the burst confirms creative fatigue as the cause. |
| Spend by Campaign | Where the burst sits in the campaign structure. | Locates the parent campaign for budget reallocation. |
| Google Ads Wasted-Spend Burst Alert | The same alert on paid search. | Whether the waste is Meta-specific or a store-wide conversion problem. |
Reconciling against Meta Ads Manager
Where to look in Meta Ads Manager: Meta Ads Manager → Ad sets with the date range set to the last 3 days, the “Amount spent” and “Purchases” (or “Results”) columns visible, and sorted by spend. Filter to ad sets with purchases equal to zero. Meta does not surface a “wasted-spend burst” alert natively, so you reconstruct it by reading the spend-with-zero-results rows. Match the attribution setting to this card’s configured window. Other Ads Manager views that look related but are not:- Cost per result: Meta hides the row or shows a dash when results are zero, which is exactly the case this card surfaces. The dash is easy to scroll past; the alert is not.
- Delivery status: an ad set marked “Active, Learning Limited” may spend without converting; this card catches the spend regardless of the delivery label.
| Reason | Direction | Why |
|---|---|---|
| Time zone | Boundary days off | Meta uses ad-account time zone; this card uses UTC. The 72-hour window edges can fall on different calendar days. |
| Attribution window | Direction depends | An ad set with conversions just outside the configured window reads as zero here and may read as non-zero in Ads Manager if a wider window is selected. Match the windows. |
| Ingest lag | Today over-counts waste | A 1 to 4 hour ingest lag means a very recent conversion may not have landed yet, so the freshest hours can look more wasteful than they are. |
| Modeled conversions | Ours may read higher waste | Modeled conversions can attach to an ad set after the fact; the card refreshes as they arrive. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
facebook_ads.capipixel_tracking_broken | A tracking break manufactures false wasted spend | If the tracking alert is firing, treat the zero-conversion reading as suspect until tracking is restored. |
shopify.total_revenue | Real orders may exist that Meta did not attribute | If Shopify shows Meta-sourced orders in the window, the ad set is converting but unmeasured, not truly wasting. |
google_ads.wasted_spend_burst_alert | Both firing suggests a shared conversion-path problem | Meta alone points to a Meta-specific creative or targeting fault. |