Do I still need the browser pixel if I have CAPI?

Yes, Meta recommends using both the browser pixel and CAPI together in a redundant setup. The browser pixel captures real-time user interactions while CAPI provides reliable server-side backup. When using both, event deduplication (via event_id) ensures events are not double-counted. This dual setup maximizes data coverage and improves overall attribution accuracy.

How do I set up Meta CAPI without coding?

PixelFly makes it easy to set up Meta Conversions API in just 5 minutes without any coding. Simply connect your Meta ad account, add the PixelFly snippet to your website, and server-side events are automatically sent with high Event Match Quality. PixelFly handles deduplication, advanced matching, and all the technical complexity for you.

100% Free - No Account Required

Free Meta CAPI Diagnostics

Check if any website has Meta Conversions API (CAPI) properly configured. Detect browser pixel vs server-side events, evaluate potential Event Match Quality, and get recommendations to maximize your Meta ad performance.

Analyzing Meta Pixel and CAPI configuration...

CAPI Diagnostics Results

Here's what we found about Meta CAPI configuration

out of 100

CAPI Readiness Score

Pixel IDs:

Browser Pixel

Server-Side (CAPI)

Advanced Matching

Event Deduplication

Estimated Event Match Quality (EMQ)

Based on detected parameters — actual EMQ may vary. Check Meta Events Manager for your real score.

Poor (1) Fair (4) Good (6) Great (8+)

Google Tag Manager

Custom Domain Tracking

Cookie Consent

CAPI Provider

Detected Pixel Events

Note: Events fired dynamically via GTM or loaded after initial page render may not appear here.

Issues & Warnings

Recommendations

Actions to improve your Meta CAPI setup

What This Means

Understanding your CAPI diagnostics results

Important: This scan analyzes the initial HTML source code

Conversions API events are sent server-to-server and cannot be fully verified from HTML alone. Events loaded dynamically via GTM, single-page app navigation, or JavaScript may not be detected. For definitive CAPI verification, check Meta Events Manager for the green server icon next to your events.

Ready to set up Meta CAPI?

Get server-side tracking running in 5 minutes with PixelFly

Start Free Trial

Understanding Meta CAPI

Learn the key concepts behind Meta Conversions API and why it matters for your advertising performance

Browser Pixel vs Server Events

The client-side Meta Pixel fires JavaScript in the user's browser to track events. Server-side CAPI sends the same events directly from your server to Meta. Browser events are vulnerable to ad blockers and cookie restrictions, while server events bypass these limitations entirely, ensuring more complete data collection.

Event Match Quality (EMQ)

EMQ is a score (1-10) that measures how effectively Meta can match your server events to user accounts. Higher EMQ leads to better ad targeting, improved lookalike audiences, and lower cost per acquisition. It improves when you send user data parameters like hashed email, phone number, IP address, and browser user agent.

Why Both Are Needed

Meta recommends running both browser pixel and CAPI together. The pixel provides real-time data for dynamic features, while CAPI offers reliable, ad-blocker-proof delivery. Event deduplication (via shared event_id) ensures events are not double-counted. This redundant setup maximizes data coverage and attribution accuracy.

Why Meta CAPI Matters for Your Ads

Without Conversions API, you are leaving significant performance on the table

15-30%

of conversions are missed with browser-only tracking due to ad blockers and iOS restrictions

2-3x

better ROAS reported by advertisers after implementing CAPI alongside browser pixel

Event Match Quality score recommended by Meta for optimal ad delivery and attribution

Meta CAPI Diagnostics FAQ

Common questions about Meta Conversions API and this free diagnostic tool

Meta Conversions API (CAPI) is a server-side tracking solution that sends conversion events directly from your server to Meta's servers, bypassing the browser entirely. Unlike the traditional Meta Pixel which fires JavaScript in the user's browser, CAPI events are sent server-to-server, making them immune to ad blockers, cookie restrictions, and browser privacy changes like iOS 14.5+. This results in more complete and reliable conversion data for your Meta ad campaigns.

There are a few ways to check. In Meta Events Manager, server events appear with a green server icon next to them, distinct from browser pixel events. You can also use this free CAPI diagnostics tool to scan your website - it detects indicators of server-side event delivery, advanced matching parameters, event deduplication setup, GTM server containers, and other signs that CAPI has been properly configured alongside your browser pixel.

Event Match Quality (EMQ) is a score from 1-10 in Meta Events Manager that measures how well your server events can be matched to Facebook user accounts. A higher EMQ means better ad targeting, more accurate attribution, and ultimately lower CPAs. Your EMQ score improves when you send more customer information parameters with your CAPI events, such as hashed email addresses, phone numbers, IP addresses, user agents, and click IDs (fbp and fbc cookies). Meta recommends an EMQ score of 8 or above for optimal performance.

Yes, Meta recommends using both the browser pixel and CAPI together in a redundant setup. The browser pixel captures real-time user interactions and enables features like dynamic ads and real-time optimization signals. CAPI provides a reliable server-side backup that is immune to ad blockers. When using both, event deduplication (via a shared event_id parameter) ensures events are not double-counted. This dual setup gives you the best of both worlds: real-time browser data plus reliable server-side coverage.

PixelFly makes it easy to set up Meta Conversions API in just 5 minutes without any coding knowledge. Simply connect your Meta ad account, add the PixelFly snippet to your website (or use our Shopify/WordPress plugin), and server-side events are automatically sent with high Event Match Quality. PixelFly handles event deduplication, advanced matching with hashed user data, and all the technical complexity behind the scenes. You get reliable CAPI tracking without managing servers or writing integration code.

Set Up Meta CAPI in 5 Minutes

PixelFly connects your website to Meta Conversions API with zero coding. Improve your Event Match Quality and recover lost conversion data instantly.

Start Free Trial Learn More

No credit card required. Cancel anytime.