At a glance
The alert that fires when Meta’s conversion tracking has silently stopped reporting while ads keep spending. Tags fail quietly, the Pixel and Conversions API stop sending purchase events, and Aggregated Event Measurement throttles delivery on a signal it can no longer measure. It watches for clicks continuing to rise while confirmed conversions collapse below the level you would expect, or for the Pixel and CAPI event-match rate dropping below a healthy threshold. The goal is to catch the break inside the same iOS attribution window, before a day of spend reports as wasted and Meta’s optimiser starts mis-bidding on a broken signal. Caveat: a tracking break and a genuine demand drop look identical on a ROAS card alone, so this card exists to tell them apart.
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 apparel brand on Shopify with the official Meta Sales Channel app providing CAPI. A theme deploy at 02:00 on 14 Mar 26 removed a script include that the Pixel depended on. All figures are illustrative.- The alert fires at 02:35, about 35 minutes after the break. Clicks kept rising on the normal overnight pattern, but observed conversions fell well below half of expected and the match rate dropped from 91% to 41%. 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 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 bidding quality. Meta keeps spending and optimising on a signal it can no longer see. Within hours the optimiser 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 Pixel script include, then confirm in Meta Events Manager → Test Events that both Pixel and CAPI events return and deduplicate.
- Recovery is not instant. Once tracking is restored, AEM and the modeled-conversion layer take time to recalibrate. Expect reported conversions to undershoot for a short period after the fix before they normalise.
- Clicks up + conversions near zero + match rate collapsed = tracking break. Engineering fix.
- Clicks 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). Audit before it becomes a hard break.
Sibling cards merchants should reference together
Reconciling against Meta Ads Manager
Where to look in Meta Ads Manager: The authoritative place to confirm a break is Meta Events Manager → Data Sources → your pixel/dataset → Overview, which shows live event volume, and the Test Events tab, which shows whether Pixel and CAPI events are arriving and deduplicating. The Diagnostics tab flags dropped or malformed events. Ads Manager itself shows the downstream effect (conversions and ROAS falling) but not the cause; Events Manager shows the cause. Other Meta views that look related but are not:- Aggregated Event Measurement settings: configures which events Meta will measure post-iOS. Useful context but not a live health monitor.
- Conversions API “Event Match Quality” score: a periodic quality grade, not a real-time break detector. It updates too slowly to catch a same-window failure.
Cross-connector reconciliation:
Known limitations / merchant FAQs
How is this different from a normal conversion drop? A demand drop lowers conversions on every tracking path at once and leaves the Pixel-to-CAPI match rate intact. A tracking break lowers measured conversions while clicks keep rising and usually collapses the match rate. This card is tuned to the second pattern. If conversions and clicks fall together, look at Conversion Drop Alert instead. What usually causes a break? The common culprits are a theme or template deploy that removes or reorders the Pixel script, a consent-banner change that blocks the Pixel until acceptance, a checkout-flow change that skips the purchase event, an expired or rotated CAPI access token, or a CAPI gateway outage. After any of these, expect this card to be the first to react. Why does it watch theevent_id match rate?
Because a half-broken setup is the hardest to spot manually. If the Pixel breaks but CAPI keeps firing (or vice versa), total conversions may only dip rather than crater, but the deduplicated match rate falls sharply. The match-rate condition catches the half-broken case that a raw conversion count would miss.
Can a deploy trip this even though nothing is actually broken?
Occasionally. A consent-mode change that delays the Pixel until after acceptance can briefly look like a break before events catch up. The 30-minute sustained condition is there to filter transient blips, but a confirmed fire still deserves a Test Events check.
How fast can I expect to be alerted?
Within minutes of a sustained divergence, well inside the iOS attribution window, which is the whole point: catching it before a full day of spend reports as wasted and the optimiser starts mis-bidding.
After I fix it, why are conversions still low for a while?
Once tracking is restored, Aggregated Event Measurement and Meta’s modeled-conversion layer take time to recalibrate. Reported conversions can undershoot for a short period after the fix. Confirm the fix in Events Manager → Test Events rather than waiting on the Ads Manager number to fully normalise.
Can I tune the thresholds?
Yes. The expected-conversion ratio and the match-rate floor are both configurable per profile in the Alert Rules tab. Tighten them on high-spend accounts where even a short break is costly; loosen them on low-volume accounts where small samples are noisy.