Do I still need Meta Pixel if I set up Conversions API?

Yes. Run both. The Pixel captures client-side signals the server misses (scroll depth, time on page), while CAPI catches events that ad blockers and iOS privacy settings strip from the Pixel. Together they give you 90-95% event coverage versus 50-60% with Pixel alone.

What Event Match Quality score should I aim for?

Above 6.0 out of 10. Below 6, Meta cannot reliably match your server events to Facebook users, which means your conversion data barely improves ad delivery. Send hashed email, phone, fbc, and fbp parameters to reach 7-8+.

How does event deduplication work between Pixel and CAPI?

Send the same event_id in both your Pixel event and your CAPI event. Meta matches them by event_name + event_id and keeps only one. Without deduplication, Meta counts every conversion twice, which inflates your reported results and confuses the optimization algorithm.

Which CAPI setup method is best for agencies managing multiple clients?

Direct API integration. It gives you full control over event parameters, lets you route events from multiple client domains through one server, and supports custom deduplication logic. Partner integrations work per-store and do not scale across client portfolios.

Field Notes Updated May 2026 10 min read

Meta Conversions API (CAPI) Guide: Setup That Recovers Lost Tracking

CAPI fixes 20-30% of the conversion signal lost to iOS 14 and ad blockers. Here's the implementation that actually works (without breaking your pixel).

Meta Conversions API sends event data server-to-server, bypassing browser limitations. The single biggest tracking improvement available post-iOS 14. Most accounts I audit haven't set it up, leaving 20-30% of signal on the table.

What CAPI actually fixes

iOS 14+ users who blocked tracking via ATT
Browser-level ad blockers (~25% of users)
Cookie consent rejections (EU)
Pixel firing failures (slow page, bot blocking)
Conversions happening server-side (subscriptions, completed orders)

Implementation paths in order of difficulty

Easiest: Native Shopify integration. Settings → Apps → Facebook & Instagram. Enable CAPI in 5 minutes. Same for WooCommerce, BigCommerce, Magento — all have native modules.

Moderate: Server-side GTM via Stape.io. $20-50/mo. Works with any platform. Set up a server-side container, route events through it to Meta. Takes a couple hours but no engineering needed.

Hardest: Custom backend implementation. Direct API integration. Best for engineering teams who want full control over event payload and timing.

Critical: deduplication

Run browser pixel AND CAPI simultaneously. They'll fire the same events for many users. Without deduplication, every conversion gets counted twice.

Set the same `event_id` on both browser pixel event and CAPI event for the same conversion. Meta uses event_id to deduplicate. Most native integrations handle this automatically; custom implementations need to do it manually.

Verify in Events Manager: should show "Server" and "Browser" sources for same events. If counts double, dedup is broken.

Match quality optimization

The more user identifiers you send per event, the better Meta matches the event to a user, the more useful the data. Send all of:

Hashed email (most important)
Hashed phone
External ID (your user ID)
IP address (auto)
User agent (auto)
fbp / fbc cookies if available

Match quality target: 6.5+ in Events Manager. Below 5.0 = weak signal. Below 3.0 = barely matching anyone.

Real progression of one account's tracking. From browser-only to full CAPI with proper identifiers, +24% conversions reported on the same actual sales.

Verifying CAPI is working

Events Manager → your pixel → Test Events tab. Trigger a real conversion. Should see both browser and server source within 30 seconds. If only one shows, integration is broken on the missing side.

FAQ

Does CAPI replace the pixel?

No — they work together. Pixel for what it can capture, CAPI for what pixel can't.

Will CAPI affect my CPA?

Reported CPA usually drops because more conversions get attributed. Actual revenue doesn't change.

Is CAPI mandatory?

Not technically. Practically yes — leaving 20%+ signal unrecovered is competitive disadvantage.

Bottom line

Set up CAPI alongside your browser pixel. Send full identifiers (especially hashed email). Verify dedup works. Aim for match quality 6.5+. Worth half a day of setup for permanent +20% reported conversions.