At a glance
The alert that catches runaway budget on a broken or fatigued ad before it eats the week. It watches each ad squad 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 squad the same day. Snapchat skews young and the audience cycles fast, so a creative that worked last week can go cold quickly, which is exactly when this burst window earns its keep. Caveat: a burst of zero-conversion spend can be a Snap Pixel or Conversions API break rather than a genuinely failing creative, so confirm against Snap Pixel / Conversions API Tracking Broken before pausing.
| What it counts | Spend on an ad squad in the last 72 hours that produced no attributed conversions, evaluated per ad squad rather than at the account total. (On Snapchat the budget-bearing unit is the ad squad, not the keyword; Snapchat is not a keyword-driven platform.) |
| 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 squad. The floor is tunable per profile in the Sensitivity tab so it matches the spend level you consider material. |
| Why per ad squad | Wasted spend hides at the ad-squad level. An account total can look fine while one ad squad quietly burns budget on a dead Single Video or a broken Dynamic Ads link, and Snapchat’s auto-bid delivery can pour a disproportionate share of a campaign budget into a single failing squad. Watching each squad surfaces the culprit. |
| Attribution model | Zero conversions is measured on the ad account’s configured attribution window, commonly 7-day swipe (click) + 1-day view. An ad squad with conversions outside that window still counts as zero here. |
| iOS ATT and mobile-only impact | Snapchat runs entirely inside the app on mobile, so every conversion depends on the Snap Pixel, the Conversions API, or the App Ads Kit firing on a device. Some apparent zero-conversion spend is really unmeasured conversion, where the Pixel or CAPI did not capture an iOS purchase. Pair with the tracking-health card to avoid pausing a squad that is actually converting but not reporting. |
| Chart type | Alert list. Each row names the ad squad, its 72-hour spend, and confirms zero attributed conversions. |
| Currency | Account currency, set at account creation and immutable. 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 Snapchat Ads 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 Gen-Z streetwear brand running several ad squads under one Pixel Purchase campaign. Reading taken at 14:00 on 14 Apr 26. Account currency GBP. The configured 72-hour floor is illustrative.| Ad squad | Spend last 72h (£) | Attributed conversions | Flagged | Likely cause |
|---|---|---|---|---|
| Prospecting, Single Video A | 1,640 | 31 | No | Healthy |
| Prospecting, Story Ad B (new) | 690 | 0 | Yes | Broken swipe-up URL in the creative |
| Retargeting 7d, Collection Ad | 480 | 19 | No | Healthy |
| Dynamic Ads, catalogue squad | 520 | 0 | Yes | Catalogue feed link 404ing on swipe-up |
| Spotlight boost, Single Video C | 360 | 0 | Yes | Creative fatigue, swipe-ups not converting |
| Test squad, low budget | 55 | 0 | No (below floor) | Too small to matter |
- Three ad squads fire. Story Ad B, the Dynamic Ads catalogue squad, and the Spotlight boost each ran three days of spend with zero attributed conversions above the floor. The test squad also has zero, but its £55 is below the floor and is suppressed as expected noise.
- The fires have different causes. Story Ad B is a brand-new creative that never converted from day one, which usually means a broken or mis-targeted swipe-up destination. The Dynamic Ads squad pulls from the product catalogue, so a 404 on the deep link to a single product page can sink the whole squad. The Spotlight video converted last week and stopped, which is the fatigue pattern, faster on Snapchat because the audience skews young and cycles through the same creative quickly. Same alert, different fix.
- Confirm it is not a tracking break first. If Snap Pixel / Conversions API Tracking Broken is also firing, the zero conversions may be unmeasured rather than absent. Check that before pausing, otherwise you pause a squad that is actually working.
- The cost of waiting is the whole week. £690 plus £520 plus £360 over three days projects to roughly £3,900 a week if left running, and Snapchat’s auto-bid can accelerate that if the campaign keeps feeding the failing squads. That is budget that could move to the healthy Single Video A squad.
- The action is a pause, then a diagnosis. Pause the three flagged squads to stop the bleed, then fix Story Ad B’s swipe-up URL, repair the catalogue deep link feeding the Dynamic Ads squad (see Active Catalogue Ads on Out-of-Stock SKUs and Spend on Campaigns with Active Feed Rejections), and refresh or retire the fatigued Spotlight creative. Reactivate once corrected.
- New ad squad + zero conversions from day one = broken swipe-up link or mis-targeting. Check the destination on a real device.
- Dynamic Ads squad + zero conversions = suspect the catalogue feed: a broken deep link, an out-of-stock SKU, or a feed rejection.
- Established ad squad + 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. |
| Snap Pixel / Conversions API Tracking Broken | The false-positive check. | Whether the zero conversions are real or just unmeasured. |
| Active Catalogue Ads on Out-of-Stock SKUs | The catalogue-health check for Dynamic Ads squads. | Whether a Dynamic Ads burst is driven by stock or feed issues rather than the creative. |
| Spend on Campaigns with Active Feed Rejections | The other catalogue-driven waste source. | Whether rejected feed items are draining a Dynamic Ads squad. |
| Mobile Landing Pages with Poor Web Vitals | The destination-quality check. | Whether swipe-ups are landing on a slow in-app page that kills conversions. |
| ROAS Dropped Below Threshold | The return-on-spend view. | Whether the burst is dragging account ROAS below your floor. |
| CTR Trend | Leading indicator of fatigue. | A swipe-up rate 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. |
Reconciling against Snapchat Ads Manager
Where to look in Snapchat Ads Manager: Open Snapchat Ads Manager at ads.snapchat.com, go to the Manage Ads view, select the Ad Squads level, and set the date range to the last 3 days. Add the Spend (Amount Spent) and Purchases (or your primary conversion) columns, then sort by spend and read the squads with conversions equal to zero. Snapchat does not surface a wasted-spend burst alert natively, so you reconstruct it by reading the spend-with-zero-conversions rows. Match the attribution setting (Attribution window selector, commonly 7-day swipe + 1-day view) to this card’s configured window. For Pixel and CAPI health, cross-check in Events Manager at business.snapchat.com. Other Ads Manager views that look related but are not:- Cost per purchase: Snapchat shows a dash or hides the figure when conversions 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 squad in the learning phase may spend without converting; this card catches the spend regardless of the learning label.
| Reason | Direction | Why |
|---|---|---|
| Time zone | Boundary days off | Snapchat uses the ad-account time zone; this card uses UTC. The 72-hour window edges can fall on different calendar days. |
| Attribution window | Direction depends | A squad with conversions just outside the configured window reads as zero here and may read as non-zero in Ads Manager if a wider swipe or view window is selected. Match the windows. |
| Ingest lag | Today over-counts waste | Snapchat reporting ingest lags a few hours, so a very recent conversion may not have landed yet, and the freshest hours can look more wasteful than they are. |
| CAPI deduplication | Ours may read higher waste | Server-side events sent via the Conversions API are deduplicated against Pixel events and can attach to a squad after the fact; the card refreshes as they arrive. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
snapchat_ads.snap_pixel_conversions_api_tracking_broken | A tracking break manufactures false wasted spend | If the tracking alert is firing, treat the zero-conversion reading as suspect until Pixel or CAPI is restored. |
shopify.total_revenue | Real orders may exist that Snapchat did not attribute | If Shopify shows Snapchat-sourced orders in the window, the squad is converting but unmeasured, not truly wasting. |
snapchat_ads.active_catalog_ads_on_out_of_stock_skus | Both firing points a Dynamic Ads burst at the catalogue | Out-of-stock or rejected SKUs can produce zero conversions while the creative itself is fine. |