top of page
Typographic Black and Blue.png

How Bach AI Monitors Your CAPI Server-Side Event Health Continuously

Your developer set up Conversion API three months ago. Events were flowing. Meta Events Manager showed green check marks. Everything looked good. Two weeks ago a Shopify app update silently broke the server-side fire. Your Event Match Quality dropped from 7.2 to 4.1. Meta is now optimizing on degraded signal and you don't know it yet.


CAPI fails silently. It doesn't show a red banner. Meta still 'receives events' — they're just degraded. Bach AI watches your CAPI health 24/7 and surfaces degradation the moment it starts.


Why CAPI Health Degrades Without Warning


Server-side events are more fragile than they look. Six failure modes we see across Indian D2C accounts:


  • Shopify app updates that overwrite custom CAPI logic.

  • Tag manager container changes that strip required parameters.

  • API token expiry when access tokens aren't refreshed properly.

  • Shopify theme changes that remove user identifier collection (email, phone hashes).

  • Code deployments to custom backends that miss the CAPI hook.

  • Meta API version deprecations when CAPI implementation uses outdated SDK versions.


Each of these silently kills your match quality without throwing an error. Meta keeps receiving events. They just become less useful.


What Bach AI Monitors in CAPI


1. Event Match Quality (EMQ)


Meta scores every event 1-10 based on the user identifiers attached (email, phone, IP, user agent, external_id, fbp, fbc, click ID, etc.). Above 7 is healthy. Below 6 is degraded. Below 5 is critical. Bach AI tracks EMQ daily and alerts on drops above 1.0 points.


2. Deduplication rate


When pixel and CAPI both fire, they should be deduplicated via shared event_id. Bach AI tracks the dedup rate. Below 80% means events are double-counting; above 95% is healthy.


3. Event coverage


Are all funnel events flowing through CAPI? ViewContent, AddToCart, InitiateCheckout, Purchase. Missing any of these reduces Meta's optimization signal.


4. Parameter completeness


Value, currency, content_ids, user_data hashes — each parameter has a presence threshold. Bach AI flags when parameter completeness drops.


5. CAPI latency


Server-side events should hit Meta within 60 seconds of the user action. Bach AI tracks the median latency; anything above 5 minutes degrades optimization.


6. Event volume vs pixel ratio


Healthy CAPI typically reports 10-25% more Purchase events than pixel (because CAPI bypasses ad-blockers and Safari/iOS restrictions). If CAPI reports the same or fewer events than pixel, something is broken.


The CAPI Health Card Inside Bach AI


Open the CAPI Health card and you see today's health summary:


CAPI health: 81/100. EMQ: 7.4 (healthy, ↑ 0.2 vs last week). Dedup rate: 92% (healthy). Event coverage: complete. Parameter completeness: 88% (alert — value parameter missing on 12% of Purchase events). Latency: 24s median (healthy).

Click any metric for the trend chart and the specific fix when something is wrong.


Real Examples of CAPI Issues Bach AI Catches


Example 1: EMQ silent drop


EMQ dropped from 7.8 to 4.3 over 5 days. Root cause detected: 'em' (email hash) parameter no longer present in events from /thank-you/* pages. Likely cause: recent Shopify theme update. Fix: re-add customer.email to the CAPI event template; code snippet provided.

Example 2: Dedup failure


Dedup rate dropped from 94% to 61% after May 8. Root cause: event_id mismatch between browser pixel and server-side fires. Fix: align event_id generation logic across both sources; code review needed in main.liquid and CAPI middleware.

Example 3: Coverage gap


AddToCart events stopped flowing through CAPI starting May 11. Browser pixel still firing AddToCart normally. Likely cause: Shopify app update removed the server-side AddToCart hook. Fix: re-install the CAPI app's AddToCart trigger or add manual webhook.

Why CAPI Match Quality Matters More in 2026


Three reasons EMQ is more important now than it was two years ago:


  • iOS 17/18 signal loss — pixel-only setups now lose 20-40% of iOS events. CAPI recovers most of it, but only if match quality is high enough for Meta to attribute those events back.

  • Advantage+ Shopping campaigns — Meta's AI-driven campaigns rely heavily on conversion signal quality. Low EMQ means weaker AI performance.

  • Value Optimization bidding — Meta needs accurate value parameters to optimize for high-value buyers. Missing or wrong value parameters disable Value Optimization's edge.


Brands with EMQ above 7.5 typically see 12-25% better Meta-attributed ROAS than otherwise-identical brands with EMQ below 5.5.


What 'Healthy CAPI' Actually Looks Like


Five characteristics of a CAPI setup that's working:


  1. EMQ between 7.0 and 9.5 across all events.

  2. Dedup rate above 90% between pixel and CAPI.

  3. All four funnel events firing (ViewContent, AddToCart, InitiateCheckout, Purchase).

  4. Value parameter present on 95%+ of Purchase events with correct currency.

  5. CAPI reporting 10-25% more events than pixel (recovery of blocked tracking).


Hitting all five takes deliberate setup. Maintaining all five takes monitoring.


How Wittelsbach AI Monitors CAPI Continuously


Bach AI runs the full CAPI health scan every 24 hours and pings you the moment any metric degrades. Fixes come with code snippets and validation steps. No more monthly surprises where you discover CAPI broke three weeks ago. Bach AI is live at [app.wittelsbach.ai](https://app.wittelsbach.ai). Two clicks to connect Meta.


Frequently Asked Questions


What's a good Event Match Quality (EMQ) score?


7.0 and above is healthy. 8.0+ is excellent. Below 6.0 is degraded and starting to hurt optimization. Below 5.0 is critical — Meta is treating your events with low confidence. Bach AI alerts whenever EMQ drops more than 1.0 point in a week or falls below 6.0.


Why does CAPI break so often?


CAPI is implementation-heavy. Every change to your tech stack — theme updates, app installs, API version deprecations, code deployments — can break it. Pixel breaks less often because Meta hosts the pixel SDK. CAPI runs on your infrastructure, so your infrastructure changes can break it.


Do I need CAPI if my pixel is working fine?


Yes, in 2026 you absolutely do. Pixel alone loses 20-40% of iOS events (Safari ITP, iOS 14.5+ ATT). CAPI recovers most of that loss. Pixel-only accounts have systematically degraded optimization signal — and you won't see the lost performance, just lower-than-expected ROAS over months.


Can Bach AI tell me if I'm sending the right user parameters to CAPI?


Yes. Bach AI lists every parameter you're sending vs every parameter Meta recommends, with completeness percentages per parameter. The most common gaps in Indian D2C: missing phone number hashes, missing external_id, missing fbp/fbc cookies on server-side events. Each gap has a specific fix.


How does Bach AI know when CAPI broke vs when it was always degraded?


Bach AI keeps a rolling 90-day history of every CAPI metric. We detect 'sudden drops' (a metric that was healthy for weeks suddenly degrades) separately from 'chronic issues' (a metric that's been degraded since you connected). The fix urgency differs — chronic issues need a one-time setup pass, sudden drops need immediate root cause.

Comments

bottom of page