Digital Marketing

GA4 Ecommerce Tracking Setup for Shopify and Custom Stores

iJurug Soft2026-11-145 min read

A proper GA4 ecommerce tracking setup records every step from product list view to purchase and refund, with a consistent items array and a unique transaction ID on every order. When it is right, GA4 revenue sits close to your backend totals, funnels show where shoppers drop off, and ad platforms bid on real sales rather than guesses.

Store numbers in GA4 not matching your order panel? Tell us your platform and checkout flow and we can point you to the likely gaps.

The event model behind a GA4 ecommerce tracking setup

GA4 does not infer ecommerce activity. Your site must send recommended events with specific names and parameters, or the monetization reports stay empty.

Funnel events

Not every store needs every event, but begin_checkout and purchase are the minimum for a usable funnel, and add_to_cart is close behind.

The items array

Each ecommerce event carries an items array: item_id, item_name, price, quantity, and ideally item_brand, item_category (up to five levels), item_variant, item_list_name, and coupon codes where they apply. The event itself carries currency and value. Use the same item_id that appears in your Merchant Center feed, so product performance lines up across Google tools.

Transaction IDs and duplicates

Every purchase event needs a unique transaction_id. GA4 uses it to drop duplicate purchases, for example when a shopper reloads the confirmation page. Missing or reused IDs are among the most common reasons revenue in GA4 runs higher than reality.

Setup by platform

The event model is the same everywhere, but how you get those events out of the store differs sharply by platform. The main question is how much of the checkout you control: a hosted checkout limits where code can run, while a custom build gives full control and full responsibility.

Shopify

Shopify's Checkout Extensibility has replaced checkout.liquid and the old "additional scripts" box, so checkout and thank-you page tracking now belongs in Customer Events. The Google and YouTube app covers the basics. For more control, a custom pixel subscribes to Shopify's standard events, such as product_viewed, product_added_to_cart, checkout_started and checkout_completed, and maps them to GA4 events. Custom pixels run in a sandbox, so they cannot read the page DOM, and they must be wired to Shopify's customer privacy settings.

WooCommerce

Established plugins push a GA4-ready data layer that Google Tag Manager can read. Check how each one handles variable products, coupons and orders that complete after an off-site payment, and avoid running two plugins that both send purchase events.

Headless and custom stores

For React, Next.js or other custom builds, the development team pushes ecommerce events to the data layer from application code. Single-page apps also need page views sent on route changes, with care not to double-count the first load. This is the most flexible option and the one that most needs a written measurement plan. Our article on ecommerce website development in Bangalore covers the build side.

Reconciling GA4 revenue with your backend

GA4 will never match your order database exactly. The goal is a gap that is small, stable and explained. Typical causes:

Server-confirmed purchases

Where browser tracking is unreliable, send purchase and refund events from your backend using the GA4 Measurement Protocol, or route them through a server-side tagging container. The backend must reuse the client ID and session ID captured in the browser, or the sale arrives without its marketing source. Design this so the browser and server never both report the same order.

Feeding ad platforms with accurate sales

Once purchases are trustworthy, import them as key events into Google Ads or use the Google Ads conversion tag with enhanced conversions, link Merchant Center so product-level performance flows through, and send purchases to Meta via both pixel and Conversions API with a shared event ID. Value-based bidding is only as good as the revenue figures behind it. iJurug Soft handles this tracking work alongside conversion improvements under our ecommerce analytics and marketing services; see our guide to conversion rate optimization services for what to do with the funnel data once you have it.

How to brief an ecommerce tracking partner

What to share up front

Red flags

Be cautious of anyone who installs a plugin and calls the job finished without testing a real purchase, refund and coupon order end to end, or who cannot explain how duplicates are prevented. Another warning sign is a setup that lives only in one person's Tag Manager account with no measurement plan, because the next site update will quietly break it and nobody will know where to look.

Frequently asked questions

Can we keep Universal Analytics style enhanced ecommerce tags?

No. Standard Universal Analytics properties stopped processing data in July 2023 (360 properties followed in 2024), and its enhanced ecommerce format differs from GA4's. Legacy data layer pushes need to be mapped or rewritten to GA4 event names and parameters.

Should refunds be tracked?

Yes, if you want revenue reports and ad platform values to reflect reality. Send refund events with the original transaction ID, from the backend where possible.

How long does a GA4 ecommerce tracking setup take?

It depends on the platform, checkout complexity, number of markets and whether server-side purchase tracking is included. A test plan covering real orders should always be part of the timeline.

Want ecommerce numbers you can act on? Share your store platform, checkout flow and the gaps you are seeing through our contact form, or write to info@ijurugsoft.com. We will start with a test order review of your current setup and come back with a written plan and quote.