Meta Conversions API vs Pixel: What Changes and Why It Matters

If you advertise on Facebook or Instagram, the Meta Conversions API is now part of a sound tracking setup, not an advanced extra. The Meta Pixel alone misses conversions because of browser restrictions, ad blockers and patchy connections. This guide explains what changes when you add the Conversions API, how the two work together, and what to check when things go wrong.

Quick answer: The Meta Pixel is JavaScript that sends events from the visitor's browser. The Meta Conversions API (CAPI) sends events directly from your server, or a hosted gateway, to Meta. Meta recommends using both together, with deduplication so the same conversion is not counted twice. CAPI improves the reliability of event data, but it does not remove the need for valid cookie consent.

What is the Meta Pixel?

The Meta Pixel (formerly the Facebook Pixel) is a snippet of code on your website. When a visitor views a page, adds to basket or submits a form, the pixel sends an event from their browser to Meta. It uses cookies, such as `_fbp`, and the `fbclid` click identifier to link activity back to ad clicks.

Its weakness is that it depends entirely on the browser. Events can be lost when:

• An ad blocker or privacy extension blocks Meta's scripts.
• Browser tracking protection, such as Safari's Intelligent Tracking Prevention, limits cookie lifetimes.
• The visitor leaves before the page finishes loading.
• The visitor declines cookies, in which case the pixel should not fire at all.

What is the Meta Conversions API?

The Meta Conversions API, often still called the Facebook Conversions API, is a server-to-server connection. Instead of relying on the browser, your website, ecommerce platform or CRM sends event data directly to Meta.

Each server event can include:

• The event name, such as `Purchase` or `Lead`.
• Event time and source URL.
• Customer information parameters, such as email or phone number, hashed with SHA-256 before sending.
• Browser identifiers like `fbp` and `fbc` where available, which help Meta match the event to a person and an ad.
• Custom data such as value and currency.

Because the request comes from a server you control, it is not blocked by ad blockers and is less affected by browser restrictions.

Meta Conversions API vs Pixel: the key differences

| | Meta Pixel | Meta Conversions API | |---|---|---| | Where it runs | Visitor's browser | Your server or a gateway | | Affected by ad blockers | Yes | No | | Can send offline or CRM events | No | Yes | | Setup effort | Low | Moderate | | Needs consent | Yes | Yes, for the same purposes |

The most important line is the last one. CAPI changes how data is sent, not whether you are allowed to send it. If a visitor declines marketing cookies, you should not send their browsing events through the server instead.

Why you should run both

Meta's recommended setup is a "redundant" one: the pixel and CAPI send the same events in parallel. This gives you:

• Better coverage: if the browser event is blocked, the server event can still arrive.
• Better matching: server events can carry hashed customer data, which improves Event Match Quality.
• Richer data: CAPI can send events that never happen in a browser, such as a lead becoming qualified in your CRM or a phone order.

Better data quality feeds Meta's delivery system, which matters for campaign optimisation and audience building.

How deduplication works

Running both means Meta receives two copies of the same event. To avoid double counting, Meta deduplicates using two fields:

1. event_name: must match exactly, for example `Purchase` in both.
2. event_id: a unique ID for that specific conversion, sent identically by the pixel (as `eventID`) and by CAPI (as `event_id`).

If the IDs do not match, or one side is missing them, Meta counts both. This is one of the most common reasons advertisers see inflated conversions after adding CAPI. A transaction ID or a generated unique string stored for that session works well.

Ways to set up the Conversions API

There are several routes, from simple to fully custom:

• Partner integrations: Shopify, WooCommerce, WordPress and many other platforms offer built-in or plugin-based connections. Quickest option, but check what events and parameters they actually send.
• Conversions API Gateway: a Meta-provided solution hosted in your own cloud environment, managed through Events Manager.
• Server-side Google Tag Manager: a server container receives events from your web container and forwards them to Meta via a CAPI tag. Flexible, and consistent with GA4 server-side tagging.
• Direct API integration: your developers send events from your backend. Most control, most effort.

Meta Pixel not working? Common problems and fixes

If your Meta Pixel is not working, or numbers look wrong after adding CAPI, check these first.

1. Pixel not firing at all

Use the Meta Pixel Helper browser extension and Events Manager's Test Events tool. Check that the pixel ID is correct and that the tag is not blocked by your consent setup after a visitor has accepted.

2. Pixel firing before consent

If the pixel fires before a visitor makes a choice, that is a compliance issue. Consent Mode v2 only controls Google tags, so Meta tags need their own consent conditions in GTM or your CMP. Our Consent Mode v2 guide covers how to apply additional consent checks.

3. Duplicate conversions

Usually missing or mismatched `event_id` values, or the pixel being installed twice, for example by a plugin and in GTM.

4. Low Event Match Quality

Events Manager scores how well your events can be matched. Low scores usually mean too few customer information parameters are being sent. Add hashed email and phone where you legitimately collect them, and pass `fbp` and `fbc`.

5. Wrong values or currency

Check that value is a number, not a string with a currency symbol, and that currency uses ISO codes such as `GBP`.

6. Events in Events Manager but not in Ads Manager

Make sure the right events are selected as conversion events and that the ad set is optimising for the event you expect.

How to test your setup

1. Open Events Manager, choose your dataset (pixel), and use Test Events.
2. Trigger a conversion on your site.
3. Confirm the event appears from both "Browser" and "Server", and that it is marked as deduplicated.
4. Check the parameters, including value, currency and customer information.
5. Review Event Match Quality and diagnostics over the following days.

FAQs

Does the Conversions API replace the Meta Pixel?

Not usually. Meta recommends running both, with deduplication, for the best coverage and matching.

Do I still need cookie consent if I use the Conversions API?

Yes. Sending data from a server does not change the legal basis you need. Respect visitors' choices for both browser and server events.

Why are my Meta conversions doubled after adding CAPI?

Deduplication is not working. Check that `event_name` and `event_id` match exactly between pixel and server events.

Is the Facebook Conversions API the same thing?

Yes. It was renamed alongside Facebook's rebrand to Meta.

Get your Meta tracking checked

Our Tracking Audit + Fix (£199) checks your Meta Pixel, Conversions API, deduplication and consent conditions alongside GA4 and GTM, then fixes what is broken. Fixed fee, white-label friendly. Get My Audit.

Related reading: Server-side tracking explained.