The Meta Conversions API Explained

A plain-English starter guide to how Facebook ads, the Pixel, and the Conversions API actually work in 2026. Written for marketers, not engineers.

The Meta Conversions API (CAPI) sends conversion events to Meta directly from your server instead of from the visitor's browser. That matters because browser tracking is leaking. Ad blockers, iOS privacy changes, and cookie restrictions mean the Meta pixel now misses a large share of the conversions that actually happen, and Meta's algorithm can only optimise on the data it receives.

This guide covers what CAPI is, how it works alongside the pixel, and how to get it running on a Webflow, Framer, Squarespace, or WordPress site without writing code or touching a server. By the end you will understand what the pixel actually does, why it now misses so much, how CAPI fills the gap, and what good tracking data is really for. No jargon, and no developer required.

What the Facebook Pixel (Dataset) Is

A pixel (also known as dataset) is the connection between your site and Meta. It carries messages about what people do. Each message is an event:

  • ViewContent: someone looks at a product or key page

  • AddToCart: someone adds something to their cart

  • InitiateCheckout: someone starts checkout

  • Lead: someone fills in a form or enquiry

  • Purchase: someone buys

Meta uses this stream for two jobs:

1. reporting how your ads did
2. deciding who to show your ads to next. The second job is where the money is.

For a deeper breakdown of which events matter most, see our walkthrough of the 7 Meta events you should be tracking for better ad performance.

What the Conversions API Does

For years every event was sent from the visitor's browser. That worked until it did not. Apple's privacy changes block tracking on iPhones unless people opt in (most do not), ad blockers stop the pixel firing, and browsers restrict cookies. The browser alone now misses a big share of what really happened, often a quarter or more of your conversions.

The Conversions API (CAPI) fixes this from the other side. Instead of relying on the browser, your server sends the event straight to Meta's server. No browser in the middle to block or lose it.

You run both together. The browser sends what it can, CAPI fills the gaps, and a shared event ID stops the same sale being counted twice. This is called deduplication, which is why running both is safe.

New to the Conversions API? Two shorter, focused reads: Why do you need the Conversions API? and How does the Conversions API work?. For the side-by-side, see Facebook Pixel vs Conversions API.

Event Match Quality: Why the Details Matter

When you open Events Manager you will see an Event Match Quality score out of 10 for each event. Here is what it means in plain terms.

For Meta to learn from a conversion, it has to match that event to a real Meta account. It does this using the identifying details you send with the event: email, phone, name, location, and so on (all securely hashed, so you are not handing over raw personal data; Meta only sees a scrambled version of these details, never the raw values). The more good detail you send, the more confidently Meta matches it, and a higher match score means better optimisation.

This is also where CAPI quietly wins. A browser often cannot access much identifying detail, but your server usually can (you already have the customer's email and details at checkout). Richer identifiers sent server-side lift your match quality, which lifts everything downstream. If your score is low, that is usually the first thing to fix.

For the full mechanics of how Meta calculates this number, see How Facebook generates Event Match Quality scores.

How Good Data Helps, and Why it is Not About One Buyer

Meta's ad system is a prediction engine. When you ask for purchases, it is constantly guessing which person out of billions is most likely to buy from you right now. The quality of those guesses depends entirely on the examples it learned from.

When the browser loses a quarter of your conversions, you are hiding a quarter of your best teaching examples. The engine has fewer confirmed buyers to learn from, so its guesses get worse, and worse guesses cost you more per result. CAPI restores those examples.

Now the part that saves the most money: the value of a buyer is the pattern, not the person. The individual who just bought is the least useful person to advertise to next, because they already bought (you usually want to exclude them from acquisition). Their real worth is teaching Meta what a buyer looks like, so it can find new people who resemble them. These are lookalikes, and they are where growth comes from. The data is fuel for finding the next thousand buyers, not a leash to drag one back.

And you never stop training. Every fresh purchase keeps the engine's picture current as seasons, trends, and products change. Feed it the whole funnel (views and add-to-carts, not just sales), and feed it continuously. Stop, and its picture of your customer slowly goes stale. If you want a deeper read on how to send the right events at the right time, see How to send smarter Meta CAPI events (and stop training your pixel wrong).


Why Broad Targeting Now Beats Manually Selecting "Interests"

A few years ago you were taught to pick your audience by hand: choose interests like "yoga," layer on demographics, narrow it down. That was right when the engine was weak and needed pointing.

The engine is no longer weak. When fed strong data and conversion signals, it finds your buyers better than you can describe them.

People interested in yoga are not necessarily people who buy your yoga product; the engine, learning from real purchases, finds the ones who actually buy. This is why broad targeting (often called Advantage+) now beats hand-built interest stacks.

But notice the condition: broad targeting only works if you feed the engine good data. Broad with weak signal is blind guessing across a huge audience, and it flails. Broad with strong signal is confident picking, and it wins. That is the direct link between CAPI and modern strategy.

The reason broad now wins is Meta's new ad delivery engine, Andromeda.

For the full story of what Andromeda is and how to optimise for it, see What is Andromeda for Facebook ads (and how to optimise for it) or our broader piece on why Meta ads strategy changed.

Haven't attribution windows shrunk?

Yes, and that makes good data matter more, not less.

An attribution window is how far back Meta looks to credit a conversion to an ad. After Apple's privacy changes the default got shorter (commonly 7-day click, 1-day view), and the old long 28-day default went away. So Meta now credits a conversion only if it happens fairly soon after the click.

A shorter window leaves less room for error. A conversion the browser fails to report, or reports late, can fall outside the window and never get counted, never teach the engine, never appear in your reporting. When the window was long, sloppy tracking was survivable. Now every lost or delayed event is a real loss, and CAPI helps by delivering events reliably and promptly.

For a related reading, see Why Facebook attributes leads to ads you don't think came from Facebook. It explains how Meta's view-through and modelled attribution work, which is why your reporting sometimes credits ads you didn't expect.

Why Meta's numbers won't match your backend

Expect this, so it does not alarm you. Meta will often report a different number of sales than your store or payment system shows. The tool is not broken and Meta is not lying. They simply count differently.

Meta credits sales within its attribution window and to the ad it thinks influenced them, fills some gaps with modelled estimates, and loses some events to iOS. Your backend counts every order regardless of how it found you. These are two different questions ("how many orders did I get" versus "how many orders can Meta tie to an ad it showed"), so the numbers rarely line up exactly. Use your backend as the source of truth for revenue, and use Meta's numbers to compare ads against each other.

If the gap between Meta and your backend is uncomfortably wide, the fix is usually upstream of reporting. See Why Facebook ads underreport conversions and how to fix it.

Be patient: the learning phase is real

New advertisers often judge results on day two, panic at erratic numbers, and switch everything off. That is usually a mistake.

The engine needs a stash of conversions before its guesses stabilise. Early on, results swing around while it learns; this is called the learning phase, and bumpy early numbers are normal, not a sign of failure. Give campaigns time and conversions to settle before judging them. Turning things off too early resets the learning and wastes the spend that was buying it.

For a structured checklist of what to set up before launching a campaign (and what to avoid touching after), see the Meta Ads Checklist 2026.

Honest expectations: data is necessary, not magic

Good signal makes a good offer and decent creative perform better. It cannot rescue a weak offer or a bad ad. Think of clean data as removing the friction between you and Meta's engine: it lets a good product find its buyers faster and cheaper, but the product and the offer still have to be worth buying. If the fundamentals are not there, better tracking will show you the truth sooner rather than hide it.

How long can Meta keep using your data?

When someone triggers an event, Meta can hold them in a custom audience for a limited time, then they age out:

  • Website custom audiences (views, add to cart, leads, etc.)up to 180 days

  • Purchase-event audiences (website and app)up to 730 days

  • Meta native lead-form (Instant Form) engagementup to 90 days

Purchases get the longest window because they are the highest-value signal and many buying cycles run longer than six months.

Note that a Lead event sent to your pixel is on the 180-day clock, which is different from a Meta native lead form at 90 days. If you are in a region with strong privacy rules, these are the maximums Meta allows, not necessarily what your consent and privacy policy permit.

Remember this if nothing else

You are not buying ads. You are training a prediction engine, then buying the quality of its predictions. Good, complete data buys good predictions, and good predictions buy cheap results.

  • The pixel is a teacher, not a net.

  • The browser loses events; CAPI sends them server to server so they arrive.

  • Higher match quality (more identifiers) means better optimisation.

  • Data teaches a pattern, not chases a person. Patterns find new buyers.

  • You never stop training, and you feed the whole funnel.

  • Broad targeting wins now, but only with strong signal behind it.

  • Shorter attribution windows make clean, prompt data more important.

  • Meta's numbers won't match your backend, and that is normal.

  • Give the learning phase time before you judge results.

  • Data is necessary, not magic; the offer still has to be good.

Where PixelFlow fits in all of this:

All of the above assumes you can actually get your events, especially server-side CAPI events, flowing to Meta cleanly. That used to mean writing server code, out of reach for anyone on a no-code platform without a developer.

That is the gap PixelFlow closes. It sends your events server-side through the Conversions API without you touching code, so you get the data-quality benefits this guide describes (more matched conversions, fewer lost events, higher match quality) that used to need an engineering team. We have dedicated guides and integrations for every major no-code platform:

If your stack uses third-party tools to handle booking or payments, you can route those events through PixelFlow too. See Track Calendly bookings with Facebook CAPI and Track Stripe payments with Facebook CAPI. For the general no-code setup walkthrough, see Set up Facebook CAPI on any website without code (visual tagger guide).

In plain terms, PixelFlow lets the prediction engine see more of what really happened on your site, which is the whole game.

Glossary


  • CAPI (Conversions API): sends events from your server to Meta, bypassing the browser.

  • Pixel / Dataset: the connection that carries your site's events to Meta.

  • Event: a single reported action (ViewContent, AddToCart, Lead, Purchase).

  • EMQ (Event Match Quality): a 0 to 10 score for how well Meta can match your events to real accounts.

  • Lookalike: new people Meta finds who resemble your existing buyers.

  • Learning phase: the early period where the engine gathers conversions and results are unstable.

  • Attribution window: how far back Meta looks to credit a conversion to an ad.

  • ROAS: return on ad spend, revenue divided by ad cost.

  • CPA: cost per acquisition, what you pay for one result.

  • ATT: Apple's App Tracking Transparency, the iPhone prompt that lets users block tracking.

Related reading


Fix Your Meta Tracking Today

Accurate reporting and attribution for your Facebook Ads

Start 7 Day Free Trial

Start 7 Day Free Trial

Frequently Asked Questions

What is the Meta Conversions API in simple terms?

It is a way to send your website's conversion events (purchases, leads, sign-ups) to Meta from your server instead of from the visitor's browser. Because the browser is no longer the only path, far fewer events get lost to ad blockers and privacy settings.

Is the Conversions API free?

Meta does not charge for the API itself. What you need is a way to send data to it. Doing that by hand requires server code and a developer. Tools like PixelFlow handle the connection for you without code.

Do I need a developer to set up the Conversions API?

Not with PixelFlow. It runs CAPI on no-code platforms like Webflow, Framer, Squarespace, and WordPress without you writing or touching any code. Setting it up manually does require a developer, which is the problem PixelFlow exists to remove.

Do I still need the Facebook pixel if I have CAPI?

Yes. You run both together. The pixel captures browser-side signals and CAPI fills the gaps it loses, with deduplication making sure nothing gets counted twice. See Facebook Pixel vs Conversions API.

Will the Conversions API actually improve my ad results?

It gives Meta more complete and better-matched data, which usually means cheaper, better-optimised results over time. It is not magic, though. Good data helps a good offer perform; it cannot rescue a weak one.

Is the Conversions API GDPR compliant?

The data you send is hashed, so Meta receives a scrambled version of personal details rather than the raw values. That said, CAPI does not remove your consent obligations. You still need valid consent before sending events from visitors in regulated regions.

How do I know if CAPI is working?

Check Events Manager. You should see your events arriving with a server source, a healthy Event Match Quality score, and deduplication recognising the matching pixel events. A low match score is usually the first thing to improve.

Does CAPI work on Webflow, Framer, and Squarespace?

Yes. These platforms do not give you a server to run CAPI yourself, which is exactly why PixelFlow handles it for you. We have simple installs for Conversions API on Webflow, Framer, Squarespace, WooCommerce, Kajabi and many more.