Skip to content
DestinationActivation

Meta Conversions API

CAPI is the path where events go from your server straight to Meta. What makes the difference here is what travels with them: because the platform already resolved who the person is, the delivery carries email, phone, external identifier, ad cookies and location — the fields that decide match quality — without you mapping anything by hand.

Data delivered

Data delivered

  • Standard events (Purchase, Lead, InitiateCheckout, ViewContent and others)
  • Custom events with any name you choose
  • Complete user_data assembled from the identity graph
  • Value, currency, content and custom properties

What it is for

What you can do with it

  • Recover conversions the browser pixel loses to blockers
  • Send the real sale value instead of a fixed estimate
  • Send only what matters: approved sales, first purchases, a specific product

How to connect

Step by step

  1. Step 1

    Create the Meta CAPI destination and paste your pixel access token.

  2. Step 2

    Run the connection test.

  3. Step 3

    Create a delivery: pick the source event, filter it and map the fields.

  4. Step 4

    Track deliveries, match quality and errors on the destination screen.

Frequently asked questions

Will it duplicate with the browser pixel?

Not if the event identifier is the same — and it is. Meta deduplicates on that identifier, and the platform sends it on both paths.

How do I know match quality is good?

The quality screen shows coverage of each parameter across payloads that were actually delivered: what percentage carried email, phone, ad cookie and so on.

Start measuring what actually becomes revenue

Create a free account, connect your first source and see your first lead timeline today. No card required.