GA4 vs Shopify and ad platforms: explain revenue differences

Reconcile GA4, Shopify and advertising reports using clear revenue definitions, refund treatment, transaction coverage and a practical comparison checklist.

Your question

Why do Shopify, GA4 and advertising reports show different revenue?

Put the thinking to work
Ads Agent ↗
THE SHORT ANSWER

Two reports can differ because they observe different interactions or apply different definitions. Before comparing GA4 with a marketing platform, align the business question and inspect scope, timing, value and attribution settings.

Compare definitions before comparing totals

Use this reconciliation checklist with the exact reports open. Record the configuration and a small sample of transaction IDs in your own secure workspace; do not upload customer data to this website.

CheckStore reportGA4 / ad-platform report
Period and timezoneWhich order date and timezone define the selection?Does the report use the same dates or assign results to an interaction date?
Revenue definitionRecord discounts, tax, shipping and cancellations.Identify the exact metric and the value sent in purchase events.
Refunds and currencyAre refunds already deducted? Which exchange-rate date is used?Were matching refund events received and was currency consistent?
Order and event coverageSelect valid orders and note test, cancelled or offline orders.Inspect missing or duplicate transaction IDs, consent and collection errors.
Channel creditAn order total describes sales under the report’s definition.Record model, window and scope; do not sum overlapping platform claims.

Illustrative reconciliation: €100,000 in one report and €91,000 in another leaves €9,000 to explain. Classify differences by definition, timing and coverage. Do not assign the entire gap to consent or lost sales without transaction-level evidence.

Start with the Shopify order definition

Open the exact Shopify sales report and write down which revenue column you are using. Compare it with the exact GA4 metric, not a dashboard label that simply says revenue. Refunds already deducted from a source must not be subtracted again. Keep a reconciliation worksheet with the reporting configuration and the remaining unexplained amount.

Then review tracking coverage and recent platform changes. Shopify notes that session measurement changes can affect sessions and conversion rates without proving a change in orders or customer behaviour. A falling conversion percentage therefore needs its denominator checked before it becomes a CRO hypothesis.

Source: Shopify: sales report definitions ↗ · Google Analytics: metric definitions ↗ · Shopify: analytics differences ↗

Check the scope first

Google distinguishes user-, session- and event-scoped traffic dimensions. The reporting attribution choice affects event-scoped credit; it does not simply rewrite every user- or session-scoped acquisition dimension. A label saying GA4 is therefore insufficient to describe a query.

Write down the actual dimension and metric used in each report. A channel-session table and an event-attribution table may both be correct while answering different questions. Compare like with like before looking for a tracking failure.

Source: Google Analytics: traffic-source scopes ↗

Create a short comparison contract

Use the same closed period, timezone and currency. Specify the purchase event, included accounts, exclusions and whether revenue includes tax, shipping, discounts, cancellations and returns. Record the conversion timestamp basis and the relevant attribution windows.

Some systems may still observe different interactions after these choices are aligned. Document the difference rather than forcing agreement. A reconciliation is useful when it explains the numbers, not when it merely makes the totals match.

Investigate before changing the budget

Check tagging, channel mapping, missing events and data freshness. Follow a small set of suitable transactions or source records where permitted. Distinguish a known definitional difference from an unexplained gap.

Keep native platform reporting visible for the decisions it supports, while naming the reference used for cross-channel discussion. Do not add multiple platforms’ assigned revenue and label the total as business revenue.

ILLUSTRATIVE EXAMPLE

The same reporting label, different questions

A team sees a low paid-social figure in a session report and a higher value in an ad platform. Its first task is to inspect period, mapping, conversion event and attribution scope. The discrepancy itself is not enough evidence to conclude that the campaign is unprofitable.

Use this at work

  1. Record dimension, metric and reporting scope.
  2. Align period, currency and revenue definition.
  3. Check tagging, freshness and source coverage.
  4. Label the remaining gap as explained or still under investigation.

Reference material

Platform guidance checked 3 October 2026. Examples and working checklists are Faccelerate editorial illustrations.

Questions about this approach?

Does using the same lookback window make reports identical?

No. Matching a window does not ensure that the systems observe the same interactions or use the same value definitions.