Google Analytics for Shopify: Shopify Analytics vs GA4
Shopify Analytics already covers sales, sessions, and conversion rate. See what Google Analytics 4 adds, when you need both, and when native reports are enough.
By The Appnary Team
Searching for Google Analytics for Shopify? Start with what Shopify Analytics already gives you. Open Shopify admin, click Analytics, and you have sales, sessions, conversion rate, and a funnel showing where visitors drop off. It's there from day one, no setup required. Then decide whether Google Analytics adds an answer you actually need.
Shopify's built-in analytics covers the questions most stores ask daily. The Overview dashboard shows total sales, order count, average order value, and sessions over whatever date range you pick. The conversion funnel breaks visitors into added to cart, reached checkout, and sessions that converted, so you can see at a glance whether the problem is traffic, interest, or checkout friction. Behavior reports show top landing pages and top products by views. Acquisition reports split traffic by channel: direct, search, social, email, paid. You don't need to install a separate analytics tag to open these reports. Order totals and visitor measurement are different, though: Shopify's session reports use cookies and can be affected by customer privacy settings. Shopify's explanation of session discrepancies covers why sessions and conversion rates can change when visitors decline consent.
For a lot of stores, especially single-product shops or anyone running a lean catalog, that's the whole picture they need. You can tell if a product page is converting, whether a discount code moved the needle, and which channel is actually driving sales.
Where Shopify's native reports run out of road is anything that requires tracking behavior across visits or building visitors into a defined audience. GA4 lets you set up custom events for things Shopify doesn't track by default: scroll depth, video plays, clicks on a button that isn't tied to a purchase. It can connect activity across devices when you have suitable identity data. That isn't automatic for every visitor: Google's reporting identity guide explains how User-ID, device IDs, and modeling affect the result. Two anonymous visits on different devices aren't guaranteed to become one journey. It also lets you build audiences for remarketing, such as everyone who viewed a product but didn't buy in the last 30 days, and push those audiences into Google Ads. That matters for stores spending real money on paid search or Performance Max campaigns, because GA4's conversion data can feed Google's bidding algorithms more context than a single purchase event, which in theory helps Google spend the budget toward people more likely to buy.
That bidding integration is a different thing from simply having Google's conversion tag installed, and the two get confused constantly. A Google Ads conversion tag just tells Google a purchase happened, which is enough for basic conversion tracking. GA4 is the fuller reporting layer sitting next to it. If you're trying to sort out which of these you actually need for your ad accounts, this comparison of pixel tracking versus tag tracking walks through the distinction in more detail.
To connect GA4, create a property and web data stream, then connect the property through Shopify's Google & YouTube app. Shopify's GA4 setup guide confirms that ecommerce events are collected automatically after setup. You don't need Google Tag Manager just to start collecting those standard events. Additional custom behavior tracking is a separate job.
After connecting the property, verify the destination and test the events you expect. Check that a product view, cart addition, and test purchase reach the intended property before relying on the reports. Google's Shopify tag setup instructions cover the connection and warn about duplicate tracking. Keep the Google Ads conversion action separate from the GA4 property: receiving an event in Analytics doesn't prove that the Ads conversion action is configured correctly.
Consent affects both reporting systems. Shopify's session measurement and GA4's visitor data can have gaps when privacy settings limit collection. Review the store's customer privacy configuration and the tags you use, rather than assuming native reports are exempt. When comparing the systems, use the same dates, time zone, and metric definition. Order revenue, sessions, and ad-attributed purchases answer different questions; their totals needn't match.
So who actually needs GA4 on a Shopify store? Stores running meaningful paid ad spend through Google Ads, especially anything beyond simple search campaigns, tend to benefit from the deeper conversion data feeding back into bidding. Stores with more than one significant marketing channel, where figuring out which channel deserves credit for a sale isn't obvious from last-click alone, get more out of GA4's audience and attribution tools than Shopify's simpler acquisition report. And any store that wants to track specific on-site behavior, like whether people watch a product video before buying or how far they scroll on a landing page, needs GA4 or something like it, because Shopify's dashboard doesn't track events at that level of detail.
On the other side, if your store is early-stage, running mostly organic or social traffic, or managed by one person without a dedicated marketing hire, Shopify's native analytics probably answers every question you're actually asking day to day. Installing GA4 because a blog post or a Shopify Partner told you to, without a specific question it's meant to answer, is how a lot of stores end up with a GA4 property nobody has opened in six months.
The practical rule: add GA4 when you have a question Shopify's dashboard genuinely can't answer, not as a default checkbox. If that day comes, budget time to verify the automatic ecommerce events and your privacy settings before using the numbers to make decisions.