GA4 setup for Shopify in 2026: complete tracking guide

May 10, 2026
Shopify Tips
6 min read
GA4 setup for Shopify in 2026: complete tracking guide

Universal Analytics has been gone for over two years. Most Shopify merchants migrated to Google Analytics 4 (GA4) under duress, kept the default settings, and never went back to clean up. Then they wonder why attribution is broken, why their data doesn’t reconcile with Shopify Reports, and why the Cost-of-Goods-Sold reporting they had in UA is missing in GA4. The Shopify GA4 setup is structurally different from UA, and the setup choices you make in 2026 affect every marketing decision downstream.

This guide walks through the GA4 setup we recommend for Shopify stores in 2026: native Shopify integration, the events that matter, server-side tracking via the GA4 Measurement Protocol, attribution settings, and the conversion events worth setting up. The practical version, not the Google docs version.

In this guide

  1. Why GA4 setup matters in 2026
  2. Step 1: Native Shopify GA4 install
  3. Step 2: Verify the default events
  4. Step 3: Mark conversions
  5. Step 4: Enhanced ecommerce parameters
  6. Step 5: Server-side via Measurement Protocol
  7. Step 6: Attribution model
  8. Step 7: Audiences for retargeting
  9. Reconciling GA4 with Shopify Reports
  10. FAQ
  11. Related reading

Why GA4 setup matters in 2026

Three reasons. First, attribution. Paid ad platforms (Meta, Google Ads, TikTok) increasingly rely on GA4 conversions as the source of truth. Bad GA4 data = mis-attributed ad spend = wrong creative and budget decisions.

Second, audiences. GA4 audiences feed into Google Ads remarketing. If your audience definitions are off, your remarketing pool is off.

Third, reconciliation. GA4 typically under-reports revenue by 5 to 30% compared to Shopify, depending on how cookie consent and ad blockers affect your customer base. Knowing the gap and explaining the difference matters for every meeting where someone asks “is this number from Shopify or from GA?”

Step 1: Native Shopify GA4 install

Shopify has a first-party Google & YouTube channel that handles GA4 installation. Skip the GTM setup unless you have specific reasons; the native channel is enough for most stores.

  1. Install the Google & YouTube channel from the Shopify App Store
  2. Connect your Google account; pick the GA4 property to send data to
  3. Enable enhanced conversions (sends hashed customer email/phone for better attribution)
  4. Verify in GA4 that real-time events are firing

Within 24-48 hours you will see purchase, add_to_cart, view_item, and other events showing up in GA4 Reports → Engagement → Events.

Step 2: Verify the default events

The Shopify-GA4 integration sends these events by default:

  • page_view
  • view_item (product page view)
  • view_item_list (collection page view)
  • select_item (clicked product on collection)
  • add_to_cart
  • begin_checkout
  • add_payment_info
  • purchase
  • refund
  • search

Verify each one fires correctly. The most common gap: view_item not firing on themes with custom JS that hijacks the page render. Use GA4’s DebugView (Admin → DebugView) with a test browser to check.

Step 3: Mark conversions

In GA4, navigate to Admin → Events → mark these as conversions:

  • purchase (always; this is the main one)
  • begin_checkout (for funnel analysis)
  • add_to_cart (for top-of-funnel attribution)

Mark generate_lead as a conversion too if you have a newsletter signup or similar high-intent form. Don’t mark page_view or session_start as conversions; the data gets noisy.

Step 4: Enhanced ecommerce parameters

The default Shopify integration sends item-level parameters with each event: item_id, item_name, item_brand, item_category, item_variant, price. Verify these populate correctly. The most common gap on combined listings stores: item_variant doesn’t reflect the grouped product structure cleanly. If you split colors into separate products and group via combined listings, each color shows up as item_id but the parent group isn’t a parameter unless you add it via metafield.

For combined listings analytics specifically, the RCL + GA4 tracking guide walks through how to track group-level conversion alongside individual product conversion.

Step 5: Server-side via Measurement Protocol

Browser-based tracking loses 5-30% of events to ad blockers, ITP (Safari intelligent tracking prevention), and cookie consent banners. Server-side tracking via GA4’s Measurement Protocol fills the gap.

For Shopify, the easiest path is a server-side GTM (sGTM) setup or a tool like Stape, Elevar, or Littledata that handles the proxying. The native Shopify integration covers most cases without sGTM, but for paid ad attribution at scale, server-side is worth setting up.

  • When to bother: stores spending $20K+/month on paid ads
  • When to skip: stores under $500K/year revenue or with minimal paid ads

Step 6: Attribution model

GA4 defaults to “data-driven attribution” which uses Google’s machine learning to assign credit across touchpoints. For most stores this is fine. The alternative settings:

  • Last click (was UA’s default): assigns 100% credit to the last source
  • Position-based: 40% to first, 40% to last, 20% spread between middle touches
  • Linear: equal credit across all touches

Stick with data-driven for reporting. For specific channel analysis (how much credit does paid social really deserve?), use the Attribution → Model comparison report to see how different models would weight your traffic.

Step 7: Audiences for retargeting

Build these audiences in GA4 Admin → Audiences:

  • Cart abandoners: add_to_cart + no purchase in 7 days
  • Product page viewers: view_item on a specific product, no purchase
  • Past purchasers: purchase in last 90 days
  • High-value visitors: view_item with item_price > $100

Link these audiences to Google Ads for remarketing. The audience pool typically takes 24-48 hours to populate.

Reconciling GA4 with Shopify Reports

GA4 will under-report revenue compared to Shopify. Typical gap: 10-25%. Reasons:

  • Ad blockers: 8-15% of users block GA4 events
  • Cookie consent: users who decline cookies don’t fire GA4 events
  • Safari ITP: limits cross-session tracking
  • Mobile app traffic: depending on integration

Shopify Reports is the source of truth for revenue. GA4 is the source of truth for traffic source attribution. Don’t try to reconcile them precisely; document the gap and use each tool for what it’s good at.

Try Rubik Combined Listings free
Try Rubik Variant Images free

For combined listings analytics, see the RCL + GA4 tracking guide.

FAQ

Do I need GTM if I’m using the Shopify-GA4 integration?

No, for most stores. The native channel covers default events. Add GTM only if you need custom event tracking the native integration doesn’t handle (e.g., specific button clicks, scroll depth, custom forms).

Why does GA4 show different revenue than Shopify Reports?

Ad blockers, cookie consent, ITP, and Safari restrictions cause GA4 to under-report by 10-25%. Shopify Reports is the source of truth for revenue. GA4 is the source of truth for traffic attribution.

Should I use server-side tracking?

Worth setting up if you spend $20K+/month on paid ads. For smaller stores, the native integration is enough.

Which attribution model should I use?

Stick with data-driven attribution (the GA4 default). Use the Model comparison report for occasional channel analysis.

How do I track combined listings as a single conversion event?

Add a metafield-driven group identifier as a custom parameter on view_item and add_to_cart events. The dedicated RCL + GA4 guide walks through it.

Is GA4 enough, or do I need Triple Whale / Northbeam too?

GA4 is sufficient for most stores under $5M/year. Above that, dedicated attribution platforms (Triple Whale, Northbeam, North Beam) start adding value because they handle multi-platform spend reconciliation that GA4 alone cannot.

Co-Founder at Craftshift

You may also like