Lucid Brands Home
©Lucid Brands 2026
Paid Media Marketing resource article: Meta Conversions API (CAPI) Explained

Meta Conversions API (CAPI) Explained

The Meta Conversions API (CAPI) is a way to send conversion events, such as purchases, leads and sign ups, directly from your server, website platform or CRM to Meta, instead of relying only on the Meta Pixel in a visitor's browser. Because it does not depend on the browser, it keeps working when ad blockers, cookie limits or browser privacy settings stop the Pixel. Running CAPI alongside the Pixel gives Meta more complete data, which helps it attribute results and find more people likely to convert.

What is the Conversions API?

An API is a way for two systems to talk to each other. The Conversions API lets your systems tell Meta, "This person just bought, and here is what we know about them," in a privacy safe, hashed form. Meta then matches the event to an ad click or view and uses it for reporting and optimization.

The term started with Meta, but the idea has spread. Google, TikTok, LinkedIn, Pinterest and others now offer server side conversion connections of their own.

Pixel vs Conversions API

Meta PixelConversions API
Where it runsIn the visitor's browserOn your server, platform or CRM
Affected by ad blockers and browser limitsYesNo
Can send offline events (phone sales, CRM stages)NoYes
SetupPaste code or use a pluginPartner integration, Gateway, server tag manager or direct code
Best practiceKeep it runningRun alongside the Pixel, with deduplication

Meta recommends using both. The Meta Pixel captures browser behavior; CAPI fills the gaps and adds events the browser never sees.

Why it matters

  • More complete data. Supermetrics, citing Meta's own studies, reports advertisers saw up to 19% additional attributed events, up to a 13% improvement in cost per result and a 44% increase in lead to quality lead rate. These are Meta's figures; your results will vary.
  • Browser privacy keeps tightening. Rokt cites a 2024 Statista survey in which 92.8% of advertisers and publishers were at least somewhat concerned about third party cookie deprecation.
  • Better optimization. Meta's delivery system learns from the conversions it sees. Missing conversions mean weaker targeting and higher costs. If you are asking why your Facebook ad costs are high, incomplete tracking is one common cause.
  • Offline and lead quality signals. You can send events like "qualified lead" or "closed deal" from your CRM so Meta optimizes for leads that turn into customers.

How it works

  1. A visitor clicks your ad and lands on your site.
  2. They take an action (add to cart, purchase, submit a form).
  3. The Pixel fires in the browser (if not blocked).
  4. Your server or platform sends the same event to Meta through CAPI, with an event ID and hashed customer details such as email and phone.
  5. Meta deduplicates the two events, matches the person and credits the ad.

Sample server event (simplified)

{
  "data": [{
    "event_name": "Purchase",
    "event_time": 1763200000,
    "event_id": "order_10482",
    "action_source": "website",
    "event_source_url": "https://example.com/checkout/thank-you",
    "user_data": {
      "em": ["<SHA256 hash of lowercase email>"],
      "ph": ["<SHA256 hash of phone with country code>"],
      "client_ip_address": "203.0.113.10",
      "client_user_agent": "Mozilla/5.0 ...",
      "fbc": "<click ID cookie value>",
      "fbp": "<browser ID cookie value>"
    },
    "custom_data": { "currency": "USD", "value": 89.00 }
  }]
}

Four ways to set it up

OptionHow it worksBest forCost
Partner integrationBuilt in connection in Shopify, WooCommerce, WordPress plugins, Wix, Squarespace and othersMost small businesses and storesUsually free with the platform
Conversions API GatewayA Meta tool hosted in your cloud account that mirrors Pixel events server sideTeams without developers on custom sitesCloud hosting fees; check current pricing
Server side tag managerSend events through a server container, often with Google Tag ManagerBusinesses tracking several ad platformsServer hosting fees and setup time
Direct integrationDevelopers send events from your backend or CRMCustom platforms, offline events, lead quality signalsDeveloper time

Rule of thumb: use the partner integration if your platform has one. Choose a server side tag manager if you advertise on several platforms. Use direct integration for CRM and offline events.

Step by step: partner integration setup

Labels in Meta Events Manager change from time to time; the flow is broadly:

  1. In Events Manager, open your dataset (formerly called a Pixel) and choose to add events through the Conversions API.
  2. Pick your platform from the partner list (for example Shopify or WooCommerce).
  3. Connect your Meta business account in the platform's settings and choose "maximum" or the highest data sharing level you are comfortable with and permitted to use.
  4. Confirm the events being sent: PageView, ViewContent, AddToCart, InitiateCheckout, Purchase, Lead.
  5. Wait for events to appear, then check the Overview for both "Browser" and "Server" sources.
  6. Check deduplication and Event Match Quality (below).
  7. Use the Test Events tool to confirm each event before running campaigns.

Deduplication

When the Pixel and CAPI both send the same purchase, Meta needs to know it is one purchase, not two. It does this with two fields:

  • event_name must match (for example "Purchase" in both).
  • event_id must match (for example the order number).

If they do not match, Meta may count conversions twice, which inflates results and confuses optimization. Partner integrations usually handle this; custom setups must pass the same ID from browser and server.

Event Match Quality

Event Match Quality is Meta's score (out of 10) for how well your server events can be matched to Meta accounts. Higher scores mean more events are credited. To improve it:

  • Send hashed email and phone whenever you have them.
  • Include the fbc (click ID) and fbp (browser ID) values.
  • Send IP address and user agent from the original browser request.
  • Add first name, last name, city, state and zip (hashed) where you collect them.
  • Send events in real time, not in late batches.
  • Only send data you have the right to share, and say so in your privacy policy.
  • Respect consent choices. If a visitor declines marketing cookies where consent is required, do not send their events for advertising.
  • Hash personal data before sending (partner integrations do this automatically).
  • Be extra careful in regulated categories like health and finance, where sending some events may be restricted.

Troubleshooting

ProblemLikely causeFix
Conversions doubledMissing or mismatched event_idPass the same ID from Pixel and server
Low Event Match QualityFew customer parameters sentAdd hashed email, phone, fbc, fbp, IP and user agent
Server events but no browser eventsPixel removed or blockedReinstall the Pixel; keep both
Events delayedBatch sendingSend in real time
Purchase values wrongCurrency or value field mappingCheck custom_data in Test Events

Conversions APIs on other platforms

PlatformServer side option
Google AdsEnhanced conversions and offline conversion imports
TikTokEvents API
LinkedInConversions API
PinterestConversions API

See our guides to conversion tracking and marketing attribution to bring them together.

Sending CRM and offline events

For lead generation businesses, the most valuable use of CAPI is often not website events but what happens after the lead arrives. If Meta only sees form fills, it optimizes for people who fill in forms, including poor quality leads. If it also sees which leads became qualified or closed, it can find more people like your real customers.

How it works:

  1. Capture Meta's click ID (fbc) and browser ID (fbp) with each lead, along with email and phone.
  2. Store them on the lead record in your CRM.
  3. When the lead moves to a stage such as "qualified" or "won", send an event (for example "QualifiedLead" or "Purchase") through the Conversions API with the same customer details and the stage value.
  4. In Ads Manager, test optimizing for the deeper event once you send enough of them each week.

Many CRMs have native Meta integrations or can do this through automation tools. Send events promptly; events sent long after the click are less useful for optimization.

Conversions API setup checklist

  • Meta Pixel installed and firing on every page.
  • CAPI connected through a partner integration, Gateway, server tag manager or direct integration.
  • Standard events mapped: PageView, ViewContent, AddToCart, InitiateCheckout, Purchase, Lead.
  • Matching event_name and event_id sent from browser and server.
  • Hashed email and phone included where collected.
  • fbc, fbp, IP address and user agent passed with server events.
  • Purchase value and currency correct in Test Events.
  • Event Match Quality reviewed for each key event.
  • Consent rules applied and privacy policy updated.
  • Offline or CRM events planned for lead quality.
  • Monthly check scheduled for drops in server events or match quality.

FAQ

What is a conversions API and how does it work?

It is a server to server connection that sends conversion events from your website platform, server or CRM to an ad platform. It works alongside browser pixels and is not affected by ad blockers or browser cookie limits.

Is the Conversions API free?

Meta does not charge for the API itself. Partner integrations are usually free, while the Gateway and server side tag managers involve hosting costs, and direct integrations cost developer time.

Is the Conversions API worth it?

For most advertisers spending meaningfully on Meta, yes. It recovers conversions the Pixel misses and lets you send lead quality data. Supermetrics, citing Meta, reports up to 13% improvement in cost per result, though results vary.

Do I still need the Meta Pixel if I use CAPI?

Yes. Meta recommends running both with deduplication. The Pixel captures browser behavior and CAPI fills the gaps.

Make sure your ads get credit for every sale

Lucid Brands's free media audit checks your Pixel, Conversions API, deduplication and Event Match Quality. Our Media Management service starts at $500 a month and includes tracking setup across Meta and Google. Read our Facebook advertising guide or contact us. If you want lead quality events from your CRM, see what is a CRM and ask about our CRM Creation and Integration service.

Your path to lucidity

Get Started With a Free Paid Media Audit

Not sure where to begin? Start with a free paid media audit. We'll show you where your current spend is working, where it's leaking, and what we'd do first.