Last year your Meta ads closed sales like clockwork. Now they feel “blind.” Inside Ads Manager, the number of purchases being tracked has dropped off a cliff — yet WhatsApp is still buzzing with orders and revenue keeps flowing. Your ROAS looks ugly on the dashboard, and you’re left wondering: is the campaign broken, or is the data lying to you?

If this sounds like your business, the problem usually isn’t your creative or your targeting. It’s leaky tracking. The fix has a name: Meta’s Conversion API (CAPI). In this article we’ll cover why CAPI became non-negotiable in the iOS era, and the basic steps to set it up so your data is accurate again.

What Is Meta’s Conversion API (CAPI)?

You’ve probably already installed the Facebook Pixel: a snippet of code on your website that sends events (page views, add-to-cart, purchases) to Meta through the visitor’s browser. The catch is that this approach — called browser-side tracking — is remarkably easy to block. Browsers, ad-blocker extensions, and a user’s phone privacy settings can all quietly stop the Pixel from firing.

The Conversion API works differently. Instead of sending data from the browser, CAPI sends it directly from your website’s server or system to Meta’s servers. This is what’s known as server-side tracking. Because the path is server-to-server, the data is far more resistant to blocking and signal loss.

A Simple Analogy: Two Delivery Routes

Imagine you’re sending a sales report to head office (Meta). The Pixel is like handing it to a courier who has to pass through several checkpoints along the way: the browser, cookies, phone permissions. If any one checkpoint is closed, the report gets stuck in transit. CAPI is a direct line from your warehouse to head office, with no easily-closed checkpoints in between. Ideally, you run both routes at once so they cover each other’s gaps.

Why Your Data Started Leaking in the iOS Era

The turning point was iOS 14.5 and its App Tracking Transparency (ATT) feature. Since that update, every iPhone user gets asked: “Allow this app to track your activity?” The majority tap “Ask App Not to Track.” That means their activity after clicking your ad on Instagram or Facebook can no longer be fully tracked by the Pixel.

And this isn’t just an Apple problem. The privacy squeeze is tightening from every direction:

  • Browsers like Safari and Firefox cap the lifespan of advertising cookies.
  • Ad-blocker extensions block the Pixel code outright, before it ever runs.
  • Google Chrome is also moving to reduce its reliance on third-party cookies.

The impact on your business: plenty of real, completed purchases simply never get seen by Meta. As an illustration, out of 100 genuine transactions, the Pixel might only “see” 65. Meta then learns from that lopsided data, so ad optimization misfires, your cost per result climbs, and the ROAS on your dashboard looks worse than reality.

Signs Your Business Needs CAPI Right Now

You don’t need to be a technician to spot this. Check for these symptoms:

  • Sales in your store dashboard (Shopify, WooCommerce, or even manual records) are higher than the purchase count Ads Manager reports.
  • Events Manager is flagging warnings — a low Event Match Quality score, or reduced/missing data.
  • Your ROAS appears to be falling even though your actual revenue is going up.
  • You’re running Purchase or Lead campaigns with a meaningful budget (say, ad spend above Rp10 million per month), which makes data accuracy critical.

If you’re nodding along to at least two of these, CAPI is no longer a nice-to-have — it’s a necessity.

How to Set Up Meta’s Conversion API (The Basics)

The good news: setting up the Conversion API is far more beginner-friendly than it was a few years ago. Here’s the basic flow:

  1. Make sure your Pixel is installed correctly. CAPI works alongside the Pixel, not as a replacement. If your Pixel is still a mess, clean that up first. Not sure it’s right? Brush up on tracking fundamentals over on the Aira Tech blog before you continue.
  2. Choose a connection method that fits your website platform:
    • Partner Integration — the easiest option. If you’re on Shopify, WooCommerce, or another popular platform, you can connect via an official plugin or integration with no coding.
    • Conversions API Gateway — a semi-automated solution for those who want more control while keeping code to a minimum.
    • Manual (developer) — for custom-built sites, where your developer sends events straight to Meta via the API.
  3. Connect it in Events Manager. Open Events Manager in Business Manager, select your Pixel dataset, then follow the wizard to activate the Conversion API for your chosen method.
  4. Send as many matching parameters as possible. The more matching information you send (email, phone number, name, city), the more accurately Meta can identify the buyer. This sensitive data is automatically hashed (scrambled) before it’s sent, so raw details are never exposed.
  5. Enable and verify deduplication. This is the step people most often skip — so let’s cover it on its own.

Don’t Forget Deduplication

Because the Pixel (browser) and CAPI (server) can both send the same purchase event, you risk counting a single transaction twice. The solution is deduplication: Meta needs a unique identifier so it knows “ah, this is the same transaction — don’t double-count it.”

To make it work, ensure every event from the Pixel and CAPI carries the same event ID, plus parameters like fbp and fbc. Get this right and you reap the full benefit of CAPI without inflated purchase numbers. Once it’s live, check the status in the deduplication column and keep an eye on your Event Match Quality score in Events Manager — ideally sitting in the “Good” range or above.

What This Actually Does to Your Numbers

To make it concrete, here’s an example (illustrative figures, not a promise of results). Say you spend Rp10 million per month on a Purchase campaign. Before CAPI, the Pixel captures only 65 of every 100 real transactions. Meta optimizes from that skewed data, so your cost per purchase looks expensive and you hesitate to scale.

After CAPI is active and deduplication is clean, the purchase signals Meta can read might rise from 65 to somewhere in the 90s per 100 transactions. That doesn’t mean sales magically jumped — it means Meta now has a fuller map to go find more buyers like your best ones. Optimization gets sharper, reporting gets more honest, and your decisions to raise or cut budget are finally based on data you can trust.

Setting up server-side tracking correctly — Pixel, CAPI, matching parameters, and deduplication all working together — is fiddly to get right the first time, but it’s the foundation everything else in your account depends on. If you’d rather have it done properly, explore our Meta Ads and tracking services, see our management packages and pricing, or build a plan tailored to your business. And to keep sharpening your ads know-how, browse more guides on the Aira Tech blog.