by Trivas.aiIf you migrated from Universal Analytics and your revenue reports still look off, you're not alone. GA4 runs on an event-based model, not the session-based structure UA used, so the old ecommerce reports you built your Monday morning routine around just don't carry over. Nothing transfers automatically.
Here's the part most teams miss: GA4 needs explicit ecommerce events, things like view_item, add_to_cart, and purchase, to populate anything in the revenue and product reports. No events, no data. It's not inferring purchases from pageviews the way some assume.
And a default GA4 install through Shopify's Google & YouTube sales channel doesn't hand you full ecommerce tracking out of the box. It captures basic events, but parameters like item_id, price, and coupon often aren't included unless you've configured things further. That gap is exactly where GA4 ecommerce events setup goes wrong for most DTC brands.
The stakes are straightforward. Without correct setup, you'll see traffic numbers that look fine, sessions, users, landing pages, all populated. But revenue attribution is broken or missing entirely. You're flying with a dashboard that looks complete and isn't.
GA4's ecommerce model is built around a specific set of events: view_item_list, view_item, add_to_cart, begin_checkout, add_payment_info, purchase, and refund. Each one maps to a stage in the buying journey, and together they're what populate GA4's ecommerce and monetization reports.
Some events fire automatically. page_view and session_start show up the moment GA4 is installed, no configuration needed. But the ecommerce events above are "recommended events," meaning GA4 knows what to do with them if you send them, but it won't generate them on its own. That distinction trips people up constantly: they assume GA4 tracking is "done" because Realtime shows activity, when really only the basic events are firing.
The purchase event is the one that matters most, and it's also the strictest. It needs a transaction_id, a value, a currency, and an items array listing what was bought. Skip any one of these and the event might still fire, but the revenue won't show up where you expect it.
This is the detail that catches teams off guard: miss the currency parameter, and GA4 doesn't throw an error. It just quietly drops the revenue from your reports. No warning, no red flag in the interface. You just end up staring at a purchase count that doesn't match the revenue number next to it, with no obvious reason why.
There are two real paths here. One is Shopify's native Google & YouTube channel app, which handles basic GA4 connection with minimal setup. The other is Google Tag Manager with a custom dataLayer, which takes more work upfront but gives you control over exactly what data gets sent and when.
For most DTC brands running ads across more than one platform, GTM is the better call. You're already managing Meta pixels, Google Ads conversion tracking, and probably TikTok or Reddit tags too. GTM lets you centralize all of that instead of relying on Shopify's native app for GA4 and separate manual tags for everything else. It also gives you the ability to add missing parameters, fix naming mismatches, and debug in one place instead of guessing at what a black-box integration is doing.
The practical work is mapping Shopify's native checkout events to what GA4 expects. Shopify fires events like checkout_completed and product_added_to_cart on the storefront, and these need to be translated into GA4's event names and parameter structure: checkout_completed becomes purchase, product_added_to_cart becomes add_to_cart, and so on. The values, currency, and item arrays need to carry over correctly in that translation, which is where a lot of half-finished GTM setups fall apart.
One thing worth flagging early: Shopify Plus and standard plans aren't equal here. Plus gives you access to checkout.liquid customization and additional scripting on the checkout page itself, which makes it possible to fire more granular events (like add_payment_info) directly from checkout. Standard plans are more limited, since Shopify locks down checkout page customization outside of Plus, so some of that event tracking has to happen earlier in the funnel instead. If you're on standard Shopify, don't expect the same level of checkout-step granularity that Plus stores can get.
For a deeper look at how GA4 fits into a broader Shopify tracking setup, see our Shopify integration guide and the GA4 solutions overview.
The most common one: duplicate purchase events. A customer refreshes the order confirmation page, or hits the back button and lands there again, and if your tag fires on page load without a safeguard, GA4 counts it as a second purchase. Revenue gets inflated, sometimes by a noticeable margin, and nobody notices until the numbers stop matching Shopify's own totals.
Currency mismatches are another quiet killer. If your Shopify store sells in EUR but your GA4 property is set to USD (or vice versa), values get reported without conversion, which throws off every revenue figure downstream. This one's an easy fix, but only once you know to check for it.
Then there's incomplete item-level data. Missing item_category or item_brand on your purchase and add-to-cart events won't break revenue totals, but it kills your ability to break down performance by product line or collection later. You won't notice the gap until you go looking for it, and by then you're stuck backfilling.
Last one: not excluding internal and test traffic. Every dev checkout, every QA order, every team member's own purchase during testing, if it's not filtered out, it's sitting in your conversion rate and revenue-per-session numbers, quietly dragging them in the wrong direction.
Don't take a GA4 ecommerce events setup at face value just because events show up somewhere in the interface. Use DebugView first. It shows you each event as it fires, along with every parameter attached to it, so you can confirm purchase is actually carrying transaction_id, value, currency, and a full items array before any real traffic depends on it.
After that, run a real test. Place a test order, then check GA4's Realtime report immediately. You should see the purchase event land within seconds, with the right value attached. If it's missing, delayed, or shows a value of zero, something in the tag setup needs fixing before you go further.
The real test, though, is comparing GA4 against Shopify's own orders report over a set date range, a week is usually enough. Pull total orders and revenue from both sources and compare.
A small gap, a few percent, is normal. Ad blockers, cookie consent declines, and browser tracking prevention all account for some level of undercounting in GA4 that has nothing to do with your setup. But if the gap is larger than that, the problem isn't data quality in Shopify. Shopify's order data is accurate by definition, it's the source of truth. A bigger mismatch means there's a tracking gap in your GA4 setup, and it's worth going back through the event configuration rather than assuming the numbers will sort themselves out.
Even a perfectly clean GA4 ecommerce events setup only gets you one piece of the picture. You've still got Shopify order data, ad spend from Meta and Google, and GA4's funnel data sitting in three different places, and someone on your team is still stitching it together in a spreadsheet every week to figure out what's actually working.
That's the gap Trivas is built to close. It pulls GA4 ecommerce events alongside Shopify orders and ad platform spend into one Redshift-backed dashboard, so the cross-checking between GA4 and Shopify that we walked through above isn't a manual weekly chore anymore, it's just sitting there reconciled. If you want to see how the underlying event and order data gets structured once it's pulled in, our data dictionary breaks down the fields, and BI reporting covers how the dashboards themselves get built.
None of that replaces the work in this article, though. Getting GA4 tracking right is still step one. Trivas picks up from there, it doesn't skip the step.
If you're mid-setup and want to keep this kind of detail on hand, it's worth subscribing to our newsletter or browsing the rest of our resources for more on GA4 and Shopify tracking.
explore more insights
3 min read
3 min read
3 min read
.d53b12e5.png&w=3840&q=75 "Trivas.ai")