How to Add GA4 to Shopify Without Double Counting

Three Routes and What Each Sends

GA4 does not replace the reports already inside your admin: it adds Google's view of the same traffic. What each tool is good for is a separate question, covered in our guide to Shopify's own analytics. This page is about getting GA4 in, once, and proving it counts each order once.

The Google & YouTube channel

The channel is a free-to-install app called Google & YouTube, and its listing promises to connect the full ecommerce journey with insights in Google Analytics. If it is not installed yet, Shopify prompts you to install it during the GA4 setup anyway.

Shopify's help page on Google Tag Manager recommends its built-in integration because Shopify has the necessary logic built in to record Google Analytics Enhanced Ecommerce data. Google's own Shopify instructions go further and call connecting your GA4 web stream in the channel “strongly preferred”. The reason that matters most to you is upkeep: the events are mapped from Shopify's standard events without code of yours.

Shopify's page on replacing Google Tag Manager scripts on the Thank you page gives the reason in one line:

What the channel sends to GA4

The list comes from Google, not Shopify: Google's reference for Shopify event parameters says the app helps automatically send important events and parameters for Google tags. We counted 11 events on that page on November 2, 2026, grouped below by the stage of the visit.

Google adds that these events and parameters are mapped from Shopify's standard events, and that not all events contain user data. On top of them, the app sends standard measurement events, such as session_start, user_engagement and first_visit. If some of the newer events clutter a report, Google suggests filtering them in Google Analytics with the shopify_event_name parameter.

Google Tag Manager as a custom pixel

Choose this route when a GTM container already carries your other tags and you want GA4 managed in the same place. Shopify's tutorial for Google Tag Manager as a custom pixel is clear about the price: tag managers loaded in its sandbox have the same restrictions as any other pixel. When GA4 runs there, page URLs may include information about the sandbox, and outbound link clicks from GA4's Enhanced measurement can't be triggered automatically. Shopify's page on replacing Google Tag Manager scripts adds that Google can't provide technical support for Google Tag Manager custom pixels.

The rule that decides this route is one sentence on Shopify's Google Tag Manager page. Pick GTM or the channel for GA4, never both:

Testing is different here too: Shopify's page on replacing Google Tag Manager scripts says Google Tag Manager custom pixels can't be tested using Google Tag Assistant, while Shopify's GTM tutorial says the Tag Assistant page extension can test which Google tags load on the page but its Troubleshoot tag feature isn't compatible with custom pixels, and the tutorial tests a GTM custom pixel with the Shopify Pixel Helper.

The container setup itself — triggers, the data layer, consent — is a separate project, laid out step by step in our guide to installing GTM on Shopify the right way.

If you want to watch the build before you start, the video below shows it end to end. It is one practitioner's walkthrough (Loves Data, May 2024), not a Shopify source; its testing chapter starts at 12:33, and its resource list links the Tag Assistant Chrome extension, so for a GTM custom pixel test the events with the Shopify Pixel Helper, as Shopify's tutorial does, and your browser's developer tools.

A custom pixel with gtag

The same custom pixel slot can hold Google's gtag snippet instead of a GTM container, and then everything Shopify says about custom pixels applies: adding and using them is unsupported by Shopify, they load in a lax sandbox, and you insert the Google Consent Mode v2 snippet yourself. For where each kind of tracking code belongs in general, see where tracking code goes in Shopify.

Before You Connect

Shopify's Google Analytics setup page starts with the Google side: you need a Google Analytics account and a GA4 property before the store can send anything. Each condition below has a place to check it and a way round it.

The Editor role comes from Google's page on adding a property. Shopify's Google & YouTube page says the channel is available only for certain countries and currencies and links to Google's list.

One thing you can skip: Shopify says you don't have to connect to the Google Merchant Center to complete the GA4 tags setup. The same channel also syncs your products to Merchant Center for Shopping listings, a separate job covered in our Google Shopping guide.

Find Old Tracking Code First

Most stores that open this page already have something installed: a snippet from an old tutorial, a Universal Analytics tag from years ago, a script in checkout settings. Inventory it before you connect, because what you do with each piece depends on where it lives.

Where old code hides

Shopify's pixel migration guide names the places code was pasted by hand — theme.liquid, checkout.liquid (Shopify Plus only), Additional scripts in your checkout settings, and the Preferences page — and gives the search terms: Google pixels often use gtag() or dataLayer.push().

The Customer events page is where the newer pieces sit. Its list is called Pixels: in our development store on November 2, 2026 it held app pixels, Google & YouTube among them, and the Add custom pixel button sits on the same page. A tag Shopify converted from the old Preferences page is a custom pixel, so this is the page to look for it. If the page is greyed out for you, that is a permissions question, answered in why Customer events can be greyed out.

In Shopify adminOpen in your store

1. Settings
2. Customer events

Zoom

Checkout leftovers are the ones people forget, because the pages they ran on changed under them. Shopify's troubleshooting note is explicit about it:

Remove first or connect first?

For a custom pixel, Shopify's instructions for adding one say to remove or modify any existing pixels first, so customer events aren't counted twice. For Additional scripts, its upgrade page gives both orders: connect the pixel before deactivating the script, which leaves a short period of duplicate events, or deactivate the script first to prevent any duplicates.

What already stopped working

Every date below has passed, so none of this is preparation. It explains why an old snippet is either dead weight or a duplicate: dead if it still points at Universal Analytics, a duplicate if it sends GA4 events next to the channel.

Connect GA4 Through the Google & YouTube Channel

Shopify's page on connecting Google Analytics in the channel says you can connect an existing GA4 property or create a new one. The steps below follow Shopify's and Google's help, with the setup page we opened on November 2, 2026 in the screenshots:

1. Add the channel. Install Google & YouTube from the Shopify App Store; it then appears under Sales channels in the left menu.
2. Connect your Google account. The setup page opens with the heading Get started with Google & YouTube, and the card Set up your online store lists Your Google account as its first task.
3. Connect the property. Shopify's help starts this from the Looking only to set up Google Analytics 4? banner: click Get started, select an existing property from the drop-down menu or create a new one, then click Connect. On our setup page, Google Analytics had its own section further down, Understand your traffic with Google Analytics, with two tasks.
4. Confirm. Google's GA4 instructions add one more click after Connect: click Confirm.

In Shopify adminOpen in your store

1. Sales channels
2. Google & YouTube

Zoom

In Shopify adminOpen in your store

1. Sales channels
2. Google & YouTube

Zoom

Shopify's help calls the entry point a banner, “Looking only to set up Google Analytics 4?”, and Google's help a section on the channel's Overview page, “Just want to set up Google Analytics 4”; both lead to Get started, choosing the property and Connect.

Adding the Google tag by hand

Google keeps a fallback inside the channel for when you can't use the connection for any reason, such as not having the right access or needing to send data to more than one GA4 property. Then you add your Google tag, the ID starting with G-, under the channel's Settings > Google tags > Manage. Google's instructions for a G- tag put it in one line: “You can manually add Google tags for additional Google Analytics properties (or other Google services).”

Consent: What Reaches GA4 When Visitors Decline

Consent decides how much of your traffic GA4 ever sees, and it is set in two places: Shopify's customer privacy settings decide who is asked, and Google's consent mode decides what its tags do with the answer.

Who sees a banner

Shopify's pixel privacy rule is short: in markets configured to require consent, usually the European Economic Area and the United Kingdom, web pixels run only when visitors have provided the permissions required in the pixel configuration. By default, new pixels require Marketing and Analytics permissions.

For a new store with active markets in the UK and EEA, Shopify sets up its own cookie banner for visitors there automatically. If you run a third-party consent tool instead, it must sync consent to Shopify through the Customer Privacy API, and Shopify asks you to use the same consent regions in its settings and in the app — otherwise non-essential data may be processed before consent. How to switch the banner on and pick regions is covered in our privacy compliance guide.

In Shopify adminOpen in your store

1. Settings
2. Customer privacy
3. Cookie banner

Zoom

None of the Shopify pages we read on November 2, 2026 names the channel's GA4 tag in the pixel privacy rule above, which is written for web pixels. Google's page on setting up Shopify to obtain user consent says that if you use the Google & YouTube app for conversion tracking and have set up a consent tool that integrates with Shopify's Customer Privacy API, consent mode should work automatically, and that after you enable Shopify's cookie banner, consent mode is enabled automatically.

Shopify's pixel migration page also warns that a Google Analytics tag never moved to the channel, and converted to a custom pixel instead, might have its consent treatment changed. Test with the banner accepted and declined, and look at what arrives.

Basic or advanced consent mode

Google describes the two modes on its consent mode overview, and Shopify adds the advertising consequence for customers such as those in the EEA. Read the table by what happens to a visitor who says no:

On a custom web pixel, Shopify's page on customer privacy settings says to manually insert a code snippet to activate Google Consent Mode v2. If you block Google tags until the visitor consents, Google says in its Analytics help on consent mode that you will not get the full benefits of consent mode.

Check That Each Order Sends One Purchase

A connected channel tells you nothing about counting. The test that matters is one order and one purchase event, checked with the tools below.

Which test tool shows what

Each tool answers a different question, and two of them stop working in situations common on new stores. Realtime is the first place to look, Google's duplicate-tag check uses Tag Assistant, and Shopify documents its Pixel Helper on the pixel testing page.

The most common false alarm is an empty DebugView on a store with a cookie banner. Google spells out why:

Run a test order

1. Open the store like a shopper. Take the online store out of private mode and accept analytics cookies if your banner asks.
2. Turn on debug mode for your browser, since DebugView needs it. For your own device, Google's DebugView help says to use Google Tag Assistant or preview mode; Tag Assistant adds a parameter to your website address to enable debug mode. Then open DebugView or Realtime in GA4. For a custom pixel, Shopify's replacement guide says Google Tag Assistant isn't compatible, and Shopify's own test tool is the Shopify Pixel Helper; pair it with Realtime and your developer tools.
3. Place a test order and go all the way to the Thank you page.
4. Count the purchase. Realtime or DebugView shows the purchase arriving, and one matching request to the analytics endpoint in the network tab of your developer tools shows it was sent once.
5. Wait before judging reports. Google says many reports and explorations can take 24–48 hours to process data.

If purchases show up twice

Work through the usual senders, in this order:

• GA4 connected twice — once in the channel and once in a Google Tag Manager container (Shopify's duplicate-tracking warning above).
• Leftover checkout code in Additional scripts or checkout.liquid.
• The same event tracked in several places — Shopify calls tracking the same event more than once a common issue when migrating.
• Several Google tags, or conversion tracking set up before the channel — Google warns this can count one action more than once for ads and free listings.

GA4 has one safety net, and it is narrow. Google's transaction ID deduplication removes a purchase registered twice with the same transaction ID, and it works for web streams only, not app streams.

If you send purchases from your own custom pixel, give each one a transaction ID and never an empty string. None of the Shopify or Google pages we read says that deduplication makes it safe to run the channel and a second Google tag side by side — remove the second sender.

Why GA4 and Shopify Won't Match

A correct setup still disagrees with your Shopify reports, for reasons that have nothing to do with tags:

• Blocked tracking. Shopify's page on analytics discrepancies notes that customers can use browser extensions to block Google Analytics from tracking their sessions and purchases.
• Consent. Where a cookie banner is active, data from visitors in those regions is collected only after they consent.
• Bots. Google says traffic from known bots and spiders is excluded from GA4 automatically, and Shopify expects single-digit percentage dips in event counts after a move to web pixels, because some bots don't trigger the pixel sandbox.
• Discounts. Since April 24, 2025, the purchase value the channel's Google tags send is the subtotal minus discounts, and Google's reference notes it does not include shipping charges and taxes, so compare it with a Shopify sales figure calculated the same way.

Session counts are where the two drift furthest, and that gap has its own explanation in our breakdown of why Shopify and GA4 never agree on sessions.

The Setup Checklist

Steps one and two apply to every route. If you chose a custom pixel (GTM or gtag), Shopify's custom pixel page says to remove or modify existing pixels before you add one, so customer events aren't counted twice: do step five, old custom pixels and theme snippets alike, before step four, which then happens in Customer events instead of the channel, so its channel checks don't apply. Step three is the one that stops you connecting GA4 twice.

The Bottom Line

Adding GA4 to Shopify takes a few screens. Trusting it takes an inventory of what was already installed and one test order.

Frequently Asked Questions