SERP Master Agency

Paid ads · 11 min read · Updated Nov 12, 2026

Meta Conversions API: What It Is and When You Need It

The Meta Conversions API (CAPI) is a server-side connection that sends conversion events, such as leads, bookings and purchases, from your website server, platform, app or CRM straight to Meta. It works alongside the Meta Pixel so Meta still receives conversions the browser misses, which improves ad optimization and reporting.

This guide explains how CAPI differs from the Pixel, when you need it, the four ways to set it up, how deduplication works, what customer data to send and how to check that it is working in Events Manager.

Key takeaways

  • The Meta Conversions API (CAPI) sends conversion events such as leads and purchases from your server, website platform, app or CRM directly to Meta.
  • Meta recommends running the Conversions API alongside the Meta Pixel, with deduplication so the same event is not counted twice.
  • You need CAPI if you run Meta ads for leads or sales and judge them on results, because browser-only tracking misses some conversions.
  • Setup routes include one-click setup in Events Manager for Pixel users, partner integrations, the Conversions API Gateway and a direct developer integration.
  • Meta suggests aiming for an Event Match Quality score of 6.0 or higher out of 10, checked in Events Manager.

What is the Meta Conversions API?

The Meta Conversions API is Meta's tool for sending marketing events from your own systems to Meta. Events can come from your website server, website platform, mobile app or CRM. Meta uses the events to optimize ad delivery, build audiences and measure results, in the same way it uses events from the Meta Pixel.

Meta’s developer documentation describes the Conversions API as a way to connect an advertiser’s marketing data to Meta’s systems, with the stated goals of better ad targeting, lower cost per result and outcome measurement. Server events are attached to the same dataset (Pixel ID) as browser events and processed in a similar way.

The Conversions API can carry several event types:

  • Website events, such as a lead form submission, booking or purchase.
  • App events from a mobile app.
  • Offline conversions, such as in-store sales or phone bookings, which can be used for offline measurement and audiences.
  • Business messaging events from customer conversations in Meta messaging apps.
  • CRM events, such as a lead becoming a qualified lead or a customer.

You will often see it shortened to CAPI, and older articles call it the Facebook Conversions API. The product is the same.

How is the Conversions API different from the Meta Pixel?

The Meta Pixel is JavaScript code that runs in the visitor's browser and reports actions from there. The Conversions API sends the same actions from your server or platform. Browser tracking can be blocked by ad blockers, privacy settings or a page closing early, so Meta recommends running both together in what it calls a redundant setup.

FactorMeta PixelConversions API
Where it runsIn the visitor’s browserOn your server, platform, app or CRM
Affected by ad blockers and browser privacy settingsYesMuch less, because events do not depend on browser code
Can send offline and CRM eventsNoYes
Setup effortLow: add a code snippet or pluginLow to high, depending on the setup route
Best useOn-site behavior such as page views and add-to-cartReliable conversion events, plus offline and down-funnel outcomes

Why browser-only tracking falls short

When a conversion never reaches Meta, two things go wrong. Your reports show fewer results than really happened, so a profitable campaign can look like a failure. And Meta’s delivery system learns from fewer conversions, so it has less information about who is likely to act. Both problems raise your effective cost per result. For how tracking quality affects spend, see our guide on how much Facebook ads cost.

Meta’s deduplication guide states the recommendation plainly: implement the Conversions API alongside the Pixel and deduplicate the overlapping events.

When do you need the Meta Conversions API?

You need the Meta Conversions API if you run Meta ads to get leads, bookings or sales and judge them on those results. It matters most when you sell online, generate leads through forms or Instant Forms, close sales offline or in a CRM, or see fewer conversions in Ads Manager than in your own records.

We use a quick five-point check we call the CAPI priority check. Each yes moves CAPI higher on your to-do list.

QuestionIf yes
Do you optimize Meta campaigns for leads, bookings or purchases?Meta needs reliable conversion events to optimize. Add CAPI.
Does Ads Manager show fewer conversions than your CRM, booking system or store?Events are being lost. Add CAPI and deduplicate.
Do sales close later, by phone or in person?Send offline or CRM events so Meta learns which leads become customers.
Do you use Meta Instant Form lead ads at volume?Consider Conversions API for CRM to optimize for lead quality.
Would missing conversions change how you split your ad budget?Accurate data protects every budget call you make.

How to read the result

  1. Zero yes answers: you probably run awareness campaigns only. The Pixel is enough for now.
  2. One or two: set up CAPI through the simplest route your platform supports.
  3. Three or more: treat CAPI as part of launch, with deduplication and match quality checked before you scale budget.

Our Meta Ads management includes Pixel and Conversions API setup before campaigns go live, where your platform supports it.

Next step

Want CAPI set up properly?

We connect the Meta Pixel and Conversions API, set up deduplication and check match quality before your campaigns go live.

Free consultation

Tell us about your business and we’ll recommend a plan or a few fixed-price tasks.

How do you set up the Meta Conversions API?

There are four main ways to set up the Meta Conversions API: one-click setup in Events Manager for existing Pixel users, a partner integration built into your website platform or CRM, the Conversions API Gateway hosted in your own cloud account, or a direct integration written by a developer. Pick the simplest route that sends the events you need.

RouteHow it worksBest for
Events Manager setupMeta’s overview says Pixel users can set up CAPI for website events in one click from Events Manager, with no code and no setup feesBusinesses with a working Pixel that want the quickest start
Partner integrationYour ecommerce platform, CMS plugin or CRM sends events using its own connector, following the partner’s guidelinesStores and sites on platforms that offer a built-in Meta connection
Conversions API GatewayMeta’s setup guide has you create the Gateway in your organization’s AWS account, which takes about 30 to 40 minutesBusinesses that want server-side events without custom code and can manage a cloud account
Direct integrationA developer sends events from your server to Meta’s API using an access token generated in Events ManagerCustom sites, apps and CRMs, or when you need full control over the data sent

Steps that apply to every route

  1. Confirm access. You need a Meta business portfolio, admin access to the Pixel (dataset) and Events Manager.
  2. List your key events. Usually Lead, Schedule, Contact, AddToCart and Purchase. Match the names you use in the Pixel.
  3. Choose the route from the table above and connect it to your existing Pixel ID. Meta’s getting-started guide says to reuse that ID for browser and server events.
  4. Set up deduplication so events sent by both the Pixel and the server count once.
  5. Send customer information parameters that improve matching, hashed where Meta requires it.
  6. Verify in Events Manager before you change campaign budgets.

Google needs the same groundwork. If you also run Google Ads, a GA4 and Tag Manager install gives you one consistent tracking setup across platforms. For larger custom builds, our web development services team can handle server-side work.

How does deduplication work between the Pixel and Conversions API?

Deduplication stops Meta counting the same conversion twice when both the Pixel and the Conversions API send it. Meta's recommended method is to send a matching event ID and event name from the browser and the server. If both arrive within 48 hours, Meta keeps one and discards the duplicate.

Meta’s deduplication guide describes two methods.

Method 1: event ID and event name (recommended)

  • The Pixel’s eventID must equal the Conversions API’s event_id.
  • The Pixel’s event must equal the Conversions API’s event_name, for example Lead and Lead.
  • Matching events are deduplicated if they arrive within 48 hours of the first event with that ID.

Method 2: browser ID or external ID

  • Send the same event_name plus fbp (the browser ID cookie) or external_id in both the browser and server events.
  • This only works when the browser event arrives first. Two browser events or two server events with identical data are both kept.

When duplicates do not differ in a meaningful way, Meta generally keeps the one received first. If you send an event through only one channel, that event needs no deduplication.

Signs deduplication is broken

  • Conversions in Ads Manager jump to roughly double what your CRM or store shows.
  • Events Manager shows a low deduplication rate warning for an event.
  • Cost per result suddenly looks far better than your actual sales.

What customer data does the Conversions API send, and how is it protected?

The Conversions API sends customer information parameters that help Meta match an event to a person, such as email, phone, name, city, click ID and browser ID. Meta requires personal fields like email, phone and name to be hashed with SHA-256 before sending. Fields such as IP address, user agent, click ID and browser ID must not be hashed.

Parameter groupExamplesHashing rule (per Meta)
Contact and personal detailsEmail (em), phone (ph), first name (fn), last name (ln), date of birth, gender, city, state, zip, countryHashing required (SHA-256)
Your own customer IDexternal_idHashing recommended
Technical and Meta identifiersclient_ip_address, client_user_agent, fbc (click ID), fbp (browser ID), lead_idDo not hash

Source: Meta’s customer information parameters reference.

Privacy responsibilities stay with you

Hashing protects data in transit, but it does not replace consent. Your privacy policy should explain that you share conversion data with advertising partners, and your consent setup should follow the rules in the regions where your customers live. Send only the fields you need for matching. If your site handles sensitive categories such as health information, get advice on what you are allowed to send before you connect any events.

How do you check the Conversions API is working?

Check the Conversions API in Meta Events Manager. Meta says events should appear within 20 minutes of being sent. Then review three things for each key event: that server events are received, that the deduplication rate is healthy, and that Event Match Quality is 6.0 or higher on Meta's 1 to 10 scale.

  1. Confirm events arrive. Trigger a test lead or purchase and look for the server event in Events Manager. Meta’s verification guide says received events should show within 20 minutes.
  2. Check deduplication. Open the event’s details and the Event Deduplication tab. Meta says higher deduplication percentages are better and that a warning appears when the rate is too low. Low overlap suggests your event IDs are not unique or only one source sends them.
  3. Check Event Match Quality. Meta scores matching from 1 to 10 and typically recommends 6.0 or higher. Adding hashed email and phone, plus fbc and fbp, usually lifts the score.
  4. Check freshness. Meta recommends keeping the delay between an event happening and sending it as short as possible, so send website events in real time where you can.
  5. Compare against your own records. Once a week, compare Ads Manager conversions with your CRM, booking system or store. A large gap in either direction points to a tracking problem.

Tracking checks belong in the same routine as lead tracking in GA4. Our guide to GA4 key events covers the Google side of the same job.

Can the Conversions API improve lead quality from Meta lead ads?

Yes, through Meta's Conversions API for CRM. It sends lead stage updates from your CRM back to Meta, so you can use the Conversion Leads performance goal and optimize for leads that progress, such as qualified leads or booked appointments. It currently works only with Facebook and Instagram lead ads that use Instant Forms.

Many businesses find Instant Form leads cheap but uneven in quality. Conversions API for CRM closes that loop by telling Meta which leads went on to qualify or buy. Meta’s guide says this approach may yield higher quality leads that are more likely to convert.

Meta’s stated requirements

  • Lead ads using Instant Forms on Facebook or Instagram.
  • At least 200 leads per month.
  • Data uploads at least once per day.
  • The lead stage you optimize for must happen within 28 days of the lead being created.
  • The target stage must convert at between 1% and 40% of leads.
  • Store Meta’s 15 to 17 digit lead ID in your CRM, or send customer details such as email or phone for matching.

If your volume is below 200 leads a month, start with standard Pixel and Conversions API events on your website and grow into the CRM integration. For help deciding between lead ads and website forms, see our comparison of Google Ads vs Facebook Ads and our PPC services.

FAQ

Meta Conversions API FAQ

Can’t find your answer? Book a free consultation or email contact@serpmasteragency.com.

Meta does not charge for the Conversions API itself, and its overview says Pixel users can set it up for website events from Events Manager with no setup fees. Other routes can carry costs: the Conversions API Gateway runs in your own cloud account, and a direct integration needs developer time. Partner plugins may be free or paid.

Yes, in most cases. Meta recommends a redundant setup that runs the Pixel and the Conversions API together, with deduplication. The Pixel captures on-site browsing behavior, while the Conversions API makes sure key conversions still reach Meta when the browser blocks or drops them.

Meta scores Event Match Quality from 1 to 10 and typically recommends aiming for 6.0 or higher. The score reflects how well the customer information in your events matches Meta accounts. Sending hashed email and phone numbers, plus the fbc and fbp identifiers, is usually the quickest way to raise it.

The Conversions API Gateway is a Meta-provided way to send server-side events without writing custom code. Meta’s setup guide has you create it in your organization’s AWS account, which takes about 30 to 40 minutes, and connect it to your Pixel in Events Manager. You pay any cloud hosting costs.

Yes. Service businesses can send Lead, Contact or Schedule events from their website server or form tool, and businesses using Instant Form lead ads can use Conversions API for CRM to report which leads qualify. Our Meta Ads management sets up the events that match how you get customers.

One-click setup in Events Manager or a platform partner integration can be live the same day. The Conversions API Gateway takes about 30 to 40 minutes to create in AWS, plus configuration. A direct integration depends on your developer and systems. Allow time to verify deduplication and match quality afterwards.

The bottom line

Start by checking Events Manager: if you see only browser events for your key conversions, pick the simplest Conversions API route your platform supports, set up event ID deduplication, then confirm events arrive and Event Match Quality reaches 6.0 or higher. Do this before you raise budgets. If you want it handled as part of your campaigns, our Facebook advertising services include Pixel and Conversions API setup from day one.

Sources

  1. Conversions API, Meta for Developers, 2026
  2. Handling Duplicate Pixel and Conversions API Events, Meta for Developers, 2026
  3. Verifying Your Setup, Meta for Developers, 2026
  4. Get Started with the Conversions API, Meta for Developers, 2026
  5. Customer Information Parameters, Meta for Developers, 2026
  6. Conversions API Gateway Setup, Meta for Developers, 2026
  7. Conversions API for CRM Integration, Meta for Developers, 2026

Keep reading

Related guides

Demand Gen Campaigns Explained for Small Businesses

Demand Gen campaigns explained: where Google shows the ads, the creative you need, budget rules from Google, and when a small business should run them.

Read the guide →

Google Ads vs Facebook Ads: Which Fits Your Business?

Google Ads vs Facebook Ads compared on intent, cost per lead, targeting and budget, with 2026 benchmarks and a simple test to pick your first platform.

Read the guide →

How Much Do Facebook Ads Cost?

How much does Facebook ads cost in 2026? See average CPC, CPM and cost per lead by industry, how Meta's auction sets prices and how to plan a test budget.

Read the guide →

Get started

Get your Meta tracking right before you scale

Book a free consultation and we will review your Pixel, Conversions API and key events, then tell you what to fix first.