How to Connect Shopify to GA4 (and Track Every Purchase Correctly)

Almost every Shopify store has GA4 "connected." Very few have connected it well. And the difference isn't cosmetic: if GA4 counts the same order twice or loses half of them, every decision you make on top of those numbers (how much to spend on ads, which products to push, where the funnel actually bottlenecks) starts from a false data point.

The two classic symptoms are opposite but share the same root cause. Double counting inflates revenue: ROAS looks great but never matches Shopify's own cash register. Missing purchases do the opposite: GA4 shows fewer orders than actually happened, and your campaigns look like they aren't converting. Both come from a setup built in layers, with no single consistent method behind it.

This is a hands-on guide. It tells you which method to pick based on the size of your store, how to set it up step by step, which ecommerce events GA4 needs to receive, and how to verify in fifteen minutes that every purchase is tracked exactly once. No theory: just things you can check today in your own dashboard.

Why Shopify-to-GA4 tracking goes wrong

Before you connect anything, understand where the errors come from. There are three, and you'll find them in almost every case.

1. Checkout changed, and the old scripts stopped working

For years, the standard way to track purchases was pasting gtag code into the thank-you page via checkout's "additional scripts." Since August 2025, Shopify has retired checkout.liquid and additional scripts in favor of Checkout Extensibility. Result: if your tracking still relied on that method, the purchase event simply stopped firing. Plenty of stores lost purchase tracking without noticing for months.

2. You have multiple integrations running at once

Double counting almost always means this: the native Google & YouTube app sends the purchase event, but the theme still has an old hand-written gtag, or a GTM container firing the same event. Two sources, one order, two purchases in GA4, and revenue that never reconciles.

3. Consent isn't wired up

On European traffic, if the cookie banner blocks GA4 but doesn't pass consent signals correctly, events don't fire (or only fire partially). It's not a Shopify bug: it's Consent Mode v2 configured badly, or not configured at all.

Three ways to connect Shopify to GA4

There are three concrete paths. The right one depends on how structured your store is and how much ad budget runs through it.

Rule of thumb: unless you have a specific technical reason to do otherwise, start with the native app. It covers the vast majority of cases, needs no code, and is the only option that handles both checkout events and consent on its own. Move to Custom Pixel or server-side when you need custom events, fine-grained deduplication, or ad-blocker resistance on serious budgets.

Setting up the native Google & YouTube app, step by step

This is the fastest path to clean tracking without touching any code.

1. Make sure you already have an active GA4 property. If you're starting from scratch, first create the property and the site's data stream by following the steps to set up GA4 from scratch.
2. In your Shopify admin, open the Shopify App Store and install the "Google & YouTube" channel.
3. Connect the Google account that owns or manages your GA4 property.
4. In the channel's settings, link the correct GA4 property. From this point on, Shopify starts sending ecommerce events.
5. Check that no other gtag or GTM container in your theme is sending the same events. If any are, remove them: this must stay the only source.
6. Wire up consent through Shopify's Customer Privacy API (native banner or a third-party CMP).

From here on, you don't touch code. If instead you need custom events or want to move away from GTM, the path is the Custom Pixel inside Settings, under Customer Events: there you subscribe to Shopify's standard events (checkout_started, product_added_to_cart, checkout_completed) and translate them into the matching GA4 events.

The ecommerce events GA4 needs to receive

Correct tracking isn't just the purchase event. It's the whole funnel, so you can see where people actually drop off. These are the events GA4 expects from an ecommerce store:

• view_item_list and select_item: product listing and click on a product card.
• view_item: product page view.
• add_to_cart, remove_from_cart, view_cart: cart management.
• begin_checkout: checkout start.
• add_shipping_info and add_payment_info: shipping and payment steps.
• purchase: the order itself, with transaction_id, value, currency, and items populated.
• refund: almost always forgotten. Without it, GA4's revenue stays inflated by returns.

The field that saves everything is transaction_id. It's the order ID. GA4 uses it to recognize the same purchase and avoid counting it twice if the customer reloads the confirmation page or hits back in the browser. If you're seeing inflated revenue with no double integrations active, the first suspect is a purchase event fired without a transaction_id. For the full event-by-event list with the correct parameters, keep a GA4 ecommerce events checklist handy.

Consent Mode v2 and GDPR: not an optional step

If you sell in Italy or Europe, consent isn't a compliance detail to fix "later." Since March 2024, Google has required Consent Mode v2 to use data from users in the European Economic Area (EEA) in audiences and remarketing for Google Ads and GA4. In plain terms: without it, you lose remarketing and a portion of modeled conversions.

On Shopify, the correct flow is this: a consent banner (Shopify's native one or a CMP) hooked into the Customer Privacy API, which passes the ad_storage and analytics_storage signals to Google. The native Google & YouTube app handles this wiring on its own; with Custom Pixel or GTM, you have to wire it yourself. If you're starting from zero on the consent side, it's worth understanding how Consent Mode v2 works before you launch campaigns.