GA4 Revenue Doesn't Match Shopify? Work Out Whether Tracking Is Actually Wrong

Before changing any tracking, make sure the Shopify and GA4 figures are genuinely comparable.

Check:

• the same date range;
• the same reporting timezone;
• which Shopify report or export you are using;
• which GA4 revenue metric you are using;
• whether refunds and cancellations are included;
• whether test orders are included;
• whether you are comparing all Shopify orders or only a particular sales channel;
• whether tax and shipping are treated consistently;
• whether the currency is the same.

This matters because even two Shopify reports can legitimately differ.

For example, Shopify documents differences between its Sales reports and order exports because refunds, test orders and report logic are not always treated identically.

GA4 also has several ecommerce metrics rather than one universal number called "revenue". Purchase revenue, item revenue and transaction-related metrics are populated from different ecommerce parameters and answer slightly different questions.

So the first step is:

Make sure the two numbers are intended to represent the same thing before treating the difference as a tracking problem.

Shopify is the operational commerce platform. It records orders directly within the store.

GA4 is an analytics system. Its ecommerce reporting depends on ecommerce events such as purchase reaching Google Analytics with the required parameters. Google confirms that ecommerce events are not inferred simply because a transaction exists in the commerce platform. They need to be collected by the measurement implementation.

This creates several legitimate sources of difference.

For example:

• a visitor may block or restrict analytics;
• consent choices may change what GA4 can observe;
• browser extensions may block Google Analytics;
• the platforms may use different timezone or reporting logic;
• refunds or subsequent order changes may be treated differently;
• the population included in the Shopify report may not match the population being compared in GA4.

Shopify explicitly states that differences with Google Analytics can arise from cookies, JavaScript availability, privacy settings, browser extensions, timezone and differences in the underlying tracking mechanisms.

That means perfect equality should not be your starting expectation.

It also means that a fixed percentage difference cannot reliably tell you whether tracking is healthy.

A useful first split is:

How many purchases does Shopify show? versus How many purchases does GA4 show?

Then separately compare revenue.

Why?

Because these patterns mean different things.

Purchase count is low and revenue is low

This makes missing purchase collection more plausible.

The next question is whether particular real orders are absent from GA4.

Purchase count is similar but revenue is wrong

This points more towards:

• incorrect purchase value;
• tax or shipping treatment;
• currency problems;
• refund handling;
• the wrong GA4 revenue metric;
• individual order values being sent incorrectly.

Google's ecommerce model uses event-level parameters such as transaction_id, value and tax, alongside item-level data. Those parameters determine what GA4 can report.

GA4 shows too many purchases

This changes the investigation again.

Possible causes include:

• duplicate purchase events;
• parallel tracking implementations;
• a purchase event being triggered more than once;
• transaction IDs not being handled correctly.

That is fundamentally different from missing measurement.

Aggregate figures tell you that the systems differ.

Individual transactions tell you how they differ.

Where possible, compare Shopify orders with the transactions recorded in GA4.

A useful reconciliation process is:

1. Choose a defined date range.
2. Establish the Shopify order population being used as the reference.
3. Compare purchase counts.
4. Extract or inspect GA4 transaction IDs.
5. Match individual Shopify orders against GA4.
6. Identify which transactions are missing.
7. Identify any duplicate GA4 transactions.
8. Compare the values of matched orders.
9. Look for patterns among the mismatches.

This produces a much more useful picture than simply saying:

"GA4 is 14% lower than Shopify."

For example, you may discover that:

• almost every order exists, but shipping is treated differently;
• a specific checkout route is consistently missing;
• purchases disappeared after a known site change;
• only consent-restricted users appear to be missing;
• several orders have been counted twice.

Each of those points towards a different fix.

GA4's transaction_id is intended to uniquely identify a transaction.

Google uses matching transaction IDs to deduplicate repeated purchase events in web streams, so each genuine order should have a unique ID. Reusing the same ID across different real orders can cause undercounting, while sending an empty transaction ID can also create serious deduplication problems.

That makes the transaction ID useful in two ways.

It helps identify the real order

If Shopify order 12345 can be associated with transaction 12345 in GA4, you can investigate actual orders rather than aggregate totals.

It helps protect against repeated purchase events

If the same purchase event reaches GA4 more than once with the same transaction ID, GA4 can deduplicate it.

However:

Transaction-ID deduplication should not be treated as permission for the website to fire purchases repeatedly.

A robust implementation should still aim to emit the purchase correctly and once.

This is probably the most common direction of discrepancy.

Possible investigation areas include:

Purchases never reaching GA4

GA4 ecommerce reporting relies on ecommerce events reaching Analytics.

Google states that ecommerce data appears when the relevant ecommerce events are sent, including purchase. On Shopify, some ecommerce events can be collected automatically when GA4 is configured through the supported Shopify setup.

If some purchases never reach GA4, investigate why.

Consent and browser restrictions

Some customers may complete purchases without being observed in GA4 in the same way as fully measurable users.

Shopify specifically identifies privacy preferences, cookies, JavaScript and browser extensions as reasons its numbers can differ from third-party analytics tools.

A lower GA4 total can therefore be partly expected without implying an implementation fault.

A checkout or tracking change

If the discrepancy became materially worse on a particular date, compare that date with:

• Shopify changes;
• checkout changes;
• consent/CMP deployments;
• theme changes;
• Google tag or GTM changes;
• ecommerce integration changes.

A stable long-term gap and an abrupt new gap are very different diagnostic situations.

Purchase event parameter problems

If the purchase event exists but required ecommerce data is malformed or missing, reports can be incomplete.

Google's current troubleshooting guidance highlights parameters such as currency, transaction_id, item identifiers and price as important to ecommerce revenue reporting.

This generally deserves closer investigation because GA4 should not be creating genuine store orders that do not exist.

Possible explanations include:

• purchase event firing twice;
• duplicate integrations;
• GTM plus another Shopify integration both measuring the purchase;
• test transactions included in the GA4 comparison;
• wrong transaction values;
• populations or time periods not actually being comparable.

A particularly useful check is:

Do the additional GA4 purchases have transaction IDs that correspond to genuine Shopify orders?

If they do not, the implementation deserves investigation.

If the same real order appears repeatedly, duplication becomes more likely.

This naturally connects to the separate MeasureNest guide on duplicate GA4 conversions and purchases.

Suppose Shopify shows:

• 100 orders

and GA4 also shows:

• approximately 100 purchases.

That does not prove the implementation is correct.

Individual purchase values can still be wrong.

Useful areas to check include:

• purchase value;
• currency;
• tax;
• shipping;
• discounts;
• item-level price and quantity;
• refund handling.

Google distinguishes event-level transaction data from item-level ecommerce data, which is one reason different GA4 metrics can give different views of revenue.

This is why the investigation should move beyond:

"How many purchase events exist?"

to:

"Do those purchase events represent the correct orders and values?"

You may see advice suggesting that a certain percentage difference between Shopify and GA4 is normal.

I would not use a fixed percentage as the primary health check.

The appropriate difference depends on factors including:

• consent behaviour;
• audience/browser mix;
• measurement implementation;
• report definitions;
• refunds;
• order types;
• the exact metrics being compared.

A small discrepancy can still hide a systematic problem.

A larger discrepancy can sometimes have an explainable measurement cause.

The more useful question is:

Can you explain the pattern?

If you can account for the difference at order level and the remaining gap is consistent with how the systems collect data, it may not represent a tracking defect.

If you cannot explain it, or the pattern suddenly changes, it deserves further investigation.