Meta Conversions API (CAPI): what it is, how it differs from the Pixel, and whether you need it
Installed the Meta Pixel, but the conversions in Ads Manager are always lower than reality? One reason is that browsers increasingly limit tracking: ad blockers, phone privacy settings and cookie restrictions all make the Pixel miss some events. The Conversions API (CAPI) is Meta's way of closing that gap.
What is the Conversions API?
The Pixel is code on your web page that records actions in the visitor's browser. The Conversions API sends events (such as a purchase or a submitted lead) from your server or system straight to Meta. If the browser blocks the Pixel, the server event still arrives.
Conversions API vs. Pixel
- Pixel: easy to set up and records page actions like views and add-to-cart, but browsers can block it.
- Conversions API: sent from a server, so more reliable, and it can send events that happen off the website, such as a lead becoming a sale in your CRM.
- Meta recommends using both together, not choosing one.
Won't using both count conversions twice?
When the Pixel and the Conversions API send the same event, set up deduplication: both send the same event name and the same event_id, and Meta counts it once. Without it, conversions are double counted and ad optimisation goes wrong.
How to set up the Conversions API
- Partner integrations: Shopify, WooCommerce and many other platforms have official or plugin integrations; connect them in Events Manager by following the steps. This is the simplest route.
- Conversions API Gateway: a Meta option that relays events through a cloud server for you, with no code, but you pay for the cloud hosting.
- Direct integration: a developer calls the API from your website backend or CRM. Most flexible, suits businesses with their own systems.
Once it's running, Events Manager shows each event's source (browser / server) and its Event Match Quality. The more customer information you send (hashed email, phone and so on), the higher the match quality and the better ads can find the right people.
Who needs the Conversions API?
- Online stores: accurate purchase numbers directly shape how ads optimise.
- Lead generation businesses: you can send a lead's later status in your CRM (qualified, closed) back to Meta, so the system learns to find better-quality leads. It works well alongside these fixes for low-quality leads.
- Businesses with bigger monthly ad spend that need accurate data to judge which ads work.
If you're just starting and take enquiries mainly on WhatsApp, a properly installed Pixel and the right campaign objective are enough for now. Not sure whether you need CAPI? See our Facebook ads management, or contact us.
Frequently asked questions
Do I still need the Pixel if I use the Conversions API?
Yes. Meta recommends using both: the Pixel records page actions, the Conversions API fills in events the browser blocks, and event_id deduplication stops double counting.
Does the Conversions API cost money?
The Conversions API itself is free. Partner integrations usually cost nothing extra; the Conversions API Gateway has cloud hosting costs; a direct integration has development costs.
What is Event Match Quality?
Event Match Quality is Meta's score for how well the customer information in an event can be matched to a Facebook user. More complete data usually means a higher score and better optimisation.
What is the difference between the Facebook Pixel and the Meta Pixel?
They are the same thing. The Facebook Pixel was renamed the Meta Pixel; the Conversions API works alongside it.