Clarvivo

Free tool by Clarvivo · no login

Compare Meta purchases with the orders your store actually took

Upload matching Shopify and Meta exports. We use paid orders as financial truth and explain whether Meta's gap is normal, missing or impossible.

Shopify orders and Meta reported purchases

Export both over the same date range. Shopify is financial truth; Meta is the claimed measurement.

This tool answers: Is Meta over-reporting purchases relative to actual orders?

Enable JavaScript to run the check — the diagnosis itself is free and needs no account.

Why this happens

Meta reports attributed conversions, while Shopify records completed orders. They should not match exactly, but Meta reporting more purchases than the store is a tracking problem, not an attribution window.

A stable shortfall can be expected; a sudden or extreme shift needs a clear next test.

Next checks

These answer the questions this one tends to raise.

How this check works

So you can trust the result — and your developer can verify it.

  1. Normalise both exports

    We parse paid Shopify orders and the conversion, value, currency and date columns Meta exports.

  2. Compare counts and value

    The result separates too many events from missing events and incorrect monetary values.

Common causes and fixes

Pixel plus CAPI duplication
Different browser and server event IDs can make Meta count one purchase twice.
Different date windows
A range or timezone mismatch looks exactly like tracking loss until it is corrected.

Frequently asked questions

Should Meta equal Shopify?
No. Consent, blockers and attribution windows normally create a gap; over-reporting is the critical signal.
What export should I use?
Include Purchases, purchase conversion value, date and currency if Meta offers them.

Use orders, not claimed purchases, as revenue truth.

Clarvivo keeps platform claims beside payments so anomalous gaps are visible before budget changes.

Reconcile Meta with real revenue

What this tool reads, and what it keeps