NOTE-028 · FIELD NOTE FILED 12 NOV 2026 · REVISED 12 NOV 2026 F-102 F-401
Do you need the Conversions API if the Meta Pixel already works?.
ABSTRACT — Meta recommends the Conversions API alongside the Pixel, not instead of it. What the Pixel can lose, what the server copy adds, when it earns its keep, and when to leave it alone.
Baris Asa, tracking consultant, London · Last checked: November 2026
Usually yes, as an addition to the Pixel, not a replacement. Meta recommends running both. Skip it for now only if the Pixel already sees nearly every order and your Meta spend is small. A quick test: if Events Manager shows clearly fewer Purchases than your shop has orders for the same days, you are losing sales the server copy would catch.“Works” usually means the Pixel fires on a test order. That says the tag is installed. It doesn’t say what share of real orders get through. The test is below.
What is the Conversions API?
The Conversions API is a server-to-server connection that sends website, app and offline events to Meta. The Pixel is code that runs in the visitor’s browser; the Conversions API is your server, shop platform or CRM talking to Meta directly. Meta says the events are processed like events sent with the Pixel (Meta: Conversions API).
Three names get mixed up. The Conversions API is the connection. The Conversions API Gateway and server-side GTM are two ways of sending through it. Meta’s “one-click” option, which needs an existing Pixel, sends website events from Events Manager with nothing for you to host. Offline events, such as sales logged in a CRM, are sent through the Conversions API, because no browser is involved.
What can the Pixel miss, and how would you see it?
Meta’s own guide gives one reason to send server events too: they cover website events that the Pixel “may lose due to network connectivity issues or page loading errors” (Meta: best practices). Think of a buyer who pays and closes the tab before the confirmation page loads.
Meta’s page doesn’t mention ad blockers or browser privacy settings. Those are real causes of lost browser events: the site files them as F-401 (browser-only collection, with ad blockers and Safari cookie limits stopping some sales reaching the platform). That is my field experience, not a Meta statement, and how much you lose varies by audience and device. In your own data it shows as Meta Purchases running below shop orders, often worst on mobile and Safari traffic. Only your numbers settle it.
How do you tell if it matters for you?
- Count the orders in your shop for last week.
- Open Events Manager and count the Purchase events from the Pixel for the same days.
- Compare. In my experience a gap of a few per cent is ordinary, and I start asking questions at double figures. This is a rule of thumb from audits, not a Meta figure. An exact multiple means something else is wrong (F-102 ).
Orders and Purchase events won’t match exactly, because of cancellations, test orders and time zones. Use the same days and the same time zone on both sides. If Meta’s number is well above your shop’s, that often points to double counting, not a missing server copy. Rule out test orders and time zones first, then start with Meta CAPI and Pixel double counting purchases.
When is it worth doing?
| Your situation | Server copy worth it? |
|---|---|
| Meta spend is small and the Pixel sees nearly every order | Probably not yet. Re-check each quarter |
| Pixel sees noticeably fewer orders than the shop | Yes. If you have a Pixel, start with Meta’s one-click option |
| You send server events for other platforms already | Yes, and decide who sends to Meta so only one tool does |
| Leads or sales are closed offline (CRM, sales calls) | Yes. The Pixel can’t see those |
| Shopify or WooCommerce with the official app | Check what the app already sends before adding anything |
How do the two copies avoid double counting?
Deduplication means Meta merging the browser copy and the server copy of one sale into a single event. Meta’s rule: the browser eventID must match the server event_id (a shared order number both copies carry), and the event names must match. If they do, Meta generally keeps the event it received first. Events are deduplicated only if they arrive within 48 hours of the first one with that ID (Meta: deduplication). For a purchase, the order ID is the usual choice.
Meta describes a second method too, matching on browser and customer identifiers, but that route generally needs the browser event to arrive first, and the event ID route is the one Meta recommends. What to ask whoever builds it: “Is the same order ID sent as the event ID from both the browser and the server?” To prove it works, follow How to check Meta Pixel and CAPI deduplication is working.
How do you add it?
- One click in Events Manager. If you have a Pixel and want website events only, Meta describes setting up the Conversions API with Meta from Events Manager. Nothing to host or code.
- Conversions API Gateway. Self-serve; runs in a cloud account your business owns (AWS or Google Cloud), so cloud costs apply. It generates an event ID for deduplication (Meta: Gateway).
- Partner integration, server-side GTM or a direct build. For brands that need the same server to feed other platforms. The wider picture is in Server-side vs client-side GTM and, for the fault itself, F-401 .
The trade-offs are laid out in Meta Conversions API setup options compared. Pick one sender per Pixel. Two server senders for the same events is how you get F-102 , the double count.
What does it not fix?
It doesn’t change who clicked your ad, and it doesn’t make Meta’s attribution agree with GA4. It improves what Meta can match to an account: Meta says more customer information parameters may increase Event Match Quality, which is scored out of 10 per event (Meta: best practices). Weak matching is its own problem, covered in Meta Event Match Quality is low.
When you need a person rather than a tool
If your numbers show a gap and you don’t know whether it is a missing copy, a double count or a consent setting, that is Meta Conversions API and Pixel work: one Purchase per order, the right value, and a server copy that deduplicates. Send me last week’s shop order count and Events Manager Purchase count for the same days and I’ll tell you which of the three it looks like.
No tool named here pays me. No partnership, no affiliate links, no commission.
Common questions
Do I need the Conversions API if my Meta Pixel works?
Usually yes, as an addition to the Pixel, not a replacement. Meta recommends sending the same events through both the Pixel and the Conversions API. Skip it for now only if the Pixel already sees nearly every order and your Meta spend is small. If you already have a Pixel, Meta’s one-click option in Events Manager needs nothing hosted; a custom build is for brands where the missing sales are large enough to pay for it.
Can I use the Conversions API without the Pixel?
The API can send events on its own, but for website events Meta’s best-practices page recommends using it in addition to the Pixel. With only one source there is nothing to deduplicate, and the browser event the Pixel would have sent is simply absent.
Will the Conversions API double count my sales?
Mainly if the copies don’t match, or if two tools send the same server event. Meta pairs a browser event with a server event when the event name and event ID are the same, and generally keeps the one it received first. That only works within 48 hours, and Meta says it does not deduplicate events from a single source.
Is the Conversions API Gateway the same thing?
No. The Gateway is one way to send server events. It runs in a cloud account your business owns, such as AWS or Google Cloud. The Conversions API is the connection itself, and, if you already have a Pixel, it can be turned on from Events Manager with nothing to host.
Sources
Read on 12 November 2026:
- Meta for Developers: Conversions API (connection layer; website, app and offline events; processed like Pixel events; one-click setup with Meta), best practices (use alongside the Pixel; redundant setup; events the Pixel may lose to connectivity or page errors; Event Match Quality out of 10), deduplication (event ID and event name; first received kept; 48 hours; fbp or external_id method) and Conversions API Gateway (self-serve; business-owned cloud account on AWS or GCP; event ID generation)