What is the Facebook Conversions API (CAPI) and why do I need it?
The Facebook Conversions API is a server-to-server integration that sends conversion event data from your server directly to Meta, bypassing the browser-based Meta Pixel. It is needed because iOS 14+ privacy changes, ad blockers, and browser cookie restrictions cause the browser Pixel to miss 20–40% of conversions for most businesses. CAPI ensures Meta receives complete event data regardless of browser-level blocking.
Should I replace my Meta Pixel with CAPI, or run both?
You should run both. The recommended setup is "redundant" — both the browser Meta Pixel and CAPI sending the same events simultaneously, with event ID deduplication configured so Meta only counts each conversion once. The browser Pixel provides faster event delivery and some additional browser-side signals; CAPI provides the fallback that captures events the Pixel misses. Running both maximises data completeness.
What is Event Match Quality (EMQ) and why does it matter?
Event Match Quality is Meta's score (0–10) indicating how well the customer data you send with events can be matched to Meta user profiles. Higher scores mean more conversions are attributed to your ads, better delivery optimisation, and improved ROAS. EMQ is determined by which customer data parameters you send (email, phone, name, address, etc.) and how accurately they are formatted. We optimise your implementation to achieve the highest possible EMQ score.
How does CAPI affect my Facebook ad performance?
CAPI improves ad performance in several ways: more complete conversion data means Meta's delivery algorithm has better signals for audience optimisation; higher Event Match Quality enables more accurate attribution, making your reported ROAS more representative of actual performance; recovering missed conversions gives Advantage+ campaigns more signals to learn from; and better conversion data enables more effective lookalike audience generation.
What customer data parameters should I send with CAPI events?
The most impactful parameters for Event Match Quality are: email address (hashed), phone number (hashed), first name, last name, city, state/region, country, postal/ZIP code, and date of birth. Email and phone number are the highest-impact parameters. All customer data must be SHA-256 hashed before sending. We configure your implementation to capture and hash the maximum set of parameters available at each event point.
Does CAPI require changes to my website?
CAPI sends data from your server, so the implementation approach depends on your platform. For Shopify, there is a native Meta app with built-in CAPI support. For other platforms, we implement CAPI via server-side GTM, a custom server-side integration, or platform-specific webhooks. In all cases, we handle the complete implementation without requiring significant changes to your website's frontend.
How does CAPI handle iOS 14+ privacy restrictions?
iOS 14+ prevents apps from tracking users across apps and websites using Apple's IDFA without explicit consent, and browsers on iOS (Safari, Chrome, Firefox) apply ITP restrictions that limit cookie-based attribution. CAPI bypasses these restrictions by sending data server-to-server, using customer data parameters (email, phone) to match conversions to Meta users rather than relying on device identifiers or cookies.
What is event deduplication and how does it work with CAPI?
Event deduplication prevents Meta from counting the same conversion twice when both the browser Pixel and CAPI send the same event. Deduplication works by including a unique "event_id" parameter with every event — the same event_id in both the Pixel and CAPI event for the same conversion. Meta uses this ID to identify and deduplicate matched events within a 48-hour window. Without correct event IDs, you risk double-counting conversions.
Can CAPI send events for lead generation as well as ecommerce?
Yes. CAPI can send any standard or custom Meta event — ViewContent, AddToCart, InitiateCheckout, Purchase, Lead, CompleteRegistration, Subscribe, FindLocation, and custom events. For lead generation businesses, we implement the Lead event with relevant customer data parameters from your form submissions, sent via both browser Pixel and CAPI for maximum data completeness and Event Match Quality.
How do I know if my CAPI implementation is working correctly?
Meta Events Manager provides diagnostic information including event volume by source (browser Pixel vs. CAPI), Event Match Quality scores, and data quality warnings. After implementation, we validate that events appear with the correct source breakdown, deduplication is working (event volume should increase compared to Pixel-only, not double), and EMQ scores have improved. We monitor these metrics for 7 days post-implementation to confirm correct operation.