Your Meta ads are optimising against incomplete data, and it is costing you. The Meta pixel runs in the browser, so ad blockers stop it, Safari limits it, and iOS privacy settings hide a large share of it. Meta sees fewer purchases than you actually got, learns from the wrong signals, and sends your budget to the wrong people. The Conversions API fixes this at the source. It sends purchases and leads to Meta from your own server, where ad blockers cannot reach. This guide covers what the Conversions API is, why the pixel alone no longer works, and how to run it on WordPress and WooCommerce.
This is one piece of a bigger shift. If it is new to you, start with our guide to server-side tracking on WordPress. The Conversions API is one of the destinations a server-side setup feeds.
What is the Meta Conversions API?
The Meta Conversions API, still often called CAPI or the Facebook Conversions API, is a server-to-server connection that sends customer actions straight from your server to Meta. Instead of relying only on the browser pixel, your server reports the purchase, lead, or add to cart directly. Because that connection does not run in the browser, ad blockers and browser privacy limits cannot stop it.
Meta recommends running the Conversions API alongside the pixel, not instead of it. Each event carries a shared identifier, so when the pixel and the API both report the same purchase, Meta counts it once. That is called deduplication, and getting it right is what separates a clean setup from double-counted sales.
Why the pixel alone is not enough
The browser pixel was built for a web that no longer exists. Four changes have eroded it:
- Ad blockers stop the pixel request before it fires, and a large share of users run them.
- Safari Intelligent Tracking Prevention caps how long the pixel cookie survives, so returning buyers look like new visitors.
- The iOS App Tracking Transparency prompt cut the signal Meta gets from a big part of mobile traffic.
- Third-party cookies are going away, which removes another path the pixel relied on.
Each of these widens the gap between the sales you made and the conversions Meta can see. A smaller, noisier signal means worse optimisation and a higher cost per result.
What the Conversions API fixes
- More complete conversion data. Purchases blocked in the browser still reach Meta from your server.
- Better optimisation. When Meta sees the real conversions, delivery improves and your cost per result usually drops.
- Higher event match quality. Server events can include hashed customer details that help Meta match the conversion to the right person.
- More durable attribution. Server-side events do not depend on cookies that Safari deletes early.
How the Conversions API works on WordPress
On WordPress and WooCommerce, a Conversions API setup has three parts: a plugin that captures the events, a server-side container that sends them to Meta, and Meta receiving them through the API.
The plugin watches your store for the actions Meta cares about: a product viewed, an item added to the cart, a checkout started, a purchase completed, a lead submitted. It pushes each one into the data layer using standard event names, and reads WooCommerce orders safely, including on stores using High-Performance Order Storage.
From there, a server-side Google Tag Manager container running on a first-party domain forwards the events to Meta through the Conversions API. It sends the shared event identifier so Meta deduplicates against the pixel, and it confirms purchases server to server, so a dropped browser event does not lose the sale.
Consent and customer data
The Conversions API sends customer data to Meta, so consent is not optional. Our setup runs Google Consent Mode v2, denied by default, so nothing fires until the visitor agrees. Customer details used for matching are hashed before they leave your site, and you decide what is sent. Done properly, a server-side setup gives you more control over that data, not less.
Setting it up on your store
The manual path is real work: stand up a tagging server, add and configure the Conversions API tag, map every WooCommerce event, hash the customer fields, wire up deduplication with the pixel, and test consent. Each step is a place to get it subtly wrong and either count sales twice or miss them.
We built our plugin and managed service to remove that. You install the plugin, import the container we provide into your Google Tag Manager, and point it at the tracking server we host. The Conversions API tag, deduplication, the WooCommerce funnel, and consent are already configured. There is no code to write and no server for you to run.
Want the Meta Conversions API set up on your store without the guesswork? See plans and pricing. It is one subscription from $15 a month and we set everything up for you.
Is it worth it?
If you spend meaningfully on Meta ads, the Conversions API usually pays for itself. Better data means Meta optimises against reality, which lowers your cost per purchase and reduces wasted spend. If you run little or no paid social, the pixel may be enough for now. We will tell you which case you are in before you commit.