If your Shopify store is live and you're spending money on ads, there's a higher-than-you'd-like chance your tracking is lying to you — not a little, sometimes a lot. Attribution gaps have gotten worse, not better, over the past few years: many advertisers now see 50–70% gaps between what platforms report and what actually happened, up from 30–40% in 2021. We've audited dozens of Shopify stores and found meaningfully broken tracking in nearly every one.
The three most expensive tracking mistakes
Purchase event misfiring. This happens when the Meta pixel fires a "Purchase" event too early in the funnel — add to cart, checkout initiation, even a product view. Your Meta dashboard shows a healthy ROAS. Your Shopify revenue tells a different story. You're scaling budget based on a number that isn't real.
Duplicate event firing. When the Meta pixel base code, a Shopify marketing integration, and a third-party app are all trying to track the same event, the same purchase gets reported multiple times. Meta counts it as 2 or 3 conversions. It looks like you're printing money. You're not.
The iOS gap. Meta's pixel alone now misses roughly 30–60% of actual iOS conversions, and stores running pixel-only tracking commonly see overall attribution accuracy drop to around 40% or lower — meaning more than half of real conversions never get reported back to the platform at all.
How to run a quick tracking sanity check
The fastest check is what we call a "purchase event comparison." Pull your Shopify orders for the last 30 days, then count Purchase events in Meta's Events Manager for the same window. If the numbers differ by more than 15% in either direction, something is wrong.
For Meta: if Meta reports more purchases than Shopify, you likely have a duplicate-firing problem. If Meta reports significantly fewer, you have an attribution gap — often iOS-related.
For Google: check Search Console, GA4, and Shopify Analytics for the same period. The numbers will never match perfectly, but they should rhyme — a large discrepancy between GA4 purchase events and actual Shopify orders is a red flag worth chasing down.
Fixing the problem: CAPI setup on Shopify
Meta's Conversions API (CAPI) sends purchase events from your server directly to Meta — bypassing browser limitations, ad blockers, and iOS restrictions entirely. The numbers on what this actually fixes are substantial: pixel-only setups typically run a 60–70% match rate and an Event Match Quality score of 3.5–5.0; adding CAPI alongside the pixel raises match rate to 85–95% and EMQ to 7.5–9.0. Independent analysis has found server-side event sending recovers roughly 38% more attributable conversions and cuts over-reported ROAS by around 31% compared to pixel-only tracking.
Shopify has a native CAPI integration under Marketing → Pixels, but it's limited — it doesn't handle custom events well and produces lower match quality than a properly configured server-side setup. For brands spending meaningfully on Meta, a custom CAPI implementation using Shopify's Customer Events API and a server-side event relay gives you full control over event parameters, deduplication logic, and match quality.
Even with a complete CAPI implementation, expect platform attribution to stay roughly 25–40% incomplete for iOS-heavy audiences — this is a structural limit of post-ATT measurement, not a sign your setup is still broken.
The cost of not fixing this
We've seen brands spending real money on Meta discover, after a tracking audit, that their actual ROAS was a full point lower than their reported ROAS — the gap made up entirely of phantom purchase events from a misconfigured app or duplicate firing. Scaling budget against a reported number that's meaningfully inflated means every additional rupee of spend performs worse than the dashboard suggests, and the misallocation compounds every month it goes uncorrected.
Tracking isn't a technical nicety. It's the foundation of every ad spend decision you make — and in 2026, with attribution gaps wider than they were a few years ago, it needs more attention, not less.
FAQs
How do I know if my Shopify tracking is broken? Run a purchase event comparison — pull Shopify orders for 30 days and compare against Meta's reported Purchase events for the same window. A gap over 15% in either direction signals a real problem.
What's the difference between the Meta pixel and CAPI? The pixel tracks from the browser and is blocked by ad blockers and iOS privacy restrictions; CAPI sends the same events from your server, bypassing those limits. Used together, match rate typically rises from 60–70% to 85–95%.
Will CAPI fully close the iOS attribution gap? No — even with a complete CAPI setup, platform attribution for iOS-heavy audiences typically stays 25–40% incomplete. CAPI narrows the gap substantially; it doesn't eliminate it.
Why does Meta sometimes report more purchases than Shopify shows? Usually duplicate event firing — multiple integrations (pixel, Shopify's native integration, a third-party app) all reporting the same purchase as separate conversions.
Is Shopify's native CAPI integration good enough? It's a reasonable starting point but has real limits — no custom event support and lower match quality than a properly configured server-side relay. Brands spending meaningfully on Meta usually outgrow it.
Our take
Tracking work has almost no glamour and almost all of the leverage — a store with clean attribution makes better decisions on the same ad spend than one without, full stop. If you haven't run a purchase event comparison in the last quarter, that's the fastest way to find out where you stand. For the CAC and LTV numbers this tracking data feeds directly into, see our guides to real CAC vs platform-reported CAC and calculating real D2C LTV. If you want us to audit your setup, talk to us — we'll tell you exactly where the gap is and what it's costing you.
If any of this sounds like your situation, talk to us. We'll tell you exactly where your revenue is leaking and what it would take to fix it. Explore Strategy & Consulting →