Meta Pixel plus Conversions API: what a small business needs
Short answer: Keep the Meta Pixel on your site and add the Conversions API so key events (leads, bookings, purchases) also travel from your server or platform straight to Meta. Meta calls running both a "redundant setup" and recommends it. The one thing you must get right is deduplication: send the same event name and a shared event_id from both sides so Meta counts each conversion once. For most small businesses, the fastest route is the built-in option in your platform or in Events Manager, not custom code.
If your ads dashboard shows fewer leads than your inbox, you're not imagining it. Browser-based tracking depends on a script running on the visitor's device, and that script doesn't always get to fire. This explainer covers what the Conversions API does, how the two sources fit together, and which setup route makes sense for your kind of site.
What the Pixel does, and where it falls short
The Meta Pixel is JavaScript on your pages. When someone views a page, submits a form or buys, it sends an event from their browser to Meta.
That works until it doesn't. Meta's own implementation guide notes that browser restrictions on data transmission may limit the efficacy of cookies and Pixel tracking. Add ad blockers, people closing the tab before a thank-you page loads, and scripts that fail on slow phones, and some conversions never reach Meta. Your ads then optimize on an incomplete picture.
What the Conversions API adds
The Conversions API (CAPI) sends events from your server, website platform or CRM directly to Meta, instead of relying only on the visitor's browser. Meta describes server events as linked to a dataset ID and processed like events from the Pixel, so they can be used for measurement, reporting and optimization in a similar way.
It also lets you send events the browser never sees, such as a phone lead marked "qualified" in your CRM a day later.
The three ways to combine them
Meta's end-to-end guide lists three approaches, as of November 2026:
| Setup | What it means | Meta's view |
|---|---|---|
| Redundant | Send all events through both Pixel and CAPI | Recommended |
| Split | Some events via Pixel (e.g. PageView), others via CAPI (e.g. Lead, Purchase) | Not as optimal; may need more work as browsers change |
| Server-only | Everything through CAPI | Possible, but you lose the browser side entirely |
For a small business, redundant is usually the right call, which brings us to the part people get wrong.
Deduplication: the step that makes or breaks it
If both the Pixel and CAPI report the same purchase and Meta can't tell they're the same, you'd count it twice. Meta's recommended fix uses two matching values:
- The event name must match: the Pixel's event (for example
Lead) and the server'sevent_name. - The event ID must match: the Pixel's
eventIDand the server'sevent_id.
On the browser side, the ID goes in the fourth argument of the fbq call, for example fbq('track', 'Lead', {}, {eventID: 'abc123'}). Your server then sends the same abc123 with its Lead event.
Two timing rules from Meta's deduplication page are worth knowing:
- Matching events are only deduplicated if they arrive within 48 hours of the first event with that ID.
- When browser and server versions don't differ meaningfully, Meta generally keeps whichever arrived first.
Meta also describes a fallback method using fbp (the browser cookie value) or external_id, but it mainly works when the browser event arrives before the server event. The event_id method is the one to aim for.
In practice, the ID should be something both sides know, like your order number, booking reference or a value your form generates and passes to the server.
Event Match Quality
Server events need customer information parameters (such as a hashed email or phone) so Meta can match them to people. Events Manager shows Event Match Quality, scored from 1 to 10, on the Overview page for a Pixel that has CAPI connected. Meta's verification guide says that where possible it typically recommends aiming for 6.0 or higher, and that a higher score can help decrease cost per action. Click the score for Meta's specific suggestions.
Only send customer data your privacy notice covers and your visitors have agreed to where consent is required. Check the rules where you operate.
Choosing a setup route
| Your site | Likely route | Effort |
|---|---|---|
| Shopify | The Facebook and Instagram by Meta sales channel, which covers the Pixel, a customer data-sharing level and the Conversions API | Low |
| WordPress/WooCommerce or another platform with a Meta integration | The platform's official Meta integration or a partner integration listed by Meta | Low to medium |
| Any site with a Pixel already installed | Events Manager's own setup: Meta's developer overview notes CAPI for website events can be set up "in one click" from Events Manager, with no code or setup fees | Low |
| Custom site or app, or you need CRM events | Direct integration: your server POSTs events to the API with an access token | Medium to high |
| Several sites or heavy traffic | A server-side gateway or tagging setup run by you or a partner | Medium |
For the direct route, Meta's getting-started page lists what you need: a Pixel ID (use the same one for browser and server events), a Meta Business Suite account, and an access token. The recommended way to get the token is in Events Manager under the Pixel's Settings tab ("Generate access token"), a link only users with developer privileges can see.
Testing before you trust the numbers
- Send a test conversion yourself (submit the form, make a small order or booking).
- In Events Manager, use the test events view to confirm both a browser and a server event arrived.
- Check that the event shows as deduplicated rather than counted twice. Meta's "Verifying your setup" page walks through this.
- Watch Event Match Quality for a few days and add any customer fields it suggests that you legitimately collect.
- Compare Meta's lead count with your own records for a week. They won't match exactly, but they should be close and move together.
FAQ
Do I still need the Pixel if I set up CAPI?
Meta recommends keeping both. The Pixel catches browser-side behavior like page views and add-to-carts; CAPI makes sure your key conversions arrive.
Will CAPI make my numbers jump?
Often the reported count rises because fewer events go missing. If it roughly doubles overnight, deduplication probably isn't working.
What should I use as the event ID?
Something unique per conversion that both browser and server can access, such as an order ID, booking reference or a random ID generated when the form loads and submitted with it.
Is this the same as Meta lead ads?
No. Lead ads collect forms inside Facebook or Instagram. CAPI is about events that happen on your own website or systems.
To get your form, booking or checkout events reaching Meta once each and on time, tell us what your site runs on.
Sources
- https://developers.facebook.com/docs/marketing-api/conversions-api
- https://developers.facebook.com/documentation/ads-commerce/conversions-api/get-started
- https://developers.facebook.com/documentation/ads-commerce/conversions-api/guides/end-to-end-implementation
- https://developers.facebook.com/documentation/ads-commerce/conversions-api/deduplicate-pixel-and-server-events
- https://developers.facebook.com/documentation/ads-commerce/conversions-api/verifying-setup
- https://help.shopify.com/en/manual/online-sales-channels/facebook-instagram-by-meta