The 30% of purchases Meta never saw
A Kochi skincare brand counted 1,000 orders a month in Shopify, but Meta Ads Manager reported only about 700 purchases.
Many buyers used iPhones with tracking limits or browsers that blocked the pixel. Meta was optimising on 70% of the truth.
After switching on the Conversions API through Shopify’s Meta channel, reported purchases rose to about 940 and cost per purchase in Ads Manager fell, because Meta could finally learn from almost all buyers.
Illustrative example based on a common pattern in Kerala e-commerce accounts. Numbers rounded.
What the Conversions API is
The pixel runs in the browser and sends events when the page loads or a button is clicked. CAPI runs on a server (your store platform, a gateway or your CRM) and sends the same events after they happen.
Meta matches CAPI events to people using details like hashed email and phone, then removes duplicates with the event_id. CAPI also lets you send offline events, such as a lead that became a sale in your CRM.
Pixel (browser) + CAPI (server), same event_id → one event, better coverage
CAPI readiness check
Tick what is already true for your Meta tracking.
0 of 5 done (0%)
Big gaps. Start with the first unticked item; each one is a quick win.
Stuck on one? Join the community and post it for doubt-clearing.
Pixel vs Conversions API
| Pixel | Conversions API |
|---|---|
| Runs in the visitor’s browser | Runs on your server, platform or CRM |
| Blocked by some browsers and ad blockers | Not affected by browser blocking |
| Sees website actions only | Can also send offline and CRM events |
| Easy to install | Easiest through a partner integration |
How experienced marketers use CAPI
1. Recover lost conversions
Stores and lead businesses typically see more conversions reported after adding CAPI, which improves optimisation.
2. Optimise for real customers
Send qualified leads or sales from the CRM so Meta finds people who buy, not just people who fill forms.
3. Prepare for privacy changes
Server-side data keeps measurement steadier as browsers tighten tracking.
What good looks like
| Business type | Starting rule | Why |
|---|---|---|
| Event Match Quality | 6+ good, 8+ strong | For the main conversion event. |
| Deduplication | Most events deduplicated | Check in Events Manager Overview. |
| Setup time with a partner | 15–60 minutes | Shopify and WooCommerce are fastest. |
When the number lies
- Double counting
- Without a shared event_id, pixel and CAPI events are counted twice and results look better than they are.
- Over-reporting from bad mapping
- Sending page views as leads through CAPI inflates results just like a broken pixel.
Mistakes to avoid
Running two CAPI integrations
Duplicate events and confused reporting.
No consent for customer data
Privacy risk under India’s DPDP Act.
Turning off the pixel after adding CAPI
You lose browser signals Meta uses for matching.
Related terms
Questions people ask about the Conversions API
What is the Meta Conversions API?
A way to send conversion events to Meta from your server or CRM instead of only from the browser pixel.
Do I need CAPI if I have the pixel?
Meta recommends both. CAPI recovers events the pixel misses and adds offline events.
Is CAPI hard to set up?
Not with a partner integration (Shopify, WooCommerce, many CRMs). Custom sites need a gateway or server-side GTM.
What is the CAPI Gateway?
A Meta-supported option that runs a small cloud server to send your pixel events server-side without custom code.
Put it into practice
- SOP 326: Set Up the Meta Conversions API (CAPI) Without a Developer →
- SOP 005: Install the Meta Pixel on Your Website →
Prefer to talk first? Book a free counselling call.