Facebook & Meta CAPI

Facebook Conversions API and Meta tracking

When Facebook CAPI Events Disappear: How to Debug Server-Side Tracking

by

Facebook CAPI events can fire successfully in GTM preview mode yet never reach Meta—and most store owners have no way to know. The debugging gap is architectural: preview mode confirms the tag fired but cannot confirm Meta accepted it. Response codes (200 success, 400 rejection) require paid server-side log tiers with per-tag activation. Events Manager shows aggregate diagnostics—you see “event issues” but not which specific events failed. Missing Event ID parameters cause 80% of deduplication errors. Event Match Quality scores of 4/10 are typical when sending minimal user parameters. The solution is visibility at the event level: see every delivery status, every response code, every error before problems compound into campaign performance collapse.

The Facebook for WooCommerce Plugin Is Broken Again

by

The official Facebook for WooCommerce plugin has a documented reliability problem—settings disappear without warning, CAPI shows browser-only events, and critical errors occur even with minimal plugins active. GitHub issues and WordPress.org support forums are filled with store owners cycling through the same troubleshooting steps: deactivate, reinstall, reconnect, watch it break again. If you’ve tried everything … Read more

CAPI and Enhanced Conversions Don’t Need Cookies

by

Facebook CAPI and Google Enhanced Conversions don’t need cookies. They use hashed customer data—email, phone number, name, and address—for conversion matching. WooCommerce collects all of this at checkout. The purchase event, your most important conversion, happens after you have customer data. Cookie deprecation changes how you track visitors TO the purchase. It doesn’t change tracking … Read more

Do You Still Need the Facebook Pixel If You Have Server-Side Tracking?

by

If your server-side tracking captures all standard events with complete customer data, the Facebook Pixel is optional. With 42.7% of users running ad blockers and Safari limiting cookies to 7 days, server-side tracking via CAPI bypasses these restrictions entirely. For WooCommerce stores with properly configured CAPI, the Pixel adds page weight without adding value.

Why Isn’t My Facebook Conversions API Tracking All My WooCommerce Purchases?

by

Facebook Conversions API fails to track 30-50% of WooCommerce purchases due to external payment redirects losing fbclid data, iOS 14+ privacy restrictions cutting attribution windows from 28 to 7 days, and cache plugins breaking event deduplication. Server-side tracking that captures purchase data directly from WooCommerce—rather than relying on thank-you page scripts—recovers these missing conversions.