The Facebook Conversions API (also called the Meta Conversions API, or CAPI) is a way to send conversion events to Meta directly from your server instead of relying only on the browser-based Meta Pixel. It matters because privacy changes have broken browser-only tracking, so server-side events restore much of the signal Meta needs to optimize and report accurately. Most advertisers should run the Pixel and CAPI together, with deduplication so each action is counted once.
What is the Facebook Conversions API?
The Conversions API is a server-to-server connection between your website (or app, or CRM) and Meta. When a customer takes an action that matters to you, your server sends a structured event to Meta describing what happened.
Two terms are worth defining clearly:
- Meta Pixel: a snippet of JavaScript that runs in the visitor’s browser and reports actions like page views and purchases. It is client-side tracking.
- Conversions API (CAPI): a server-side channel that reports the same kinds of actions from your own server. It is server-side tracking and does not depend on the browser.
An event is a single tracked action, such as Purchase, Lead, AddToCart, or CompleteRegistration. Each event can carry parameters like value, currency, and hashed customer information used for matching.
Why does CAPI matter now?
Browser-only tracking used to be enough. It is not anymore, for two well-established reasons.
Apple’s App Tracking Transparency and iOS 14.5
With App Tracking Transparency (ATT), introduced in iOS 14.5, Apple required apps to ask users for permission before tracking them across other companies’ apps and websites. Many people declined. This reduced the browser-based signal Meta could collect, which weakened optimization and reporting for advertisers.
Third-party cookies are going away
Third-party cookies are small files set by a domain other than the one you are visiting, historically used to follow users across sites. Browsers have moved to deprecate them, and Safari and Firefox already block them by default. As this support fades, client-side tracking loses reach and reliability.
Server-side tracking through CAPI is more resilient to these shifts because the event originates from your server, where you already have first-party data, rather than from a browser that may block scripts or cookies.
Pixel vs CAPI vs both
The most common question is whether to replace the Pixel with CAPI. For most advertisers the answer is to run both. The Pixel captures rich in-browser context, and CAPI captures events the browser misses.
| Capability | Pixel only | CAPI only | Both (recommended) |
|---|---|---|---|
| Where events originate | Browser | Your server | Browser and server |
| Resilient to ad blockers and cookie loss | No | Yes | Yes |
| Captures rich browser context | Yes | Limited | Yes |
| Tracks back-end events (refunds, CRM, offline) | No | Yes | Yes |
| Risk of double counting | Low | Low | Needs deduplication |
| Typical signal quality for optimization | Reduced | Strong | Strongest |
How does the Conversions API work?
The flow is straightforward once you see the pieces.
- A customer takes an action, such as completing a purchase.
- Your server builds an event with an event name, a timestamp, and parameters like value and currency.
- The event includes customer information parameters (for example email or phone) that are hashed before sending. Hashing converts data into an irreversible string so the raw value is never transmitted.
- Your server sends the event to Meta’s endpoint along with a shared event ID.
- Meta uses the data to match the event to a person where possible, then feeds it into ad optimization and reporting.
How do you set up CAPI?
There are several setup paths. Choose based on your technical resources, not on hype.
Direct integration
Your developer sends events to Meta’s API straight from your server. This offers the most control and the cleanest data, and it is the best fit when you have engineering support and back-end events to capture.
Partner or CMS integration
Platforms like Shopify, WooCommerce, and many tag managers offer built-in or app-based CAPI connections. This is the fastest route for most small and medium businesses because it avoids custom code.
Conversions API Gateway and one-click setups
The Conversions API Gateway is a managed, no-code option that mirrors your Pixel events to the server side and handles deduplication automatically. Meta has also introduced one-click, Meta-hosted CAPI setups inside Events Manager that require no server of your own. These lower the barrier for teams without developers, though direct integration still gives the richest control.
What is event deduplication?
Event deduplication is how Meta avoids counting the same action twice when it arrives from both the Pixel and CAPI. Without it, one purchase sent by the browser and again by your server could be counted as two.
Deduplication works by sending the same event ID and event name from both sources for a single action. When Meta sees two events that share those identifiers, it keeps one and discards the duplicate. Browser identifiers like the fbp cookie value also help Meta connect the two events. If you use the Gateway or many partner integrations, dedup is configured for you; with direct integration you must set the matching event ID yourself.
What does good signal do for optimization?
Better signal is not a vanity metric. It changes results.
- Smarter delivery: Meta’s models learn from more complete conversion data, so they find buyers more efficiently.
- More accurate reporting: you see conversions the browser would have missed, which corrects undercounted return on ad spend.
- Stronger matching: more event data with quality parameters improves how often events are attributed to a person.
- Lower cost per result: cleaner optimization usually means the algorithm wastes less budget on the wrong people. For practical steps, see our guide on how to lower CPA on Facebook ads.
Common CAPI mistakes to avoid
Most CAPI problems are setup problems, not platform problems.
- No deduplication: sending Pixel and CAPI without a shared event ID, which inflates conversion counts.
- Missing parameters: sending events without value, currency, or customer-information parameters, which weakens matching.
- Sending unhashed data: customer information must be hashed before it leaves your server.
- Ignoring diagnostics: the Events Manager Diagnostics tab flags dropped events, dedup errors, and parameter mismatches. Check it.
- Treating CAPI as optional: relying on the Pixel alone leaves real conversions uncounted. If your numbers look off, our breakdown of why Facebook ads are not converting covers tracking gaps in detail.
Where Adfure fits
Adfure is a profit-first AI media buyer for Meta, Google, TikTok, and LinkedIn. It is judgment-first, so you approve the moves, you keep full ownership of your ad account, and Adfure never touches your card. Strong server-side tracking is the foundation our 24/7 watch relies on, which is why our free AI ad audit checks your Pixel and CAPI signal first. You can also explore the full feature set or how we handle account access and security. If overspending is the worry, start with how to stop wasting money on Facebook ads, and for search, the Google Ads audit checklist.
Frequently asked questions
Is the Conversions API the same as the Meta Pixel?
No. The Meta Pixel is browser-based, client-side tracking, while the Conversions API is server-side tracking that sends events from your own server. They report similar actions but through different channels, and most advertisers run both together.
Do I still need the Pixel if I use CAPI?
In most cases yes. The Pixel captures rich in-browser context, and CAPI captures events the browser misses, such as ad-blocked sessions and back-end actions. Running both with deduplication gives the strongest, most complete signal.
Does CAPI replace cookies?
Not exactly. CAPI reduces dependence on third-party cookies by sending events from your server using first-party data. As browser tracking weakens, server-side events keep more of your conversion signal intact.
Will the Conversions API double-count my conversions?
Only if deduplication is not configured. When the Pixel and CAPI send the same event ID and event name for one action, Meta keeps a single event and discards the duplicate, so each action is counted once.
Do I need a developer to set up CAPI?
Not always. Partner and CMS integrations, the Conversions API Gateway, and Meta’s one-click setups let many small businesses enable CAPI without custom code. A developer gives you the most control and the cleanest data through direct integration.
Is CAPI worth it for a small business?
Yes. Better signal improves delivery, reporting accuracy, and matching, which usually lowers cost per result. The setup effort is modest, especially through a partner integration or the Gateway.
Want to know how complete your tracking signal really is? Get a free AI ad audit and see your Pixel and CAPI health before you spend another dollar.