TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

READING ROOM › SYMPTOM FILES › SYM-074

SYMPTOM FILE SYM-074 FILED 13 NOV 2026 · REVISED 19 NOV 2026

Tools for finding the gap between GA4 and Shopify revenue: what each one can and can't tell you.

ALSO FILED AS
  • “best tools for fixing GA4 revenue higher than Shopify discrepancies”
  • “tools to reconcile GA4 and Shopify revenue”
  • “how to find GA4 Shopify revenue discrepancy”
  • “GA4 Shopify reconciliation tool”
  • “match GA4 transactions to Shopify orders”
  • “GA4 Shopify order by order comparison”

Baris Asa, tracking consultant, London · Last checked: November 2026

No tool fixes a gap between GA4 and Shopify revenue on its own: the fix is a change to whatever sends the purchase. Tools find the cause. Two you already have do most of the work: Shopify’s orders export and GA4’s Transactions report, matched order by order, show which orders are extra, missing or wrongly priced. Tag Assistant, GA4 DebugView, the browser’s Network panel and the Shopify Pixel Helper then show which sender caused it.

I have no partnership, affiliate or commission arrangement with any tool on this page.

This note is about the tools. Whether your gap is normal at all (refunds, tax, time zones) is in GA4 revenue higher than Shopify. Read that first if you haven’t compared purchase counts yet.

Which tool answers which question?

ToolWhat it tells youWhat it can’t tell you
Shopify orders exportEvery order, its number and totalWhat GA4 received
GA4 Transactions reportGA4 revenue per order ID, and (not set)Which tag sent it
Tag Assistant, GTM PreviewWhich Google tags fired on a pageAnything inside a Shopify custom pixel
GA4 DebugViewWhat GA4 received from your test deviceOther visitors, or data over 30 minutes old
Browser Network panelEvery request the browser sentServer-side senders, or whether GA4 kept it
Shopify Pixel HelperEvents one custom pixel receivedThe other pixels, and GA4
BigQuery exportEvery purchase event, joinable to ordersAnything before you linked it
Tracking apps (Littledata, Elevar, Analyzify)What they sent, in their own reportsWhy your old data is wrong

The order matters. Find which orders differ before you look for which sender. A sender hunt without the order list is guesswork.

Step 1: which orders differ? Shopify’s export and GA4’s Transactions report

Shopify. Orders, Export, then choose the date range of one closed week (a full week that ended at least two days ago; Google says GA4 can take 24 to 48 hours to process). Larger exports, and exports by date, arrive by email. The Name column is the order number as it shows in your admin, and Total is the full order cost. Subtotal, shipping and taxes have their own columns. A multi-item order takes several rows, with most fields blank after the first. Keep one row per order.

GA4. Reports, Monetization, Transactions: one row per Transaction ID, with ecommerce purchases and purchase revenue. Set the same week. Export it as a spreadsheet. If your reports have been customised and it’s missing, it is in the Library, or you can build it in Explore: a free-form table with Transaction ID as the row and Ecommerce purchases and Purchase revenue as values. On a busy property a long date range can roll rows into (other); keep to a week (R-502 ).

The join only works if GA4’s Transaction ID is a value the export carries, such as the Name column. Setting that up, with the other decisions that keep the match clean, is the reconciliation chapter of the field manual.

Match them. Put both in one sheet and look up each Shopify order in the GA4 list. Your tag may send the order number (#1001), Shopify’s longer order ID, or something else. Find one test order in both to see which, then match on that. Five patterns come out:

  1. An order in GA4 twice, or a (not set) row with many purchases: the purchase fires twice (F-101 ). GA4 drops a second purchase with the same transaction ID, so the copy that gets through usually has no ID or a different one.
  2. IDs in GA4 that aren’t orders. A second sender using its own ID, or test orders. Shopify leaves test orders out of its sales reports.
  3. Same orders, GA4 revenue 100 times higher, or higher by tax and shipping, or wrong on foreign-currency orders: the amount is built wrongly (F-302 ).
  4. Orders in Shopify, not in GA4. Spread evenly, it’s usually consent and blockers (F-201 ). Concentrated on one payment method or from one date, it’s a lost purchase: see GA4 purchase event not firing.
  5. Everything matches but the week’s total. Refunds: Shopify subtracts them, GA4 only does if it gets a refund event. See GA4 revenue after refunds.
ORDERSHOPIFY TOTALGA4 REVENUEREADING
#4410£82.00£82.00match
#4411£56.50£5,650.00100x, F-302
#4412£119.00not in GA4missing
(not set)none£3,904.0041 extra purchases, F-101
#4413£74.00£74.00match
ORDER MATCH · one week, five rows of 412 · worked example, illustrative figures, not a client account

One spreadsheet, three different faults. The (not set) row is the biggest: 41 purchases sent with no ID. The second sender’s copies all land there. The fix starts with finding that sender.

Step 2: which sender? Tag Assistant, DebugView, the Network panel and the Pixel Helper

Place one test order with all four open. Each sees a different slice. You need at least two, because none of them sees everything.

Tag Assistant and GTM Preview (tagassistant.google.com) show which Google tags fired on each page and with what values. They are the quickest way to spot a GTM purchase tag with two triggers. Their blind spot on Shopify is checkout: a purchase sent from a custom pixel runs in a sandbox, and Shopify says Tag Assistant’s Troubleshoot tag feature doesn’t detect Google tags in one. More on that sandbox in GTM in a Shopify custom pixel.

GA4 DebugView (Admin, Data display, DebugView) shows the events GA4 received from a device in debug mode: Tag Assistant turns it on for your browser, or set debug_mode on the GA4 tag while testing. Count the purchase events for your test order and click each to read its transaction_id and value. It only shows debug devices and the last 30 minutes. Google says events won’t appear if consent mode is on and you haven’t consented to analytics cookies, so accept the banner first. Empty when it shouldn’t be? See GA4 DebugView is empty.

The browser’s Network panel (right-click, Inspect, Network) sees every request the browser sends, whichever tool sent it. Filter for collect and look at the order confirmation page. Two GA4 purchase requests for one order means two senders. Each request shows the measurement ID it went to (the G- code), which catches a second property too. It includes custom pixels and app pixels alongside GTM. It can’t see purchases sent from a server: tracking apps that send orders from their own servers, server-side GTM, or the Measurement Protocol. If step 1 shows extra purchases and the browser sends only one, check the server-side GA4 settings in your installed apps, and the Measurement Protocol API secrets under GA4 Admin, Data streams. It also can’t tell you whether GA4 kept the request.

The Shopify Pixel Helper opens from Settings, Customer events: select the custom pixel, then Test. It shows the events that pixel received and whether its code ran (green dot) or threw an error (red dot). It tests one pixel at a time, clears on every page, and Shopify says it doesn’t work on headless stores. Use it to confirm which pixel is the second sender once the Network panel shows there are two.

Also check GA4 Admin, Events, Create event. A rule there that outputs purchase from another event (say, a thank-you page view) makes a second purchase that no tag on the page shows you. Which apps send what on Shopify, and where they double up, is in Shopify tracking apps: what each one sends.

Step 3: when the spreadsheet is too big, BigQuery

GA4’s BigQuery export gives you every purchase event, with ecommerce.transaction_id and ecommerce.purchase_revenue on each. Load the Shopify orders next to it and the step 1 match becomes a query you can rerun every week. Google describes the daily export as raw, unsampled event data. Standard properties can export up to 1 million events a day, and the BigQuery sandbox has limits; past them, BigQuery bills the project.

What it can’t tell you: anything from before you linked it. Google says data starts flowing within 24 hours of linking, and its help describes no backfill; in the properties I’ve linked, there was no earlier history to query. So link it before you need it. Exports often don’t match GA4 reports exactly, and that is expected; see GA4 BigQuery export doesn’t match reports.

If you can compare a week by hand, the spreadsheet does the same job.

Do tracking apps like Littledata, Elevar or Analyzify fix the gap?

They replace the thing that sends purchases. That fixes the gap only if your current sender was the fault and every other sender is switched off. Installed next to an existing GA4 tag, a tracking app is a second sender, and the gap gets wider (F-101 ).

Their own reports are useful but limited. Elevar’s Channel Accuracy Report compares Shopify orders with the events Elevar sent to each destination and the responses it got back. That shows whether Elevar sent every order. It doesn’t show what GA4 recorded, or whether another tag sent the same order too. Check GA4’s Transactions report as well.

How the apps compare is in Elevar alternatives for Shopify tracking and Elevar vs Littledata. Diagnose first: a fault in the setup moves with you to any app.

What about dashboards that show Shopify’s own revenue?

Any report that reads revenue straight from Shopify orders will agree with Shopify, because it is Shopify’s number. That’s useful for reporting. It tells you nothing about why GA4 differs, and it doesn’t change what GA4, Google Ads or Meta receive. Bidding still runs on what the ad platforms receive.

When you need a person rather than a tool

When step 1 shows a pattern and you can’t find the sender, or there are several senders and nobody knows who installed them. I do that work as a GA4 reconciliation: one closed week, order by order, every sender named, the duplicate switched off, and the same spreadsheet left with you to recheck it.

Common questions

What are the best tools for fixing GA4 revenue higher than Shopify?

No tool fixes it by itself; the fix is a change to whatever sends the purchase. The tools find the cause. Start with two you already have: Shopify’s orders export and GA4’s Transactions report, matched order by order. Then use Tag Assistant or GTM Preview, GA4 DebugView, the browser’s Network panel and the Shopify Pixel Helper on one test order to see which sender is wrong. BigQuery does the same match for thousands of orders.

Can a Shopify tracking app like Littledata or Elevar fix the gap?

It can replace the thing sending purchases, which fixes the gap only if that sender was the fault and every other sender is switched off. Installed next to an existing GA4 tag, it adds a second sender and widens the gap. Diagnose first, then decide whether a new sender is needed.

Does Elevar’s Channel Accuracy Report show whether GA4 matches Shopify?

Not quite. Elevar says the report compares Shopify orders with the events Elevar sent to each destination and the responses it got back. It shows whether Elevar sent every order, not what GA4 recorded or whether another tag also sent the same order. Check GA4’s own Transactions report as well.

Do I need BigQuery to reconcile GA4 with Shopify?

Not for a small store. A week of Shopify’s orders export against GA4’s Transactions report, in a spreadsheet, finds the extra or missing orders. BigQuery earns its place when there are too many orders to compare by hand or you want the check to run every week. Standard properties can export up to 1 million events a day, and the BigQuery sandbox has limits.

Why can’t Tag Assistant see my GA4 purchase on Shopify checkout?

If the purchase is sent from a Shopify custom pixel, it runs in a sandbox, and Shopify says Tag Assistant’s Troubleshoot tag feature doesn’t detect Google tags there. Use the Shopify Pixel Helper and the browser’s Network panel for that sender instead.

Which GA4 report shows purchases by order number?

The Transactions report under Reports, Monetization: one row per transaction ID, with ecommerce purchases and purchase revenue. Purchases with no ID show as (not set). If someone has customised your reports and it’s missing, it is in the Library, or you can build the same table in a free-form exploration.

Sources

All read on 13 November 2026.

← back to the reading room