Meta CAPI guide and setup service

Meta Conversions API: How It Works and How to Set It Up Properly

The Meta Conversions API (CAPI) sends conversion events from your server straight to Meta, alongside the browser Pixel. Done properly, with event_id deduplication and strong customer data, it recovers events lost to ad blockers and Safari and gives Meta better signals to optimise on.

Updated November 2026 · By Abdul Kayium

On this page

  1. What is the Meta Conversions API?
  2. Pixel vs Conversions API vs both
  3. How Meta CAPI works
  4. 5 ways to set up Meta CAPI
  5. Event Match Quality and customer parameters
  6. Deduplication with event_id
  7. Consent and GDPR
  8. Testing with Test Events
  9. Common mistakes
  10. How I set it up for you
  11. FAQ

What is the Meta Conversions API?

The Meta Conversions API is a server-to-server connection between your website, store or CRM and Meta's ad system. Instead of relying only on a JavaScript Pixel in the visitor's browser, your server sends events like Purchase, Lead or CompleteRegistration directly to Meta's Graph API.

Why it matters: the browser is a hostile place for tracking now. Ad blockers stop the Pixel from loading, Safari's tracking prevention shortens cookies, and people close the tab before the thank-you page fires. In the accounts I audit, the Pixel alone usually misses somewhere between 10% and 30% of purchases. Meta's algorithm can only optimise on what it sees, so missing conversions mean worse targeting and higher cost per result.

CAPI fixes the delivery problem. It also lets you send data the browser never has, such as order margin, a CRM lead status or a refund, and it is the only route Meta now offers for offline and CRM events. I have set it up for 250+ businesses, from Shopify stores to B2B lead-gen sites, and the pattern below is what I use every time.

Pixel vs Conversions API vs both

The question is not Pixel or CAPI. Meta's own recommendation, and mine, is a redundant setup: both send the same events and Meta deduplicates them. Here is how the three options compare.

Pixel onlyCAPI onlyPixel + CAPI (recommended)
Where it runsVisitor's browserYour serverBoth
Blocked by ad blockersOftenNoServer copy still arrives
Affected by Safari ITPYes, short cookiesLess, if cookies are set first-partyLess
Captures fbp and browser contextYesOnly if you pass them throughYes
Can send CRM or offline eventsNoYesYes
Event Match QualityMediumMedium to highHighest
Setup effortLowMedium to highMedium, needs dedup

CAPI on its own works, but you lose the browser signals the Pixel picks up for free. Pixel on its own is cheap, but it will undercount. Running both, with deduplication, gives you the coverage of the server and the context of the browser.

How Meta CAPI works

Take a purchase. When the order completes, two copies of the same event are sent to Meta: one from the browser Pixel and one from your server. Both carry the same event_name (Purchase) and the same event_id, usually the order ID. Meta receives both, sees they match, keeps one and fills in any missing data from the other.

If the Pixel is blocked, the server event still gets through and counts. If the server is slow, the Pixel event is already there. Either way Meta records one conversion, not two. That is the whole idea, and almost every CAPI problem I fix comes back to one of those three boxes being wrong.

5 ways to set up Meta CAPI

There is no single correct method. The right one depends on your platform, your budget and whether you also need server-side tracking for GA4 and Google Ads.

1. Server-side GTM on Stape

This is my default. A server GTM container runs on your own subdomain (for example sst.yourdomain.com), hosted on Stape or Google Cloud Run. The web container sends events to it, and the Meta CAPI tag forwards them to Meta. The same container also feeds GA4 and Google Ads, so you build one pipeline instead of three. I walk through it step by step in Meta CAPI setup via server GTM, and the dedup side in server GTM deduplication for Meta. The wider picture is on my server-side tracking page.

2. Meta Conversions API Gateway

CAPI Gateway is Meta's own hosted option. It mirrors your Pixel events to the server automatically, with little configuration. It is quick and needs no tagging work, but it only serves Meta, gives you limited control over the data, and you still pay for the hosting (through AWS or a partner such as Stape). Good for teams who run Meta only and want something simple.

3. Shopify native or partner integration

The Facebook and Instagram app on Shopify turns on CAPI with a few clicks and sets the data sharing level to Maximum. It is fine for small stores. The limits show when you spend more: little control over parameters, no custom events, and it does not help your other platforms. Many stores move to a custom pixel plus server GTM. I compare both routes in how to send Shopify purchases to Meta CAPI. WooCommerce and other platforms have similar plugins with similar trade-offs.

4. Direct API integration

Your developers call the Graph API endpoint for your Pixel (dataset) from your own backend, with an access token. This gives full control and no extra hosting, but you need to handle hashing, retries, batching, consent and API version upgrades yourself. It suits product teams with an in-house backend and a clear owner.

5. CRM and offline events via CAPI

For lead-gen businesses, the valuable event is not the form fill. It is the qualified lead or the closed deal that happens days later in the CRM. Meta retired the old offline conversions API, so these now go through CAPI with action_source set to system_generated or physical_store. You send the stage change from HubSpot, GoHighLevel, Pipedrive or your own system, matched by hashed email, phone and external_id. See Meta offline conversions from your CRM, and my offline conversion tracking page for the Google Ads side.

MethodBest forControlOther platformsRunning cost
Server GTM on StapeMost businesses, multi-channel adsFullGA4, Google Ads, TikTok and moreFree tier, then a monthly plan
CAPI GatewayMeta-only advertisersLowNoHosting fee
Shopify native appSmall Shopify storesLowNoFree
Direct APITeams with developersFullBuild each one yourselfDeveloper time
CRM offline via CAPILead-gen, B2B, long sales cyclesFullPairs with Google Ads offline importsZapier, Make or sGTM

These are not exclusive. A typical B2B client of mine runs server GTM for website events plus CRM events for qualified leads, both going into the same dataset.

Event Match Quality and the customer parameters to send

Event Match Quality (EMQ) is Meta's score from 0 to 10 for how well it can match your events to real Meta accounts. Higher matching means more attributed conversions and better optimisation. It is shown per event in Events Manager. I aim for 8+ on Purchase and 7+ on Lead. If yours is lower, my post on fixing Event Match Quality goes deeper.

The parameters that move the score, roughly in order of impact:

The most common EMQ killer I see is a server event that has the email but no fbc or fbp, because the cookies were never passed from the browser to the server. The second is sending the server's own IP address.

Deduplication with event_id

When both the Pixel and CAPI send an event, Meta needs a way to know they are the same. It uses two fields: event_name and event_id. If both match, within a 48-hour window, Meta keeps one. In the Pixel the field is called eventID; in CAPI it is event_id. Same value, different spelling.

For purchases, the order ID is the obvious choice. For leads and other events, generate a unique ID in the browser (in GTM a simple variable works), push it to the data layer, and send it with both the Pixel tag and the server request. Never use a value that repeats, like a timestamp in seconds or the page URL. I explain the mechanics in event_id deduplication explained and the browser side in how to deduplicate Meta CAPI and browser events.

Check it in Events Manager: open the event, look at the deduplication section, and confirm that most server events show as deduplicated with a browser copy. If you see roughly double the conversions you expect, dedup is broken. Meta Pixel duplicate events covers the other causes.

Moving tracking to the server does not move it outside the law. If your visitor declines marketing cookies, the server should not send their event with personal data to Meta either. In practice that means your consent banner state (from Cookiebot, CookieYes, Usercentrics or similar) has to travel with the event to the server, and the Meta tag only fires when marketing consent is granted.

A few rules I follow on every EU and UK setup:

Consent Mode v2 (ad_user_data, ad_personalization) is a Google concept, but the same banner drives both. I set them up together so Google and Meta respect the same choice.

Testing with Test Events

Never switch CAPI on and hope. In Events Manager, open your dataset and go to Test Events. Copy the test event code (it looks like TEST12345), add it to your CAPI tag or API call, and place a real test order or submit a test lead.

You should see two rows for the same event: one marked Browser and one marked Server, with the server one flagged as deduplicated. Click the server event and check the parameters received: email and phone hashed, fbc and fbp present, the real client IP, value and currency correct. Then remove the test code before going live, because events sent with it are not used for optimisation.

After launch I check three things for a week: the Overview tab shows both connection methods, EMQ is where it should be, and the Diagnostics tab has no warnings about missing parameters or duplicate events.

Common mistakes

If you are not sure which of these you have, a short audit usually finds it within an hour.

How I set it up for you

I set up Meta CAPI as a fixed-scope project, usually inside a wider tracking setup. On Outdoortid I moved Shopify tracking for Google Ads, GA4 and Meta server-side across four projects over 16 months. On Comfybedss, server-side GTM with Consent Mode v2 took tracked orders from 60% to 95%. I also work white-label for agencies like ScalixAI, AdRock and Profitable Sites.

  1. Audit. I check your current Pixel, events, EMQ, dedup and consent, and tell you what is broken.
  2. Plan. We agree the events, the setup method and where the data comes from.
  3. Build. Pixel and CAPI with a shared event_id, full customer parameters and consent gating, usually on server GTM.
  4. Test. Real orders or leads in Test Events, checking dedup, parameters and values.
  5. Hand over. A short report showing what was fixed, plus a week of monitoring.

What I need from you: admin access to Meta Business Manager and the dataset, Google Tag Manager, your website or store admin, and your consent banner. I send a checklist before we start.

Timeline: about 3 hours of work, delivered in one to two days. CRM offline events depend on the CRM, usually a few days.

Price: Meta Pixel and CAPI is a +€400 add-on to my ecommerce setup from €750, with server-side tracking +€400. CRM offline events are quoted per project. See full pricing. If you also run Google Ads, pair this with Google Ads enhanced conversions.

Related guides

Waqas Khokhar
Waqas Khokhar Ex-Google · CEO @ScalixAI
From Whop Whop to Cluely Cluely and other high-growth brands, Abdul Abdul was our go-to tracking specialist

// client reviews

Waqas Khokhar · CEO ScalixAI
client review

Wall of love

Adélaïde De Vos
Adélaïde De Vos3,922 followers
LinkedIn

I had the pleasure to work with Abdul and I can say that he exceeded my expectations. Professional, patient, and clear in his explanations.

Tobias
Tobias7,030 followers
LinkedIn

Abdul set up our tracking for Google Ads and Meta Ads, which helped us get 20%+ more conversions on the same ad spend.

Victor Serban
Victor Serban6,520 followers
LinkedIn

Abdul delivered our first project in just 3 hours. 1.5 years and 30+ projects later, still the best tracking.

Kosta
Kosta8,730 followers
LinkedIn

3 hours to set up. 97%+ accurate data, exactly what we needed. Huge difference.

Donal O'Sullivan
Donal O'Sullivan9,937 followers
LinkedIn

We increased our data accuracy from 50-70% to 95%. Ads are working much better now.

David Friend
David FriendCEO, Profitable Sites
LinkedIn

Kayium set up accurate tracking that helped us scale ads fast and boost conversions by over 25%.

Lalita Sundari
Lalita Sundari7,924 followers
LinkedIn

His strategic mindset and expertise in GTM, GA4, Pixel & Server Side Tracking are invaluable!

Emmett
Emmett7,900 followers
LinkedIn

Abdul really knows his stuff. His tracking knowledge is seriously impressive.

Hasan
Hasan1,200 followers
LinkedIn

Our tracking was a mess. Abdul fixed it in under 24 hours, and everything finally matched.

NIk
NIk4,270 followers
LinkedIn

After Abdul’s setup, our tracking matched our actual sales by 95%+ with our backend CRM.

Meta Conversions API FAQ

Do I still need the Meta Pixel if I use the Conversions API?

Yes, in almost every case. Meta recommends running both. The Pixel captures browser signals like the fbp cookie and on-page behaviour, while CAPI fills the gaps left by ad blockers, Safari limits and closed tabs. You send the same event from both with the same event_id and Meta keeps one.

What is a good Event Match Quality score?

For Purchase, aim for 8 or higher out of 10. For Lead, 7 or higher is solid. Anything under 6 usually means you are not sending hashed email, phone, external_id or the fbc and fbp values from the server.

Is the Conversions API GDPR compliant?

CAPI is a transport, not a consent tool. It is compliant when you only send events and personal data for users who gave marketing consent, hash personal data with SHA-256, and have a lawful basis and a data processing agreement with Meta. Your consent banner state must reach the server.

Which setup method should I pick?

For most businesses I use server-side GTM on Stape, because it handles Meta, GA4 and Google Ads from one place. Shopify stores on a small budget can start with the native integration. CAPI Gateway suits teams that only care about Meta. Direct API is for developers with their own backend.

Why is Meta showing duplicate events after adding CAPI?

Because the browser and server events do not share the same event_id and event_name, or the server event arrives without an event_id at all. Meta can only deduplicate when both match exactly within the dedup window.

Can I send CRM sales and qualified leads to Meta?

Yes. Meta replaced offline event sets with the Conversions API, so CRM outcomes like qualified lead or closed deal are sent as CAPI events with action_source set to system_generated or physical_store, matched by hashed email, phone, external_id and the lead ID where you have it.

How long does a Meta CAPI setup take?

Most of my setups take about 3 hours of work, spread over one or two days so we can check real events in Events Manager. CRM offline events take longer because the CRM side needs mapping.

How much does it cost?

Meta Pixel and Conversions API is a +€400 add-on to my ecommerce setup, and server-side hosting on Stape has a free tier, with paid plans as your traffic grows. Full prices are on the pricing page.

Get Meta CAPI set up properly

Claim your free audit. I will check your Pixel, CAPI, deduplication and match quality and tell you what to fix.

Chat on WhatsAppAvailable now • Replies in ~5 min