Key takeaways
- The Conversions API sends events from your server to Meta. It works alongside the Pixel, not instead of it.
- When the Pixel and the server send the same event, give both copies the same
event_nameandevent_idso Meta keeps only one. - Event Match Quality measures how well your customer information matches Meta accounts. It does not measure sales or deduplication.
- Server events still need a lawful basis and must respect consent. Ask legal counsel about Law 25 or GDPR.
- The Conversions API improves signal quality. It does not guarantee more conversions.

What the Conversions API is
The Meta Conversions API (CAPI), still often called the Facebook Conversions API, lets your server send website, app and offline events straight to Meta. It complements the Meta Pixel, which sends the same kind of events from the visitor’s browser.
The Pixel depends on the browser. Ad blockers, browser privacy features, slow pages and closed tabs can stop some of its requests. A server event does not depend on the browser in the same way, so Meta can receive events the Pixel missed. It also gives you more control over what you send.
Meta recommends running both together. The Pixel captures browser context; the server adds reliability and data you hold only on your side, such as a confirmed order value. Both feed the same dataset in Events Manager. The full reference is in Meta’s Conversions API documentation.
If you run a Shopify store and want the wider picture of server-side tracking (GA4, Google Ads, consent routing), read our server-side tracking guide for Shopify. This article stays on Meta.
Setup options compared
There are four common ways to send Conversions API events: a partner integration, the Conversions API Gateway, server-side Google Tag Manager, or a direct integration with the API. The right one depends on your platform, your team and how much control you need.
| Option | How it works | Effort | Best for | Watch out for |
|---|---|---|---|---|
| Partner integration | A platform app sends server events for you, such as Shopify’s Facebook & Instagram app or the Meta integrations for WooCommerce and other platforms | Low, no code | Stores on a supported platform that want a quick, standard setup | Limited control over events and parameters; check the data-sharing setting that turns on server events |
| Conversions API Gateway | A Meta-provided service, set up from Events Manager, that runs on cloud infrastructure you control or through a hosting partner and relays your Pixel events from the server | Low to medium | Sites without a partner integration that want server events with little code | Built around Pixel events; you pay for hosting and keep it updated |
| Server-side GTM | A Google Tag Manager server container receives events and a Meta tag sends them to the API | Medium to high | Teams already using GTM that want one pipeline for Meta, GA4 and Google Ads | Someone must build, test and maintain both containers and the hosting |
| Direct API | Your own backend calls the Conversions API endpoint with an access token | High | Custom platforms, CRMs, offline or lead events, large in-house tech teams | Developer time for hashing, retries, deduplication and API version updates |
For Shopify, start with the Facebook & Instagram app before you build anything custom. Move to server-side GTM or a direct integration when you need events or parameters the app does not send, or one pipeline for several ad platforms.
Event deduplication
Deduplication is how Meta keeps one copy of an event that both the Pixel and the server sent. For it to work, both copies need the same event_name and the same event ID: eventID on the Pixel side and event_id on the server side.
Generate the ID once, when the action happens, and pass it to both paths. An order number works for a purchase. A random ID created on page load works for events like ViewContent. Do not let the server create a new ID on each retry, or each retry looks like a new event.
Event names must match exactly. Purchase and purchase are different events. Meta’s documentation also sets a time window for matching browser and server copies, so send server events promptly rather than in late batches. See Meta’s deduplication guide for the current rules.
Customer information and Event Match Quality
Customer information parameters help Meta match a server event to the person who saw your ad. Event Match Quality (EMQ) is the score, from 0 to 10, that Events Manager shows for how well those parameters can match events to Meta accounts.
Common parameters include email (em), phone (ph), first and last name, city, province or state, postal code, country and external_id. You must normalize these values (trim spaces, use lowercase, keep digits only with the country code for phone numbers) and hash them with SHA-256 before sending.
Some parameters are sent without hashing: the client IP address, the user agent, and the fbp and fbc values from Meta’s browser cookies. For website events, Meta requires client_user_agent and event_source_url, plus action_source set to website. The full list is in the customer information parameters reference.
Know what EMQ does not measure. It does not check that deduplication works, that purchase values are right, that every order is sent, or that your ads cause sales. A high score with duplicated purchases is still broken tracking. Hashing is also not anonymization: it is a transport format, and you still need a lawful basis to share the data.
Standard events and parameters
Use Meta’s standard event names whenever one fits, and send the parameters that let Meta optimize and report on value. Custom events are fine for extra actions, but standard events are easier to optimize for and to read in reports.
Ecommerce. The usual funnel is ViewContent, AddToCart, InitiateCheckout, AddPaymentInfo and Purchase. Send value and currency on every Purchase, plus content_ids or contents and content_type so events match your catalog for dynamic ads. Use one currency rule and decide whether value includes tax and shipping.
Lead generation. Use Lead for form submissions, CompleteRegistration for sign-ups, Schedule for booked appointments and Contact for calls or chats. If you qualify leads in a CRM, the server path lets you send a later event when a lead becomes a customer, using action_source values like system_generated where they fit.
The server event itself needs event_name, event_time (a Unix timestamp), action_source and user_data. Meta rejects events with an event_time that is too old, so do not queue website events for days. Check the server event parameters reference for limits.
Consent, Law 25 and GDPR
Sending events from a server does not remove consent duties. If a visitor refuses advertising cookies or tracking, the server path must respect that choice the same way the Pixel does.
In practice, pass the consent state from your consent banner to every path. On the browser side, the Pixel supports fbq('consent', 'revoke') and fbq('consent', 'grant'). On the server side, your code or container must check consent before it sends or enriches an event.
In Québec, Law 25 sets rules on consent, transparency, and transfers of personal information outside the province. In Europe, GDPR and the ePrivacy rules apply. Other regions have their own laws. This article is not legal advice. Have legal counsel review what you collect, why, who receives it and how long you keep it before you send customer data to Meta.
Testing in Events Manager
Test every event in Events Manager before you rely on it. The Test Events tab shows browser and server events in near real time, and the Diagnostics tab lists errors and warnings once live traffic flows.
For server events, copy the test code from the Test Events tab and send it as test_event_code in your payload. Then trigger each action on your site: view a product, add to cart, start checkout, place a test order or submit a form. Check that each event arrives from both the browser and the server, with the same event ID, the right value and currency, and the customer information you expect.
Remove the test code before going live. After launch, check Diagnostics regularly for duplicate events, missing parameters, invalid hashes and dropping event volume. Problems often appear after a theme update, a new checkout app or a consent banner change.
How to read the results
The Conversions API improves the signal Meta receives. It does not guarantee more conversions, lower costs or better return on ad spend.
After launch, Ads Manager may report more conversions. Part of that can be events the Pixel used to miss, not new sales. Compare Meta’s numbers with your own source of truth (Shopify orders, CRM leads) over the same period. Expect gaps: attribution windows, modeled conversions, time zones and refunds all differ between systems.
Better signals can help delivery over time, because the algorithm learns from more complete data. But the ad itself still drives most results. If tracking is clean and results are flat, look at your offer and your creative. Our article on creative diversity on Meta covers how to test that.
Step-by-step checklist
Follow these steps in order. Most tracking problems come from skipping the first two.
- List every Pixel, app and tag that sends events to Meta today, and remove duplicates.
- Write down which events you need, their exact names, parameters and where the event ID comes from.
- Pick a setup option: partner integration, Conversions API Gateway, server-side GTM or direct API.
- Connect consent from your banner to both the Pixel and the server path.
- Send the same
event_nameand event ID from both paths. - Add normalized, hashed customer information, plus IP address, user agent,
fbpandfbcwhere permitted. - Test each event with
test_event_codein the Test Events tab. - Go live, then check Diagnostics and Event Match Quality during the first week.
- Compare Meta conversions with your orders or leads every month.
Common mistakes
Most Conversions API problems come from duplicated or mismatched events, not from the API itself. Watch for these:
- Two apps or tags sending the same Purchase, so Meta counts it twice.
- Different event IDs, or no event ID, on the browser and server copies.
- Sending unhashed email or phone numbers, or hashing values before normalizing them.
- Missing
valueorcurrencyon purchases, or mixing currencies. - Sending server events when the visitor refused consent.
- Forgetting to remove
test_event_codeafter testing. - Judging success by Event Match Quality or by Ads Manager numbers alone.
If you want a second pair of eyes on your setup, our Data team audits and builds Meta tracking, and our Ads team runs the campaigns that use it. You can also book a free 30-minute call to review your Events Manager together.
Running Meta ads on top of this setup? See our Meta and Facebook ads agency.
Frequently asked questions
Is the Facebook Conversions API the same as the Meta Conversions API?
Yes. It is the same product. Facebook renamed its parent company Meta in 2021, and the API kept working under the new name. Both terms point to the server-side events you send to a Meta dataset.
Do I still need the Meta Pixel if I use the Conversions API?
In most cases, yes. Meta recommends a redundant setup: the Pixel sends events from the browser, the Conversions API sends the same events from your server, and deduplication keeps one copy of each.
Will the Conversions API increase my conversions?
Not by itself. It can make Meta receive and match more of the conversions that already happen. More reported conversions are a measurement change, not proof of more sales. Check your own orders or leads to judge the real effect.
Do I need a developer to set up the Conversions API?
Not always. A partner integration, such as Shopify’s Facebook & Instagram app, needs no code. The Conversions API Gateway needs some cloud setup. Server-side Google Tag Manager and a direct API integration need technical skills to build and maintain.
What is a good Event Match Quality score?
Meta rates Event Match Quality from 0 to 10 for each event. Higher is better, but the score only describes how well your customer information can match people to Meta accounts. It does not check deduplication, purchase values or whether your ads drive sales.

