Quick answer: Meta pixel vs Conversions API: the pixel tracks in the browser, the Conversions API from your server. Use both, with deduplication.
If you run Facebook or Instagram ads, Meta needs to know what happens after someone clicks: did they view your quote page, submit a form, book a call? There are two ways to tell it, and in 2026 most businesses should use both.
The Meta pixel
The pixel is a small piece of JavaScript on your website. When someone visits, it runs in their browser and sends events to Meta: PageView, Lead, Contact, Purchase and so on.
The problem: browsers increasingly block or limit it. Ad blockers, Safari’s tracking prevention, iOS privacy settings, cookie consent banners and short cookie lifetimes all mean a share of real visits and leads never reach Meta.
The Conversions API (CAPI)
The Conversions API sends events from your server (or a service you use) directly to Meta, rather than from the visitor’s browser. Because it doesn’t rely on the browser, it isn’t stopped by ad blockers or browser restrictions in the same way.
It can also send events that never happen in a browser, such as a lead becoming a customer in your CRM, or a phone sale.
Why use both
Meta recommends running the pixel and the Conversions API together:
- The pixel captures browser signals (like the fbp and fbc cookies) that help match visitors to Meta users
- CAPI fills in events the pixel misses
- Together they give Meta a more complete picture, which usually means better optimisation and more accurate reporting
Deduplication: don’t count leads twice
If both the pixel and CAPI report the same lead, Meta needs to know it’s one lead, not two. That’s done with deduplication: send the same event name and a matching event ID from both. Meta then keeps one and discards the duplicate.
Most good integrations handle this automatically. Check in Events Manager that your events show as deduplicated and that lead counts match your inbox.
Event match quality
Events Manager shows an event match quality score for CAPI events. It reflects how much customer information (hashed email, phone, name, location, IP address, browser ID) you send, which helps Meta connect the event to a real person. Higher match quality generally means better attribution and optimisation. Aim for “Good” or above.
How to set it up
From easiest to most technical:
- Platform integrations. WordPress (Meta’s official plugin or many form and e-commerce plugins), Shopify, Wix, Squarespace, WooCommerce, GoHighLevel and HubSpot have built-in pixel and CAPI options.
- Conversions API Gateway. A Meta-provided setup that runs on a cloud server and sends pixel events server-side. Little coding, small monthly hosting cost.
- Server-side Google Tag Manager. Common for businesses already using GTM. More control, more setup.
- Direct integration. A developer sends events from your website’s backend or CRM.
Check it’s working
In Events Manager → your dataset:
- Events from both “Browser” and “Server” sources
- Deduplication working (look for the deduplication status)
- Event match quality Good or better
- Your Lead count matching real enquiries
Then submit a test enquiry using the Test events tab and confirm it arrives once.
Privacy
You’re sending visitor and customer data to Meta. Your privacy policy should say so, and if you serve visitors outside Australia you may need consent banners. Don’t send sensitive information, such as health conditions, in event data.
Sources and further reading
Written by Gregory
20 years building websites and running lead generation, mostly with my own money on the line. Based in Sydney, working with clients worldwide. How I work →