Meta Pixel + CAPI Setup in 2026: Track Every Sale Correctly

I’ll be blunt: half the Meta Ads accounts I audit don’t have a creative problem or a budget problem. They have a tracking problem.

Meta shows a good CPA. Shopify shows less revenue. The founder scales the “winner” and nothing grows. Sound familiar?

Here’s how I set up tracking on every client account so Meta optimises on real buyers — not ghosts.

Why this matters more than ever in 2026

iOS privacy changes, ad blockers, and cookie loss mean the browser Pixel alone misses 20–40% of purchases. If Meta can’t see your sales, it can’t find more people like your buyers.

That’s what Conversions API (CAPI) fixes — it sends events from your server, not the browser, so blocked clicks still get counted.

Pixel alone = blind. Pixel + CAPI together = Meta can actually see.

The setup I use (Shopify / D2C)

1. Install both, not one. Use the official Facebook & Instagram app on Shopify or a first-party CAPI integration. Don’t use three different apps sending Purchases — duplicates are worse than gaps.

2. Fire these four events minimum: ViewContent, AddToCart, InitiateCheckout, Purchase. Every event must send value + currency (INR for Indian brands).

3. Deduplicate properly. Pixel and CAPI will both send the same Purchase — that’s expected. They must share the same event_id so Meta merges them into one. Check in Events Manager: if you see double purchases, deduplication is broken.

4. Send customer info for matching. Email, phone, city, postcode — hashed automatically. More parameters = higher match quality. I aim for match quality 7 or above. Below that, I fix it before spending more.

How to test it (5 minutes)

1. Open Events Manager → Test Events.
2. Visit your site, add to cart, go to checkout, place a test order.
3. You should see browser + server events arrive with the same event ID, marked as deduplicated.
4. Check Diagnostics — fix any “low match quality” or “missing value” warnings first.

If a developer set this up for you, still check it yourself. I’ve seen “CAPI connected” setups sending zero Purchase value for months.

3 tracking mistakes I fix every month

Mistake 1: Purchase fires twice. Two apps both sending CAPI. Revenue in Meta is 2x Shopify. Fix: keep one source of truth, remove the other.

Mistake 2: No value sent. Events fire but value is 0 or missing. Meta then optimises for cheap buyers, not high-value ones. Fix: pass order value + currency on every Purchase.

Mistake 3: Retargeting pools are empty. Website custom audiences show <1,000 people because the domain isn’t verified or events never fired. Fix: verify domain, prioritise 8 events for iOS, rebuild audiences after 2 weeks of clean data.

What good tracking unlocks

Once match quality is 7+, three things change:

• Your learning phase actually completes.
• Your scaling stops breaking — Meta finds buyers, not clickers.
• Your reported ROAS finally matches Shopify within 10–15%.

That’s when you can trust the numbers enough to scale.

Takeaway

Don’t spend another ₹50,000 on ads until Events Manager shows clean, deduplicated Purchases with value. Tracking is boring work, but it’s the foundation everything else stands on.

I fix tracking in every audit I do — here’s what’s included. Or message me and I’ll take a look.

FAQ

Do I need both Pixel and Conversions API in 2026?

Yes. Pixel alone misses too many sales after iOS changes. CAPI sends server-side events so Meta still sees purchases from blocked browsers.

What is a good event match quality score?

7 or above out of 10. Below that, send more customer parameters (email, phone, postcode) and check your integration.

Why is Meta revenue different from Shopify?

Usually broken deduplication, missing Purchase values, or different attribution windows. Compare with the same 7-day click window first, then check Events Manager diagnostics.