wesaw
FRGet started

Why your Shopify sales don't show up in Meta

Your store and Meta report different numbers. Start by separating delivery from attribution, then inspect the evidence for individual orders before diagnosing a tracking failure.

A gap between Shopify orders and Meta's advertising reports does not by itself prove missing events. The reports can cover different populations and attribution windows. For a specific order, inspect consent, browser evidence and the server delivery response to distinguish an excluded event, a failed delivery and an attribution difference.

Is the sale missing, or just attributed elsewhere?

Check which figures you are comparing. Shopify orders, events received by a Meta dataset and purchases attributed in Ads Manager are different populations. A lower advertising total does not prove delivery loss, and equal totals do not prove that every order arrived.

Align the time period, time zone, event type and report scope first. Then inspect individual eligible orders and their recorded destination responses. An accepted delivery remains distinct from advertising attribution.

Was the reporting script blocked?

This is the most common cause and the least visible one. A blocker refuses the request that reports the sale, so the order completes normally and Meta never hears about it. Nothing appears in your store's admin, because from your store's point of view nothing went wrong.

Worth knowing: this happens without anyone installing an extension. Firefox enables tracking protection by default and Safari restricts what a browser-side script can retain, so a meaningful share of the loss comes from browsers behaving as shipped.

Did the shopper decline tracking?

Then the sale is legitimately outside the reporting, and no tool should recover it. A refusal removes data rather than hiding it. This is the one cause on this page with no fix, and any product promising to close it is describing something you should not buy.

Did the click information survive to the checkout?

A missing click identifier can remove a useful matching signal. Inspect whether it survived redirects and checkout, but do not conclude that attribution is impossible: Meta may use other available signals. The receipt shows signal presence, not the destination's attribution decision.

What actually closes the gap

  1. Report the sale from your server instead of the browser, so a blocker never sits in the path. The order is already on your server; nothing new is collected.
  2. Send the details the order already contains. A browser knows four things about the buyer; the order knows a name, a city, a postcode and often a phone number.
  3. Keep the click identifier from landing to checkout, rather than hoping a cookie survives.
  4. Keep the pixel running alongside it, matched on a shared event identifier, so the sale is counted once and not twice.

Sources

  • Firefox enables Enhanced Tracking Protection by default for all users, blocking known trackers with no extension installed.Mozilla
  • On our own test store, reporting server-side raised the match parameters sent with each purchase from 4 to 14, and Meta's Event Match Quality to 8.0 out of 10, read on 18 August 2026. The same score read 9.3 on 21 August, once the browser half was reporting as well.wesaw, own test store

The terms on this page

What wesaw does about it

Last reviewed: