Skip to main content
Metrics type: Supporting Metrics • Category: Ad Platform

​
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.

​
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.
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
Quick reads:
  • 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

​
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.
Why our number may legitimately differ from Snapchat: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

Why 72 hours and not 24? A single day of zero conversions is often noise: a slow weekday, a small ad squad, or a conversion that lands just after the window. Three consecutive days of zero-conversion spend is a pattern worth acting on. The 72-hour window trades a little detection speed for far fewer false fires. Is zero-conversion spend always wasted? Not always. Some of it is unmeasured conversion, where the Snap Pixel or the Conversions API failed to capture an iOS purchase, which is a real risk because Snapchat runs entirely on mobile in-app and every conversion depends on a device-level event firing. Always check Snap Pixel / Conversions API Tracking Broken before pausing. A small amount of zero-conversion spend is also normal for new squads in the learning phase; the floor is there to suppress that. How do I tell a broken creative from a fatigued one? Look at the history. A squad that never converted from launch usually has a broken or mis-targeted swipe-up destination, often a wrong product URL or, for Dynamic Ads, a broken catalogue deep link. A squad that converted recently and then stopped is fatiguing; CTR Trend will usually show the swipe-up rate declining into the burst, and Snapchat fatigue arrives fast because the audience cycles quickly. My Dynamic Ads squad fired but the creative looks fine. What now? Dynamic Ads pull from your product catalogue, so the fault is often in the feed rather than the ad. Check whether the swipe-up deep link 404s, whether the featured SKUs are out of stock, or whether the feed has active rejections. The sibling cards Active Catalogue Ads on Out-of-Stock SKUs and Spend on Campaigns with Active Feed Rejections isolate those causes. Why does the test squad not fire even though it has zero conversions? Its spend is below the configured floor. Tiny test budgets routinely run a few days without a conversion, so the floor suppresses them. Adjust the floor in the Alert Rules tab to match what counts as material spend for your account. Should I let Vortex IQ auto-pause these? Auto-pause can be enabled for high-spend bursts, but most teams prefer a manual review because a Pixel or CAPI break can masquerade as wasted spend on Snapchat. The conservative default is to surface the recommendation and let a human confirm before pausing. Why did the figure change after I read it this morning? Conversions ingest with a lag, and Conversions API events deduplicate against Pixel events and can attach after the fact. A squad that looked fully wasted at 09:00 may show a few late-attributed purchases by midday. Trust the figure once the window has settled rather than acting on the freshest hour. Why does the unit say ad squad and not keyword? Snapchat is not a keyword-driven platform like paid search. There are no search keywords to flag, so the unit of wasted spend is the ad squad (or the individual ad). Many wasted squads on Snapchat are creative-fatigue or swipe-up-destination casualties rather than mistargeted audiences.

​
Tracked live in Vortex IQ Nerve Centre

Wasted-Spend Burst (3-day spike) is one of hundreds of KPI pulses Vortex IQ tracks across Snapchat Ads 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.