Do I need Conversions API if I already have the Facebook Pixel?

Yes. Browser-side pixel tracking loses 20-35% of events due to ad blockers, iOS restrictions, and cookie limitations. Conversions API sends data server-to-server, bypassing these gaps. Running both together with event deduplication gives you the most complete data set.

How do I check if my Facebook Pixel is firing correctly?

Use three tools: the Meta Pixel Helper Chrome extension shows real-time pixel fires on your site, Events Manager Test Events tab lets you verify events as you browse, and Events Manager Diagnostics flags missing parameters or duplicate events. Check all three after installation.

What is the minimum number of conversions Facebook needs to optimize?

Facebook needs approximately 50 conversions per week per ad set to exit the learning phase. If you cannot hit 50 purchases per week, optimize for an event higher in the funnel like Add to Cart or Initiate Checkout, then switch to Purchase once volume grows.

Can I use one Facebook Pixel across multiple domains?

Yes, but you must configure Aggregated Event Measurement for each domain separately in Events Manager. Each domain gets its own set of 8 prioritized events. For cross-domain tracking like landing page to checkout on different domains, first-party cookies will not carry over. Use Conversions API to bridge the gap.

Field Notes Updated May 2026 11 min read

Facebook Pixel & Conversion Tracking Setup in 2026: The Complete Stack

Browser pixel alone isn't enough anymore. Here's the multi-layer tracking setup every account spending real money should have.

If you're still running just the browser pixel, you're losing 15-30% of conversion signal post-iOS 14. The fix is a stack: browser pixel + CAPI + offline conversion uploads + match quality monitoring.

Layer 1: Browser pixel (the basics)

Standard Facebook pixel embedded in your site. Fires events client-side via JavaScript. Required as the foundation, but increasingly unreliable due to:

Browser ad blockers (~25% of users)
iOS Intelligent Tracking Prevention
Cookie consent rejections in EU
Slow page loads where pixel doesn't fire before user leaves

Setup verification: install Pixel Helper extension, visit your site, verify Page View fires. Then trigger Add to Cart, Initiate Checkout, Purchase. All should fire with correct values.

Layer 2: Conversions API (CAPI)

Server-side event tracking. Your server sends events directly to Facebook's API, bypassing browser limitations. The single highest-impact tracking improvement available.

Implementation paths:

Native integration (Shopify, WooCommerce, BigCommerce, Magento) — easiest, takes 30 minutes
Stape.io / Server GTM — works for any platform, $20-50/mo, no code
Custom backend implementation — for engineering teams who want full control

Match quality target: 6.5+ in Events Manager. Below 5, the signal is weak even though events fire.

Real account: enabled CAPI on top of browser pixel. Not 24% more conversions happened — 24% more got REPORTED. Same money, better visibility.

Layer 3: Offline conversion uploads

For B2B/SaaS where conversions happen after the trial ends, in CRM, or via sales team. Upload these conversions back to Facebook so the algorithm can optimize for actual revenue, not just trial signups.

Methods:

Salesforce / HubSpot / Pipedrive native integrations
CSV upload via Events Manager
API push from custom CRM

Layer 4: Match quality monitoring

Send the right user identifiers to maximize matching:

Hashed email (most important)
Hashed phone
External ID (your user ID, hashed)
IP address + user agent (auto-captured)
fbp / fbc cookies (auto-captured if present)

The more identifiers per event, the better the match. Aim for match quality 6.5+. Below 5 means most events aren't connecting to a Facebook user.

Aggregated Event Measurement (AEM)

Required for iOS 14+ tracking. Set up your conversion event priority list (max 8 events per domain). Most important conversion event goes first; less important events get less precise data on iOS.

Typical priority for e-commerce:

Purchase
Initiate Checkout
Add to Cart
View Content

FAQ

Is CAPI optional?

Technically yes. Practically no for any account spending more than $1k/month. Leaving 20%+ signal on the table.

Match quality 5.0 — is that bad?

Below average. You're losing some matches. Add more identifiers (especially hashed email).

Do I need both browser pixel and CAPI?

Yes — they deduplicate via event_id. Browser fires what it can; CAPI fills the gaps. Together they're more reliable than either alone.

Bottom line

Browser pixel + CAPI is mandatory. Match quality 6.5+ minimum. AEM properly configured. Offline conversion uploads for downstream events. Skip any of these and you're running with worse data than your competitors.