Meta Conversions API (CAPI) Explained: Why You Need It and How to Set It Up
8 min read
The Meta Conversions API, usually shortened to CAPI, lets your server send conversion events directly to Meta instead of relying only on a pixel running in the visitor's browser. If you advertise on Facebook or Instagram and Meta reports fewer purchases or leads than your store or CRM records, missing browser data is a likely cause. CAPI is the standard way to shrink that gap.
This guide covers what CAPI is, why browser-only tracking falls short, what CAPI can and can't fix, the main ways to set it up, and how to test your work. It's written for marketers and business owners, with enough technical detail to brief a developer, and you don't need to code to follow it. Platform interfaces change, so confirm current menu names in Meta's own documentation.
What the Conversions API actually is
The Conversions API lets a server send events such as page views, add to cart, leads, and purchases to Meta over a secure connection. Your website backend, store platform, CRM, or a tag server reports the action instead of the visitor's browser. Each event carries the event name, a timestamp, and customer information parameters that help Meta match the action to a person who saw or clicked an ad.
In most setups CAPI doesn't replace the Meta Pixel. Meta recommends running both so each can cover for the other: the pixel captures browser-side signals and cookies, and the server connection sends events the browser may have lost. When the same event arrives through both routes, Meta uses a shared identifier to count it once. That process is called deduplication, and we cover it below. Think of the server route as a backup that also adds new kinds of events.
Why browser-only tracking loses data
A pixel depends on code loading and running in the visitor's browser, and plenty can interfere. Ad blockers and privacy-focused browsers can stop the script or its network calls. Safari and other browsers limit how long certain cookies last, which weakens the link between a click and a later purchase. On iPhones, Apple's App Tracking Transparency prompt lets people opt out of cross-app tracking, and that reduced the signals available to advertisers.
Consent choices matter too. In regions with privacy laws, visitors who decline marketing cookies shouldn't be tracked, and a well-configured site respects that. Page problems cost you data as well: a slow site, a tab closed before the pixel fires, or a thank-you page that doesn't load. So the pixel often sees only part of real activity. That skews reporting, and it hurts optimization, because Meta's delivery system learns from the events it receives. Fewer, lower-quality signals can mean weaker targeting.
What CAPI fixes, and what it does not
CAPI helps in a few specific ways. It can recover events the browser missed, since the server records the order whether or not a script ran. It can pass richer, hashed customer details, which improves matching. It also lets you send events that happen away from your website, like a lead qualifying in your CRM, a phone order, or an in-store purchase, so Meta can optimize toward outcomes that matter to your business instead of just form fills.
It won't bypass privacy rules or user choices. If a visitor hasn't consented to tracking where consent is required, you shouldn't send their data. It won't guarantee higher numbers either: some businesses see reported conversions rise and others see little change, depending on how much data they were losing before. And it can't fix a poor offer, weak creative, or the wrong event setup. Treat it as plumbing that makes your measurement more complete and more reliable.
- Recovers events lost to blockers and browser limits
- Sends CRM and offline events such as qualified leads or closed deals
- Improves customer matching through hashed identifiers
- Doesn't override user consent or privacy law
- Doesn't guarantee a specific lift in reported conversions
Setup options: choosing the right route
There are several ways to implement CAPI, and the right one depends on your platform, budget, and technical resources. Use the simplest option that sends the events you need with good match quality. Many small businesses can finish a partner integration in under an hour, while custom builds suit companies with unusual funnels or in-house developers. If you're unsure, begin with the partner option and move to a custom build only when a real gap appears.
Partner integrations
Platforms such as Shopify, WooCommerce, and several website builders and CRMs have built-in Meta connections that handle both the pixel and CAPI. You connect your Meta account, choose your pixel, and select the data-sharing level. For standard ecommerce stores this is usually the easiest and most reliable route. Check that the integration sends each event only once and isn't running alongside an older manual pixel.
Conversions API Gateway
Meta has a Gateway option that runs a managed server for you, often through a cloud provider, and forwards events from your existing pixel. It can suit teams who want server-side coverage without writing code, though hosting may carry a monthly cost. Hosting options, setup steps, and pricing change, so check Meta's current documentation before you commit.
Server-side Google Tag Manager
A server-side GTM container sits between your site and Meta, receiving events and forwarding them. You get flexibility and control, including shared use with other platforms, but it needs setup, hosting, and ongoing maintenance. If you already run server-side tagging for analytics, you can reuse the same container for Meta, which cuts duplicated effort and keeps tracking consistent across platforms.
Direct integration
A developer can send events straight to Meta's API from your backend. It gives you the most control and works well for custom applications and CRM-driven events, but it takes engineering time and testing. Someone has to define each event payload, handle errors and retries, and monitor delivery. Budget developer time for the initial build and for later changes to the site.
Event matching and deduplication
Two things decide whether CAPI works well: match quality and deduplication. Match quality depends on the customer information parameters you send, such as email, phone number, first and last name, city, and country. Meta requires most of these to be normalized, for example trimmed and lowercased, and then hashed with SHA-256 before sending. Browser identifiers such as the fbp and fbc values, plus the visitor's IP address and user agent, go through as they are. More valid parameters generally give better matching.
Deduplication prevents double counting when the same action arrives from both the pixel and the server. The standard method is to send the same event name and the same event ID from both routes. If the pixel fires a Purchase with an ID of order-1042, the server event should carry that same name and ID. Without it, you may see inflated counts. Meta's Events Manager shows an Event Match Quality score and flags deduplication problems, which helps you find weak spots.
Step-by-step setup
The exact screens differ by platform, but the sequence below fits most setups. Start by auditing what you have now, because fixing an existing pixel is often simpler than starting over. Then decide which events matter most to your business. Sending every possible event adds complexity and little else. For most advertisers the main events are a purchase or lead, plus a few upstream steps like view content and add to cart.
Work in a test environment where possible, and document your event names and IDs so everyone on the team uses the same ones. If you're using a partner integration, check its data-sharing setting and make sure it sends full customer information where your privacy policy and consent flow allow. Give each step an owner, since tracking projects often stall when nobody is responsible for the final test.
- Audit your existing pixel and events in Meta Events Manager
- Choose an implementation route that fits your platform and skills
- Connect your Meta business account, pixel, and any required domain verification
- Map your key events and decide which customer parameters you can legally collect
- Send the same event name and event ID from both pixel and server
- Add consent logic so events only send when permitted
- Test with Meta's Test Events tool before publishing changes
Testing and verifying your setup
Use the Test Events tab in Events Manager to confirm that server events arrive and are labeled as coming from the server. Trigger a real action on your site, such as a test purchase, and check that both the browser and server versions appear and are marked as deduplicated instead of counted twice. Review the diagnostics tab for warnings about missing parameters, delayed events, or low match quality. Run these checks before and after any site change.
Then reconcile with your own records. Over one to two weeks, compare Meta's reported purchases or leads with your store orders or CRM entries. They'll rarely match exactly, since Meta attributes conversions to ads while your backend counts every order. The relationship should be stable, though, and the gap should narrow once CAPI is live. If Meta's number jumps far above your real order count, suspect duplicate events.
Privacy, consent, and common mistakes
CAPI is a technical tool and gives you no legal cover. You remain responsible for collecting data lawfully and honoring consent, and your privacy policy should describe what you share with advertising partners. Where consent is required, wire your consent banner to the tracking setup so that declining marketing cookies also stops server events tied to that person. If you're unsure about requirements in your market, get qualified legal advice.
The common mistakes are easy to avoid once you know them. Sending events without an event ID causes double counting. Hashing values that shouldn't be hashed, or hashing without normalizing first, breaks matching. Incorrect values or currencies corrupt reporting. Another frequent problem is adding a partner integration on top of an existing manual setup and forgetting to deduplicate. Dynamic Growth is automated software, and its Tracking Health Check scans your site URL for detected tags and missing events, which gives a first look at your browser-side tracking before you build the server side. It has no access to your Meta account, so server events still need checking in Events Manager.
Frequently asked questions
Do I still need the Meta Pixel if I use CAPI?
In most cases yes. Meta recommends running the pixel and CAPI together so each covers gaps in the other, with deduplication preventing double counting. The pixel captures browser signals, while the server connection recovers events the browser misses and sends offline or CRM events.
Will CAPI increase my conversions?
It can increase reported conversions if your browser tracking was losing data, but no lift is guaranteed. Results depend on your audience, site, and how complete your pixel was before. The more dependable benefit is better data for optimization, rather than a fixed percentage gain.
Is CAPI the same as server-side tagging?
They're related but different. CAPI is Meta's API for receiving events. Server-side tagging, such as a server-side GTM container, is one way to send those events. You can also use a partner integration, the Gateway, or direct code to reach the same API.
Does CAPI work with a consent banner?
Yes, but you have to connect them. Events should only be sent when the visitor has given the consent your local law requires. A banner that stops the pixel while the server keeps sending data defeats the purpose and can create compliance risk. Test the consent paths.
How do I know if CAPI is working?
Open Events Manager and use the Test Events tool to see server events arrive, then check the diagnostics tab for warnings and your Event Match Quality score. Compare Meta's totals with your store or CRM over a couple of weeks. A stable relationship with no sudden spikes points to a healthy setup.