At a glance
The alert that fires when Snapchat’s conversion tracking has silently stopped reporting while ads keep spending. Tags fail quietly, the Snap Pixel and the Conversions API (CAPI) stop sending purchase and add-to-cart events, and Snapchat’s Goal-based bidding throttles delivery on a signal it can no longer measure. It watches for swipe-ups continuing to rise while confirmed conversions collapse below the level you would expect, or for the Snap Pixel and CAPI event-match rate dropping below a healthy threshold. Because every Snapchat ad lives inside the app and every swipe-up lands on a mobile in-app browser, a single broken script on a mobile template can take down the entire tracking layer at once. The goal is to catch the break inside the same 7-day-click / 1-day-view attribution window, before a day of spend reports as wasted and Dynamic Ads lose the audience signals they depend on. Caveat: a tracking break and a genuine demand drop look identical on a ROAS card alone, so this card exists to tell them apart.
| What it watches | The health of Snapchat conversion tracking: the browser-side Snap Pixel events, the server-side Conversions API events, and the match rate between them. It compares the live conversion rate against the recent expected baseline for the same swipe-up volume. |
| Trigger condition | Swipe-ups rising while combined Snap Pixel and CAPI conversions run below roughly half of expected for more than about 30 minutes, OR the deduplication match rate between Snap Pixel and CAPI falling below roughly 80%. Both thresholds are tunable per profile in the Sensitivity tab. |
| Why match rate matters | A healthy dual setup deduplicates Snap Pixel and CAPI events by a shared event identifier. When that match rate falls, either the Pixel or the server side has stopped sending, or the IDs no longer line up, which is the early signature of a half-broken implementation. |
| Snapchat’s CAPI | Snapchat’s server-to-server conversion path. It carries the conversions the in-app browser Pixel cannot see, and it feeds the Dynamic Ads catalogue audiences (viewed, added-to-cart, purchased). If CAPI breaks, dynamic retargeting pools dry up first. |
| In-app browser fragility | Snapchat has no desktop placements, so 100% of swipe-up traffic lands in the Snapchat in-app browser on mobile. Consent banners, third-party cookie restrictions and slow mobile pages all interfere with the Snap Pixel here, which makes the server-side CAPI path the more reliable signal and an outright CAPI break the most damaging failure mode. |
| Chart type | Alert list. Each row names the affected Pixel or CAPI dataset, the expected vs observed conversion level, and the match rate. |
| What it is not | Not a demand metric. A real fall in sales also lowers conversions; this card is calibrated to fire on the swipe-up-rising-conversions-falling pattern that signals measurement failure rather than lost demand. |
| Currency | Not currency-denominated; the unit is a count and a rate. |
| Time window | RT (real-time, evaluated continuously on the standard refresh). |
| Roles | owner, marketing, engineering |
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
Lumen & Loft, a UK homeware brand on Shopify running Dynamic Ads off a catalogue synced from the store feed, with CAPI delivered through the official Snapchat Shopify integration. A theme deploy at 23:00 on 13 Apr 26 removed a script include that the Snap Pixel depended on. All figures are illustrative.| Time window | Swipe-ups | Expected conversions | Observed conversions | Event match rate | State |
|---|---|---|---|---|---|
| 12 Apr, all day | 5,400 | ~162 | 165 | 90% | Healthy |
| 13 Apr, 21:00 to 23:00 | 480 | ~14 | 14 | 89% | Healthy |
| 13 Apr, 23:00 to 23:40 | 410 | ~12 | 2 | 38% | Alert fires |
| 13 Apr, 23:40 onward | rising | rising | near zero | falling | Alert sustained |
- The alert fires at 23:40, about 40 minutes after the break. Swipe-ups kept rising on the normal evening pattern (Snapchat delivers heavily in the late evening to its Gen-Z and younger-millennial audience), but observed conversions fell well below half of expected and the match rate dropped from 89% to 38%. That divergence is the tracking-break signature.
- The match-rate collapse is the tell. The CAPI server events kept arriving (Shopify’s server-side path was untouched), but the in-app browser Pixel stopped, so the deduplicated pairs fell apart. A pure demand drop would lower conversions on both paths together and would not crater the match rate.
- Every minute of delay costs measured ROAS and starves Dynamic Ads. Snapchat keeps spending and optimising on a signal it can no longer see, and the viewed, added-to-cart and purchased audiences that drive catalogue retargeting stop refilling. Within hours the auction starts mis-allocating budget toward audiences that merely look like they stopped converting.
- The fix is an engineering action, not a marketing one. Roll back the theme deploy or re-add the Snap Pixel script include, then confirm in Snapchat Events Manager that both Pixel and CAPI events return and deduplicate.
- Recovery is not instant. Once tracking is restored, Snapchat’s Goal-based bidding and the modeled-conversion layer take time to recalibrate, and the Dynamic Ads audiences need to rebuild. Expect reported conversions to undershoot for a short period after the fix before they normalise.
- Swipe-ups up + conversions near zero + match rate collapsed = tracking break. Engineering fix.
- Swipe-ups down + conversions down + match rate steady = genuine demand drop, not this card.
- Match rate falling slowly over days = creeping implementation drift (consent changes, script reorder, feed sync drift). Audit before it becomes a hard break.
Sibling cards merchants should reference together
| Card | Why pair it with Snap Pixel / Conversions API Tracking Broken | What the combination tells you |
|---|---|---|
| Conversion Drop Alert | The conversion-side view of the same event. | Conversions falling while swipe-ups hold separates a tag failure from a demand fall. |
| ROAS Dropped Below Threshold | A tracking break shows up there as a false ROAS drop. | Confirms the ROAS drop is measurement, not demand, so you do not cut spend in error. |
| Conversions Trend | The daily series for context. | A vertical cliff (not a gradual slope) points to a tracking break. |
| Active Catalogue Ads on Out-of-Stock SKUs | The catalogue side of the same plumbing. | If the feed and CAPI both wobble, suspect a single store-feed deploy, not two unrelated faults. |
| Spend on Campaigns with Active Feed Rejections | Feed health that often breaks alongside CAPI. | Rejections plus a CAPI break point to a catalogue or feed sync fault at the root. |
| Mobile Landing Pages with Poor Web Vitals | The in-app browser environment the Pixel runs in. | A slow page that never finishes loading can stop the Pixel firing, masquerading as a break. |
| Wasted-Spend Burst (3-day spike) | The spend consequence of optimising blind. | A burst that starts the same hour as this alert is spend chasing a broken signal. |
Reconciling against Snapchat Ads Manager
Where to look in Snapchat Ads Manager: The authoritative place to confirm a break is Snapchat Events Manager, reached from Ads Manager at ads.snapchat.com by opening the Events Manager (Business Details > Events Manager, or business.snapchat.com), then selecting the affected Snap Pixel or Conversions API dataset. The event activity view shows live event volume and source (browser vs server), and the Test Events tool shows whether Snap Pixel and CAPI events are arriving and deduplicating in real time. The Diagnostics panel flags dropped, malformed or low-quality events. Ads Manager itself shows the downstream effect (conversions and ROAS falling) but not the cause; Events Manager shows the cause. Other Snapchat views that look related but are not:- Attribution settings: configures the click and view windows (commonly 7-day-click / 1-day-view). Useful context but not a live health monitor.
- Event Quality score: a periodic quality grade in Events Manager, not a real-time break detector. It updates too slowly to catch a same-window failure.
- Catalogue health: flags product-feed issues that affect Dynamic Ads, but a clean catalogue can still sit behind a broken CAPI dataset.
| Reason | Direction | Why |
|---|---|---|
| Detection lead time | Ours fires earlier | Snapchat’s Event Quality scores update on a slow cadence; this card watches the live swipe-up-to-conversion divergence and fires within minutes. |
| Expected-baseline basis | Variable | The expected conversion level is derived from the account’s own recent ratio. A genuine shift in audience mix can move the baseline, which is why the swipe-up-rising condition is required before firing. |
| Match-rate sampling | Marginal | Snapchat’s match-quality figures are sampled and lagged; the live match rate this card watches is closer to real time and can read lower or higher in the moment. |
| Attribution model | Window only | Snapchat’s default 7-day-click / 1-day-view window backfills some view conversions a day late; this card reads the live event stream, not the attributed total, so the two can diverge until the window closes. |
| Time zone | Boundary only | Snapchat uses ad-account time zone; this card uses UTC. Relevant only at day boundaries, not for a within-window break. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
google_analytics.gtm_tag_fire_failure_alert | If both fire at once, a site-wide deploy broke tags | If only Snapchat fires, the break is in the Snap Pixel or CAPI path specifically, not the whole tag layer. |
shopify.total_revenue | Real orders continue during a tracking break | If Shopify orders keep flowing while Snapchat conversions crater, the conversions are real but unmeasured: a tracking problem, confirmed. |
google_ads.conversion_tracking_broken_alert | Both firing points to a shared root cause | Snapchat alone points to a Snapchat-specific Pixel/CAPI failure. |