On this page
How the Conversions API works
The Pixel runs in the visitor’s browser, so ad blockers, Safari’s tracking limits and lost cookies all cut into what it reports. The Conversions API sends the same purchase, lead or sign-up from your own server to Meta, where none of those apply. Meta then matches the event to an ad click using the customer details you send.
Meta recommends running both, not choosing one. The browser event gives Meta fast signal and cookie context. The server event fills the gaps. A single conversion usually arrives twice, and Meta keeps one.
Think of it as a second route for the same fact. A customer buys, your order system knows, and your server tells Meta directly. Nothing about the customer’s browser has to cooperate, which is why server events also cover offline outcomes such as a closed deal or a booked appointment.
Meta’s Pixel and Conversions API together are sometimes called a redundant setup. The point of the word is that either source can carry an event when the other drops it, so a blocked browser does not erase a sale.
Pick the method that fits your stack
There are three routes. A partner integration (Shopify, WordPress plugins and most checkout platforms) is a toggle plus a login, and it is the right answer for most stores. The Conversions API Gateway is a hosted setup that Meta provides, which runs on a cloud server and may carry hosting costs. A direct integration means your developer posts events to the Graph API with an access token.
Start with the partner option if your platform has one. Go direct only when you need events the partner does not send, such as a CRM stage change or an offline sale. The related setup for ad platforms that need a server layer is covered in server-side tracking.
Whichever route you choose, you end up with the same thing in Events Manager: a dataset (the new name for the Pixel container) receiving events from more than one source. You can see each source labeled Browser or Server, which makes it easy to tell which route is carrying the volume.
Is your tracking counting every conversion?
Runs tracking health checks on your pixels and tags. Sends a weekly performance review.
Send the events and the right fields
In Events Manager, open your Pixel’s dataset, go to Settings, and generate an access token under Conversions API. Each event needs an event name (Purchase, Lead, CompleteRegistration), an event time, the action source (website), the event source URL, and customer information such as hashed email and phone, plus the click ID and browser ID when you have them.
More matching fields means a higher event match quality, which is how well Meta can tie the event to a person. Send value and currency on purchases. Send events as they happen, not in a nightly batch, because late events help optimization less.
Hash personal data (email, phone, name) with SHA-256 after trimming and lowercasing it, as Meta’s documentation specifies. Never send raw email addresses. Pass the client IP address and user agent unhashed when you have them, since Meta uses both for matching.
Deduplicate against the Pixel
Without deduplication you report double the sales. Generate one event ID per action, such as the order number, and send it with both the Pixel event and the server event. The event name must match exactly, and the server event has to arrive within 48 hours of the browser one.
If your Pixel already fires, check it first with the steps in Meta Pixel not tracking. A broken browser event cannot be deduplicated against.
If your server and browser events use different IDs for the same order, Meta sees two purchases. The fastest audit is to place one order and count how many Purchase events the dataset shows for it.
Verify before you trust it
Use the Test Events tab with the test code Meta gives you, then place a real test order. You should see the event under both Browser and Server, marked as deduplicated. In the Overview tab, look at the event match quality score for each key event and the diagnostics list for warnings.
Optimization needs volume too: Meta’s rule of thumb is about 50 optimization events per ad set per week to leave the learning phase, which you can read about in the learning phase guide. Sprites can run a tracking health check on a schedule, reading events by source, deduplication and event match quality, and propose fixes as approval cards you edit before anything changes.
Give it a few days of real traffic before judging. Compare Meta’s reported purchases with your order system for the same dates: a gap of some percent is normal because of attribution rules, but a 2x difference points to a duplication problem, and a big shortfall points to missing server events.
Re-check after any change to checkout, your tag manager, or your platform plugin. Tracking breaks quietly when a theme update removes a script or a new payment step skips the confirmation page.
Questions
How does the Facebook Conversions API work?
Your server sends each conversion to Meta as an HTTPS request tied to your Pixel’s dataset, with the event name, time and hashed customer details. Meta matches it to an ad interaction and uses it for reporting and optimization, even if the browser never reported it.
Is the Meta Conversions API free?
Yes, Meta does not charge for the API. Costs come from whoever builds or hosts the integration: a developer, a tag server, or the cloud server behind the Conversions API Gateway.
Is there an API for Facebook ads?
Yes. The Conversions API sends events to Meta. The separate Marketing API creates and manages campaigns, ad sets and ads. They use different endpoints and different permissions.
How many conversions does Meta need?
As a rule of thumb, about 50 optimization events per ad set in a week to exit the learning phase. Fewer events still run, but delivery stays less stable. Optimize for an event you get often enough.
Do I still need the Pixel if I use the Conversions API?
Yes. Meta recommends both so each covers what the other misses. Send a shared event ID so the duplicates collapse into one event.