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's purchase numbers are a claim, not a count. Meta attributes a purchase to an ad if the buyer clicked within the click window or, by default, viewed an ad within a day. It also models conversions it can't observe directly. The result can be higher or lower than your actual orders, and both directions can be legitimate or broken.

If Meta reports more purchases than Shopify took, either duplicate Purchase events are firing, or view-through attribution is claiming orders that came from elsewhere. If Meta reports far fewer, the Purchase event may be failing on some checkout paths, or the Conversions API and Pixel aren't covering all orders.

This analyzer compares Shopify's paid orders and revenue with Meta's purchases and purchase value over the same period, and classifies the gap so you know which story the numbers tell.

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. Upload both exports for the same dates

    Shopify orders (total, financial status, date) and a Meta Ads export with Purchases and purchase conversion value, plus date and currency if available.

  2. We align periods and currencies

    Different date ranges or currencies are flagged before the comparison, because they explain many gaps on their own.

  3. We compare count and value separately

    Purchases against paid orders, and purchase value against gross revenue, are each classified as normal loss, under-reporting, broken, an exact match to check, or over-reporting.

Common causes and fixes

Duplicate Purchase events
A theme pixel plus an app, or a Pixel event and a Conversions API event without a shared event_id, count one order twice. Use the Meta Pixel + CAPI Dedup Checker.
View-through attribution
Meta's default includes 1-day view. Orders from other channels by people who saw an ad are claimed. Compare with 7-day click only to see the difference.
Purchase missing on express checkout
Shop Pay, Apple Pay and PayPal flows sometimes bypass the page where the Pixel fires. Make sure the Conversions API covers server-side order events.
Value includes tax and shipping
If purchase value runs above Shopify revenue, check what's included in the value parameter and whether it's sent in the store currency.

Frequently asked questions

Is it normal for Meta to report fewer purchases than Shopify?
Yes. Not every order comes from Meta, and consent and browser limits reduce what Meta can observe. Record your baseline gap and investigate sudden changes.
Meta reports more purchases than Shopify. Is my Pixel broken?
Possibly duplicated, or view-through attribution is claiming orders from other channels. Check deduplication first.
Should I compare with attribution settings changed?
Exporting with 7-day click only removes view-through claims and gives a more conservative comparison.
Does it use order IDs?
No. Meta's ad exports don't include order IDs, so the comparison works on totals.
Is my data stored?
No. Exports are parsed for the result and findings expire after 7 days.

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