What Is Meta Conversions API (CAPI)? Setup, EMQ and Deduplication
What is Meta Conversions API, how does it differ from the Pixel and how do you set it up? Required parameters, hashing, Event Match Quality and testing.
What is Meta Conversions API? In short, Meta Conversions API (often called CAPI) is a connection that sends conversion events to Meta directly from an advertiser’s server, CRM or app instead of the Pixel in the browser. Because the events do not depend on the browser, part of the signal lost to cookie restrictions and ad blockers comes back. Meta recommends using it alongside the Pixel, not in place of it.
In this post I explain how Conversions API works, how it differs from the Pixel, the setup options, the required parameters and the hashing rules. After that I cover Event Match Quality, deduplication and the checks I run before going live.
How does Meta Conversions API work?
Short answer
How does Meta Conversions API work?
When a user completes an action on the site, the site’s server sends that event in an HTTP request to the pixel’s events endpoint in Meta’s Graph API. The request contains the event name, the event time, the event source and hashed customer information. Meta uses that information to match the event to a Meta account and an ad click, then uses it for optimization and reporting.
Meta’s developer documentation describes Conversions API as a tool that connects an advertiser’s marketing data with the Meta systems that optimize ad targeting and measurement.[1] In practice, that connection means your server sends events to Meta as JSON.
The request is a POST to the /{PIXEL_ID}/events endpoint built from your pixel ID, and it is authorized with an access token generated in Events Manager. According to Meta’s usage guide, a single request can carry up to 1,000 events.[6]
On the server side, an event reaches Meta in one of two ways. In the first, the browser event goes to the site’s own measurement server, for example a server-side GTM container, and is forwarded to Meta from there. In the second, the event never passes through the browser. When a payment is confirmed or a lead moves to the “won” stage in the CRM, the back end sends the request to Meta directly.
What is the difference between Meta Pixel and Conversions API?
Meta Pixel is a JavaScript code that runs in the user’s browser and sends events to Meta from there, while Conversions API sends events from the advertiser’s server. The Pixel easily captures browser behavior such as page views and scrolling. Conversions API can deliver outcomes the browser never sees, such as a payment confirmation, a cancellation or a sale closed in the CRM.
Meta Pixel
- Runs in the user's browser
- Installed with a single code snippet
- Directly affected by ad blockers and cookie restrictions
- Creates the _fbp and _fbc cookies
- Only sees events that happen on the site
Conversions API
- Runs on the advertiser's server or in a CRM integration
- Requires an access token and a server-side setup
- Not directly affected by browser restrictions
- Can use cookie values if they are passed to the server
- Can also send offline and CRM events
Meta calls this combination a “redundant setup” and recommends that advertisers implement Conversions API alongside their Pixel.[2] In a redundant setup the server event still reaches Meta even if the browser event is lost. When both arrive, Meta counts them as one event through its deduplication rules.
I covered the browser restrictions behind this difference and the general logic of server-side measurement in the server-side tracking post. Here I focus on the setup and parameters that are specific to Meta.
How do you set up Conversions API?
There are four common ways to set up Conversions API: the no-code setup in Events Manager, a ready-made Meta integration in your e-commerce or CRM platform, a tagging server such as server-side GTM, and a direct API integration. Meta states that advertisers who already have the Pixel can set up Conversions API from Events Manager without writing code.[1]
| Method | Who it suits | Limitation |
|---|---|---|
| No-code setup in Events Manager | Sites with a Pixel that want to start quickly | Limited for custom events and CRM data |
| Platform integration (Shopify, WooCommerce, CRM) | E-commerce and sales teams on a ready-made platform | The fields sent depend on the integration |
| Server-side GTM | Teams sending server-side data to several platforms | Requires hosting and maintenance |
| Direct API | Businesses with custom software and their own back end | Development and monitoring are your responsibility |
Whichever route you choose, the setup order stays roughly the same:
- Map your events
Write down which action goes out under which event name: a standard event such as Lead, Schedule or Purchase, or a custom event? Settle the value, currency and order number fields here.
- Create the access token
Generate an access token for Conversions API in the pixel settings in Events Manager. Keep the token on the server only; never put it in browser code or in a repository.
- Generate a shared event_id
If the Pixel and the server send the same event, give both sides the same unique ID, such as an order or application number.
- Prepare customer information
Normalize the fields you are allowed to send and hash contact details with SHA-256. Add IP, user agent, fbc and fbp without hashing.
- Validate with Test Events
Add the test code from the Test Events screen in Events Manager to the request, confirm that events arrive with the right names and are deduplicated, then remove the code.
Example request
The body below shows a purchase on a website being sent from the server. The values are examples; the em and ph fields are sent hashed.
{
"data": [
{
"event_name": "Purchase",
"event_time": 1763550000,
"event_id": "order-10482",
"action_source": "website",
"event_source_url": "https://www.example.com/checkout/complete/",
"user_data": {
"em": ["<sha256(lowercased email)>"],
"ph": ["<sha256(phone with country code)>"],
"client_ip_address": "203.0.113.10",
"client_user_agent": "Mozilla/5.0 ...",
"fbc": "fb.1.1763549000000.AbCdEf...",
"fbp": "fb.1.1763540000000.1234567890"
},
"custom_data": { "currency": "TRY", "value": 1250 }
}
]
}
Which parameters does Conversions API require?
According to Meta’s server event parameters reference, every event requires event_name, event_time, user_data and action_source.[4] Website events should also include event_source_url. If these four fields are missing, the event is not processed; missing or inconsistent user_data lowers the chance that the event is matched to a person.
- event_name: The name of the event. Using standard event names (Purchase, Lead, Schedule) makes reporting and optimization easier.
- event_time: The moment the event happened, as a Unix timestamp in seconds, in GMT. According to Meta, this value can be at most 7 days before you send it. If any event is older, the whole request returns an error and none of its events are processed.[4]
- action_source: Where the conversion happened. It takes values such as
websitefor a site,physical_storefor a sale completed in a store or clinic, andchatfor messaging. - user_data: Customer information used to match the event to a person.
Offline sales follow a different rule. Meta recommends uploading in-store and offline transactions sent with the physical_store source within 62 days of the conversion.[6] In health tourism the procedure day, and in e-commerce a cash-on-delivery handover, often fall into this scenario.
Hashing and normalization
According to Meta’s customer information parameters reference, email, phone, first name, last name, date of birth, gender, city, state, zip code and country must be hashed with SHA-256.[3] client_ip_address, client_user_agent, fbc and fbp are sent unhashed. Hashing is recommended for external_id but not required.
Values are normalized before hashing. For email, leading and trailing spaces are removed and all characters are lowercased. For phone numbers, symbols, letters and leading zeros are removed, and the country code is always included.[3] For a Turkish number, that means the format 90532… instead of 0532 ….
On the cookie consent side, if a user rejects advertising cookies, the server-side tags must respect that choice as well. I explained how the consent signal travels from the browser to the server in the Consent Mode v2 post.
What is Event Match Quality and how do you improve it?
Event Match Quality is the score that shows how well Meta can match an event received from a server to a person with a Meta account. It appears per event in Events Manager. What drives the score is the coverage and accuracy of the customer information fields sent with the event.
These fields strengthen matching the most:
- fbc: When a user clicks a Meta ad, the
fbclidparameter is added to the landing page URL. The Pixel writes this value to the_fbccookie. According to Meta’s documentation, thefbcvalue has the formatfb.1.<creation time>.<fbclid>, andfbclidis case sensitive.[5] - fbp: If none exists, the Pixel saves a unique browser identifier to the
_fbpcookie.[5] Passing this value to the server ties the server event to the Pixel event from the same browser. - Email and phone: Contact details collected in a form or checkout step, correctly normalized and hashed.
- IP address and user agent: The IP and user agent of the request for website events.
- external_id: The customer number in the site or the CRM. It links events that belong to the same person.
The mistake I see most often is a server event sent with empty fbc and fbp fields. If the user came from an ad but the click ID was never passed to the server, Meta cannot tie the event to that click. The fix is to read these cookies on the landing page and send them to the server together with the form or order record.
What should you do if Pixel and Conversions API events are counted twice?
If the Pixel and Conversions API send the same event, both events must carry the same event_name and the same event_id. According to Meta’s deduplication guide, the Pixel’s eventID value must match the server’s event_id exactly.[2] Without a match, the same purchase is counted twice and ROAS looks higher than it really is.
Deduplication also has a time limit. Meta deduplicates copies that arrive within 48 hours of receiving the first event with a given event_id.[2] So in a setup that sends the server event days later, double counting can happen even when the IDs match.
As an alternative, Meta also supports deduplication by event name plus fbp or external_id. However, that method only works when the browser event arrives first and the server event second.[2] I prefer to send an event_id with every event; it simplifies both the setup and debugging.
How is Conversions API used in health tourism and e-commerce?
Conversions API delivers the most value in businesses where the real outcome happens in the sales process, not on the website. In health tourism the journey runs from lead to consultation to procedure. In e-commerce the purchase value can change later because of returns, cancellations or cash on delivery.
Health tourism: A form submission or WhatsApp click on the site is only the beginning. The event that really matters for optimization is the patient coordinator qualifying the lead, the deposit being paid or the procedure taking place. Sending these stages from the CRM through Conversions API lets Meta learn which audience brings quality leads. For records from Meta’s own lead forms, the lead_id field is sent unhashed.[3] I covered the Google side of this flow in the health tourism offline conversions post, and the WhatsApp channel in the WhatsApp conversion tracking post. I summarize the sector-specific approach in the health tourism digital marketing guide.
E-commerce: Sending the purchase event from the server after the payment provider’s confirmation brings orders whose browser never reached the thank-you page into measurement. Basket contents, currency and the confirmed value come from the order system, so they are more reliable. If you are building a profit-based bidding strategy, you can also enrich this value with POAS logic.
How do you check that the setup works correctly?
To validate a Conversions API setup, check separately that events reach Meta, that the required fields are filled, that deduplication works and that match quality is sufficient. For testing, Meta asks you to send the code generated on the Test Events screen in Events Manager with the test_event_code parameter.[6] This code is for testing only and must be removed from production requests.
The last item is the most frequently skipped check. Even if everything looks green in Events Manager, regularly comparing Meta’s conversion count with the CRM or order system helps you spot both missing and double-counted conversions early.
Where should you start?
Meta Conversions API is a connection that sends conversion events from the server to Meta and recovers part of the signal the Pixel misses. To work correctly, it needs the required parameters filled, customer information normalized and hashed, and the same event_id used as the Pixel. Its real value shows up when it feeds outcomes from the CRM, such as sales and appointments, back to Meta.
My advice is to clarify your event map and consent setup first, then start with the simplest setup route and validate it with Test Events. After that, move on to improving match quality with fbc, fbp and contact details, and to adding CRM events. I describe how I build measurement and ad management together on the performance marketing page, and the integration work on the software side on the software development page.
Key terms
- Meta Conversions API
- Meta Conversions API is an interface that creates a direct connection between an advertiser's server, CRM or app and Meta's ad systems, delivering conversion events from the server. It is often shortened to CAPI and Meta recommends using it together with the Meta Pixel.
- Event Match Quality
- Event Match Quality is the score that shows how well Meta can match an event received from a server to a person with a Meta account. The score depends on the coverage and accuracy of the customer information sent with the event, such as email, phone, IP, user agent and cookie identifiers.
- fbclid
- fbclid is the click ID parameter added to the landing page URL when a user clicks a Meta ad or a link on Facebook or Instagram. The Meta Pixel stores this value in the _fbc cookie; when it is sent in the fbc field of a Conversions API request, the conversion can be tied to the ad click.
- action_source
- action_source is the required Conversions API parameter that states where a conversion happened. It takes values such as website for a site, physical_store for an in-store sale, chat for a messaging app or system_generated for events created by a system.
Frequently asked questions
What is Meta Conversions API?
Meta Conversions API (CAPI) is a connection that sends conversion events to Meta directly from an advertiser's server, CRM or app. Because events are delivered without depending on the browser, part of the signal the Pixel misses flows back into ad optimization.
Does Conversions API replace the Meta Pixel?
No. Meta recommends using the two together. The Pixel captures browser behavior and cookie identifiers, while Conversions API delivers the confirmed outcome from the server. If both send the same event, the event name and event_id must match, or the conversion is counted twice.
Do you need a developer to set up Conversions API?
Not always. A site that already has the Pixel can start with the no-code setup in Events Manager or with its e-commerce platform's Meta integration. Sending sales from a CRM, designing custom events or using server-side GTM does require technical work.
Which customer data is sent with Conversions API?
Contact details such as email, phone, first name, last name, city, zip code and country are sent hashed with SHA-256. IP address, user agent and the fbc and fbp cookie values are sent unhashed. Which fields you send should depend on the consent you collected and on privacy law such as KVKK and GDPR.
How far back can you send Conversions API events?
For website events, event_time can be at most 7 days before the moment you send it. A request that contains an older event is rejected as a whole. For in-store and offline sales, Meta recommends uploading transactions within 62 days of the conversion.
Sources
- Meta for Developers: Conversions API
- Meta for Developers: Handling Duplicate Pixel and Conversions API Events
- Meta for Developers: Customer Information Parameters
- Meta for Developers: Server Event Parameters
- Meta for Developers: ClickID and the fbp and fbc Parameters
- Meta for Developers: Using the Conversions API
The full topic: Meta Ads guide ↗ · Tracking guide ↗