Meta Conversions API (CAPI for short) is a connection that lets a website, server or CRM send events directly to Meta's servers. The Meta Pixel sends data from the visitor's browser; the Conversions API sends the same data from your server. When the two work together, the server fills in the signal the browser loses.
Why you need it
Data sent from the browser is blocked more and more: ad blockers, browser limits on third-party cookies and tracking, in-app browsers and consent choices. Every lost event means Meta's ad algorithm learns from less data. The Conversions API reduces that loss by sending the data from the server, and it is the only way to bring events that happen off the website (a sale that comes in by phone, a qualified lead in your CRM) into Meta.
Pixel vs. Conversions API
| Meta Pixel | Conversions API | |
|---|---|---|
| Sends from | The visitor's browser | Your server or your CRM |
| Blocking risk | Affected by ad blockers and browser restrictions | Does not depend on the browser |
| Off-site events | Cannot send them | Can send them (CRM, phone, store) |
| Data control | Limited | You decide which fields are sent |
| Setup | Easy | More technical work |
For the best results, Meta recommends a "redundant" setup that uses both.
Deduplication: not counting the same event twice
When the Pixel and the Conversions API both send the same purchase, Meta has to count it as one event. To make that happen, both channels send the same event_name (for example, Lead) and the same unique event_id. Meta deduplicates a second event that arrives with the same ID within a set time window. If the event_id is inconsistent, events double in your reports and optimization breaks.
Match quality
For a server event to be useful, Meta has to be able to match it to a user. That is what the customer information parameters are for:
- Hashed email and phone (
em,ph): hashed with SHA-256. - Click and browser IDs (
fbc,fbp): these come from the Meta ad click and the Pixel cookie. - IP address and browser details (
client_ip_address,client_user_agent).
The Event Match Quality score in Events Manager shows how good this matching is. If the score is low, first check which parameters are missing.
Ways to set it up
- Platform integration. Meta integrations on Shopify, WooCommerce and similar platforms switch on the Conversions API with a few settings. It is the fastest route, but customization is limited.
- Conversions API Gateway. Meta's own no-code solution that runs in your cloud account; it copies Pixel events from the server.
- Server-side Google Tag Manager. If you already use server-side tracking, you can send to Meta from the same infrastructure. It gives you the most control over the data.
- Direct API. A direct integration with the Meta Marketing API to send events from a custom system or from your CRM.
Lead ads and the CRM
In lead-driven businesses such as B2B and healthcare, the most valuable use is sending the outcome in your CRM back to Meta. When the sales team marks a lead as qualified or a deal closes, that event goes to Meta through the Conversions API. From then on, the campaign looks not just for people who fill in forms but for people who resemble those who became qualified leads. For the Google Ads side of the same idea, see Google Ads offline conversion tracking.
Consent and KVKK
The Conversions API gets around browser restrictions, but not user consent. If a visitor has rejected advertising cookies, you should not send events for that user from the server either. The customer information you send must be covered in your privacy notice, and its legal basis should be reviewed with a specialist (in Turkey, under KVKK, the personal data protection law).
Setting up your Meta campaigns to work with sales data is part of our Meta ads agency service; the server infrastructure is covered on the server-side tracking page.
Frequently asked questions
Does the Conversions API replace the Meta Pixel?
No. Meta recommends using the Pixel and the Conversions API together. The Pixel sends data from the browser and the Conversions API from the server; when the same event arrives through both channels, it is deduplicated with the event_id.
What is Event Match Quality?
Event Match Quality is the score Meta shows in Events Manager for how well the customer information you send can match an event to a Meta account. Parameters such as hashed email, phone and the click ID (fbc) raise the score.
Do I need a developer to set up the Conversions API?
Not necessarily. Built-in integrations on platforms such as Shopify and WordPress, Meta's Conversions API Gateway and server-side Google Tag Manager offer no-code or low-code routes. Custom systems and CRM events may need a direct API integration.
Can I send sales from my CRM to Meta?
Yes. With the Conversions API you can send events that happen off the website, such as a lead marked as qualified in your CRM or a closed sale, to Meta along with customer information. This moves lead-ad optimization from form volume to sales quality.
Sources
Furkan CoşkunPerformance Marketing Specialist
Furkan Coskun , specialized in digital marketing, stands out for its data-driven approach Performance Marketing Specialist 'tir. Produces effective results with high analytical skills in the planning, optimization and scaling of performance campaigns.
