MetaStep 2 of 5 on the chain

Conversions API

Also called CAPI.

Meta's server-to-server route for sending events, used alongside or instead of the browser pixel. Offline and CRM outcomes reach Meta through it.

Why it matters

Meta's equivalent of offline conversion import, and the channel that carries lead-gen outcomes back. Without it, Meta optimises toward form fills and nothing further down.

What goes wrong

Sending the same event from both the pixel and the API is normal and expected; Meta deduplicates on an event id you supply. Getting that id wrong is the usual cause of double-counted conversions and inflated reported value.

For lead gen the events worth sending server-side are the ones the browser never sees: qualified, opportunity, closed won, each with its value and the identifiers Meta can match on. Meta scores each event's identifiers as an Event Match Quality figure, and a low score on the server-side lead event is the usual reason a CRM outcome is received but never attributed. A click identifier is the strongest signal, and Meta wants it in its own cookie format rather than raw from the URL.

How to check it on your own account

Events Manager, your dataset, Overview. Each event shows whether it arrives from the browser, the server or both, with a deduplication rate and a match quality score. A lead event arriving from the browser only means no CRM outcome is reaching Meta; a low match quality on the server event means outcomes arrive but do not attach to anyone.

Next to this

Where this comes up

In your trade

The industry pages that work this through for a kind of business.

The rest of this step

Measure this on your own data

The diagnostic reads a CRM export in your browser and reports your volume, your match rate and the spread between your leads against the thresholds in this glossary. Nothing is uploaded and no account is needed.

See what your own leads are worth

Read your closed deals and find out whether your lead values actually vary, and by how much. Nothing is stored, and your file is read in your browser.

Try it on a sample dataset