Meta Ads Attribution: Why Facebook's Numbers Don't Match Your Revenue

Meta says it drove 40 purchases this week. Shopify says 25. Neither number is wrong, exactly — they're measuring different things, on different attribution windows, using different data. Here's what's actually happening.

What Meta Ads is actually counting

Meta's reported conversions come from its own attribution window — by default, a mix of 7-day click and 1-day view attribution, meaning Meta will credit itself for a purchase that happens up to 7 days after someone clicked an ad, or up to a day after they simply saw one without clicking. That view-through component alone explains a big chunk of the mismatch: Meta is claiming credit for people who saw an ad and happened to convert later, through any channel, without ever clicking through from Meta.

Your store's own order data, by contrast, usually only knows about the last touchpoint that was actually tagged — the last UTM-tagged link or the last platform click ID present at checkout. Two completely different counting methods, applied to the same set of customers, will never produce the same number.

A concrete example of the gap

Why this mismatch actually matters for budget decisions

• Judging Meta purely by your store's last-click numbers can make it look like it's underperforming, when it's actually generating a meaningful share of view-through demand your other reporting simply doesn't credit it for.
• Judging your other channels purely by Meta's self-reported numbers has the opposite problem — Meta will happily claim credit for conversions that a different channel's tagging shows as the actual last touch.
• Neither number alone tells you what's true. What you actually want is the full sequence — see customer journey analytics.

What actually closes the gap

1. Consistent UTM tagging on every Meta campaign

Meta's own click ID (fbclid) helps within Meta's ecosystem, but a consistent UTM tagging convention is what lets a downstream analytics or attribution tool compare Meta against every other channel on equal footing.

2. Server-side event tracking

Browser-based Pixel tracking loses events to ad blockers, Safari's Intelligent Tracking Prevention, and iOS privacy settings — all of which quietly undercount what Meta can see in the first place, before attribution windows even enter the picture. See Meta Conversions API vs. Pixel for how that gap gets closed.

3. Looking at the full journey, not either platform's own number

The only way to actually know whether Meta's view-through claims are reasonable is to see the whole path a customer took — what they saw, what they clicked, and what happened last — in one place, rather than trusting whichever platform's dashboard you happen to have open.