The Meta Conversions API, often shortened to CAPI, lets a server send conversion events to Meta directly, without relying on the visitor's browser. Most sites use it alongside the Meta Pixel and send each event from both, with a shared ID so that Meta counts it once.
What the Conversions API is
The Meta Pixel is a script that runs in the visitor's browser and reports what happens on your site. The Conversions API does the same job from a server. Your server, or a tool acting for you, sends a request to Meta that describes the event.
Each event carries a few required pieces of information:
event_name: what happened, such asPurchaseorLead.event_time: when it happened.action_source: where it happened. For a site, this iswebsite.event_source_url: the page address.user_data: identifiers that help Meta recognize the person.custom_data: details such asvalueandcurrency.
The request is signed with an access token that you create in Meta's Events Manager. The token is a secret. It belongs on a server and never in a web page.
Why send the same event from browser and server
Each route has a weakness. The browser can be stopped by ad blockers, short-lived cookies or a tab closed too early. The server may not see Meta's own browser cookies unless your site passes them along. Our article on why ad platforms miss conversions covers the browser side.
Sending from both covers each weakness with the other route's strength. When the browser event arrives, Meta has the browser's context. When it is blocked, the server event still arrives. Meta recommends this paired setup.
It has one condition. Meta must be able to tell that the two events describe the same purchase. Otherwise it counts two.
Deduplication with event_id
Meta treats a browser event and a server event as the same event when they share the same event name and the same event ID. It keeps one and discards the other.
In the Pixel, the ID goes in the fourth argument:
fbq('track', 'Purchase',
{ value: 49.00, currency: 'USD' },
{ eventID: 'order-1042' }
);
In the Conversions API, the same value goes in the event_id field:
{
"event_name": "Purchase",
"event_time": 1794052800,
"event_id": "order-1042",
"action_source": "website",
"event_source_url": "https://example.com/checkout/thanks",
"user_data": { "em": ["<sha256 of the e-mail>"], "fbp": "fb.1.1794000000.1234567890" },
"custom_data": { "value": 49.00, "currency": "USD" }
}
For a purchase, the order number makes a good ID because both the page and the server know it. For events without a natural ID, such as a lead form, generate one ID in the browser and pass it to the server with the form.
Mistakes that break deduplication
- Different event names.
Purchasefrom the browser andpurchaseorOrderfrom the server do not match. - Two random IDs. The browser and the server each generate their own ID, so the IDs never agree.
- An ID on one side only. Without an ID on both events, Meta has much less to compare.
- A long delay. Meta only deduplicates events that arrive within a limited window of each other. A server event sent days later, in a batch, may be counted again.
- A reused ID. If every purchase carries the same fixed ID, Meta may discard real sales as duplicates.
Event match quality
An event is only useful to Meta if it can connect it to a person who saw or clicked an ad. Event match quality is a score out of 10 that Events Manager shows for each event. It reflects how much useful customer information your events carry and how well that information matches Meta accounts.
These are the main parameters that feed it:
| Parameter | What it is | Hashed before sending |
|---|---|---|
em | E-mail address | Yes |
ph | Phone number | Yes |
fn, ln | First and last name | Yes |
external_id | Your own customer ID | Recommended |
fbc | The click ID, from the _fbc cookie or the fbclid in the address | No |
fbp | The browser ID, from the _fbp cookie | No |
client_ip_address | The visitor's IP address | No |
client_user_agent | The visitor's browser name and version | No |
A purchase event usually scores higher than a page view, because the checkout has collected an e-mail address and a phone number. The click ID is especially valuable since it points to one specific ad click. Sending more parameters only helps when they are real and correctly formatted.
Hashed e-mail and phone
Meta asks you to hash personal details before sending them. Hashing runs the text through a one-way function, here SHA-256, that produces a fixed string of 64 characters. The same input always gives the same output, and the output cannot be turned back into the input.
Meta hashes the details it holds for its own accounts in the same way and compares the two strings. If they are equal, it has found the person without your server ever sending the readable address.
The comparison only works if both sides prepare the text identically, so normalize before hashing:
- E-mail: remove spaces at the start and end, and convert to lowercase.
Jane@Example.combecomesjane@example.com. - Phone: keep digits only and include the country code.
+1 (415) 555-0100becomes14155550100.
An address hashed with a stray capital letter produces a completely different string and matches nothing.
Hashing is a safeguard for data in transit. It does not remove your privacy obligations. A hashed e-mail address is generally still treated as personal data, and in regions with consent rules it should only be sent after the visitor has agreed. Check what applies to your business. Our article on consent mode and conversion tracking gives the general picture.
How to check your setup
- Open Events Manager and select your dataset, which is Meta's current name for a pixel.
- Use the Test Events tool. Send a test purchase and confirm that it arrives from both the browser and the server.
- Confirm that the two are shown as deduplicated and that one purchase is counted.
- Look at the event match quality for
Purchaseand see which parameters are being received. - Compare a week of purchases in Events Manager with a week of orders in your shop. The two totals should be close.
Where Tagbreeze fits
Tagbreeze sends each conversion to Meta from the browser and from its servers, with the same event name and event ID on both, so deduplication works without extra setup. It waits for consent in the EEA, the UK and Switzerland before sending.
In short
- The Conversions API sends events to Meta from a server. The Pixel sends them from the browser.
- Use both. Give each pair the same
event_nameand the same event ID so Meta counts one. - Event match quality rises with real, well-formatted identifiers, especially the click ID and a hashed e-mail address.
- Normalize before hashing, and send personal details only when you are allowed to.
To have this handled for you, add your site.