Paid ads · 11 min read · Updated Nov 12, 2026
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.
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:
You will often see it shortened to CAPI, and older articles call it the Facebook Conversions API. The product is the same.
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.
| Factor | Meta Pixel | Conversions API |
| Where it runs | In the visitor’s browser | On your server, platform, app or CRM |
| Affected by ad blockers and browser privacy settings | Yes | Much less, because events do not depend on browser code |
| Can send offline and CRM events | No | Yes |
| Setup effort | Low: add a code snippet or plugin | Low to high, depending on the setup route |
| Best use | On-site behavior such as page views and add-to-cart | Reliable conversion events, plus offline and down-funnel outcomes |
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.
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.
| Question | If 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. |
Our Meta Ads management includes Pixel and Conversions API setup before campaigns go live, where your platform supports it.
Next step
We connect the Meta Pixel and Conversions API, set up deduplication and check match quality before your campaigns go live.
Tell us about your business and we’ll recommend a plan or a few fixed-price tasks.
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.
| Route | How it works | Best for |
| Events Manager setup | Meta’s overview says Pixel users can set up CAPI for website events in one click from Events Manager, with no code and no setup fees | Businesses with a working Pixel that want the quickest start |
| Partner integration | Your ecommerce platform, CMS plugin or CRM sends events using its own connector, following the partner’s guidelines | Stores and sites on platforms that offer a built-in Meta connection |
| Conversions API Gateway | Meta’s setup guide has you create the Gateway in your organization’s AWS account, which takes about 30 to 40 minutes | Businesses that want server-side events without custom code and can manage a cloud account |
| Direct integration | A developer sends events from your server to Meta’s API using an access token generated in Events Manager | Custom sites, apps and CRMs, or when you need full control over the data sent |
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.
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.
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.
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 group | Examples | Hashing rule (per Meta) |
| Contact and personal details | Email (em), phone (ph), first name (fn), last name (ln), date of birth, gender, city, state, zip, country | Hashing required (SHA-256) |
| Your own customer ID | external_id | Hashing recommended |
| Technical and Meta identifiers | client_ip_address, client_user_agent, fbc (click ID), fbp (browser ID), lead_id | Do not hash |
Source: Meta’s customer information parameters reference.
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.
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.
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.
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.
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
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.
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.
Keep reading
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.
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.
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.
Get started
Book a free consultation and we will review your Pixel, Conversions API and key events, then tell you what to fix first.
Free consultation
Tell us about your business. We reply within one business day to plan the right service for you.
We have emailed you a confirmation. Our team will reply within one business day to set up your free consultation.
Pick a time nowAgency partnerships
Resell our SEO under your brand. Share a few details and we will send partner pricing and a sample white-label report.
We have emailed you a confirmation. Our partnerships team will reply within one business day with partner pricing.
Book a partnership call