1. Make the reports comparable
Choose a closed reporting period. Match time zone, store scope, currency and the treatment of tax, shipping, discounts and refunds. Record whether the comparison concerns all store orders or only orders in the measured online journey. A comparison made from mismatched definitions cannot isolate a tracking problem.
2. Quantify the pattern
Calculate the difference using the agreed revenue scope. Split the result by date, market, device or checkout route where useful. A sudden change after a release suggests a different investigation from a persistent gap associated with collection limits. Check transaction counts and values separately.
3. Inspect individual orders
Select a bounded sample, including an expected successful event, a missing transaction and any suspected duplicate. Keep order identifiers in the private investigation record. Check whether the event fired, whether it reached the intended property, and whether the value and currency matched the agreed definition.
4. Classify the cause
- Definition: revenue scope, dates, refunds or currency.
- Coverage: orders outside the measured journey or unavailable collection.
- Implementation: missing, duplicate or incorrectly parameterized events.
- Destination: wrong property, stream or configuration.
- Change: checkout, consent, theme or integration release.
5. Fix one cause and retest
For an implementation issue, write the expected behavior before changing tags. Re-run the affected journey, including refresh and failure scenarios. Compare a later period using the same definitions. Keep a note if historical figures cannot be corrected by the release.
6. Report what remains uncertain
Show the original gap, diagnosed causes, changes and residual difference. Shopify’s own discrepancy guidance recognizes that reporting systems differ. The target is a useful, explainable measurement setup, not a claim that browser analytics will reproduce every finance total exactly. Escalate unresolved value definitions to the store and finance owners.
Separate expected differences from collection faults
Build a reconciliation using the same reporting period, time zone, currency and revenue basis. Then classify differences: known scope differences, missing transactions, duplicate transactions and inconsistent values. Keeping those categories separate prevents a legitimate definition difference from being treated as a tracking failure, or a genuine failure from being dismissed as normal variation.
An illustrative investigation might find that the store report includes shipping while the analytics purchase value does not. Aligning that definition explains part of the gap, but it does not rule out missing events. Follow a small sample of transaction identifiers through the available collection records inside the business’s controlled tools. Record the size and likely cause of the unresolved portion. Fix one identified issue, retest and compare on the same basis before declaring the whole discrepancy resolved.
- Use a written reconciliation table with matched dates and definitions.
- Test suspected causes against individual transactions where available.
- Keep unresolved differences visible and avoid changing several variables at once.
Get help investigating measurement gaps →
Frequently asked questions
Why does measured revenue differ from the store records?
Investigate a GA4 revenue gap by aligning definitions first, then tracing a sample of orders through collection. A difference between analytics and a store report can come from both expected scope differences and actual implementation faults.
Should we compare headline revenue totals first?
First align period, time zone, currency and revenue definition. A mismatch in scope can create an apparent fault before any event is inspected.
How do we investigate the remaining gap?
Trace a defined sample of orders and classify differences, such as missing or duplicate collection. Change one cause and retest before declaring the issue resolved.
Sources and further reading
Primary material for the concepts discussed here. Our practical checklists and illustrative examples are editorial recommendations. Source links open in a new tab.