How to Set Up GA4 Ecommerce Tracking in 2026

Table of Contents

• What You Need Before You Start
• Step 1: Create Your GA4 Property and Data Stream
  • Configure Property Settings and Data Retention
• Step 2: Build Your GA4 Ecommerce Data Layer
  • Data Layer Best Practices That Prevent Broken Reports
• Step 3: Configure Google Tag Manager for Ecommerce Events
• Step 4: Map GA4 Purchase Event Parameters Correctly
• Step 5: Verify Data in DebugView and Troubleshoot GA4 Ecommerce Reports
• Consent Mode, Server-Side Tracking, and BigQuery for 2026
• Frequently Asked Questions

Last Updated: September 25, 2026

What You Need Before You Start

Setting up GA4 ecommerce tracking starts with three things: a Google Analytics 4 property, a Google Tag Manager account, and edit access to your store's checkout code. This guide from Elevated Digital walks through the full 2026 setup, from data layer to purchase event.

GA4 ecommerce is the framework that sends shopping activity (views, carts, checkouts, purchases) into Google Analytics 4. Without it, you see traffic but not revenue.

Gather these before you begin:

• Admin access to your GA4 account
• A Google Tag Manager container on your site
• Developer or theme access for data layer edits
• A test order you can place safely

Google's own GA4 ecommerce setup documentation recommends planning your event map first. Skipping that step is the most common reason reports come back empty.

Step 1: Create Your GA4 Property and Data Stream

Create your GA4 property first, then connect a data stream. The data stream is the pipeline that carries events from your site into GA4.

A GA4 data stream is a connection between your website and a GA4 property that collects user interactions as events.

To set it up:

1. In GA4, go to Admin, then Create Property
2. Enter your business name, reporting time zone, and currency
3. Choose Web as your platform
4. Enter your site URL and name the stream
5. Copy the Measurement ID for your tag manager

Configure Property Settings and Data Retention

Data retention defaults to two months, which is too short for ecommerce analysis. Change it to 14 months before you collect anything.

Also enable Google Signals if you want cross-device reporting, and confirm your currency matches your store's actual selling currency. A mismatch here quietly distorts every revenue figure.

Step 2: Build Your GA4 Ecommerce Data Layer

The data layer is a JavaScript object that holds ecommerce details before tags read them. Build it before you touch Google Tag Manager.

The GA4 ecommerce data layer is a structured JavaScript array that passes item and transaction details from your site to Google Tag Manager, which then forwards them to GA4.

Each event pushes an ecommerce object with an items array. Here is the pattern:

dataLayer.push({ ecommerce: null }); dataLayer.push({ event: "view_item", ecommerce: { currency: "CAD", value: 89.99, items: [{ item_id: "SKU-1042", item_name: "Wool Throw", price: 89.99, quantity: 1 }] } });

Data Layer Best Practices That Prevent Broken Reports

Clear the previous ecommerce object before every push. GA4 merges data from stale pushes otherwise, and you get phantom items in your reports.

Other rules that matter:

• Use one consistent currency code across all events
• Always include item_id and item_name
• Never push the same event twice on one page load
• Keep values numeric, not strings

Step 3: Configure Google Tag Manager for Ecommerce Events

In Google Tag Manager, you build one GA4 Event tag per ecommerce event and trigger each one from its matching data layer event.

Set up the core events in this order:

1. view_item fires on product pages
2. add_to_cart fires when a shopper adds an item
3. begin_checkout fires when checkout opens
4. purchase fires on the confirmation page

For each tag, set the event name, add your Measurement ID, and map the data layer variables. Then create a Custom Event trigger using the exact same event name.

Step 4: Map GA4 Purchase Event Parameters Correctly

The purchase event carries the parameters that feed your revenue reports, so map every one with care.

Get Started Today →

GA4 purchase event parameters are the specific fields (transaction_id, value, tax, shipping, currency, coupon, and items) that describe a completed order and populate GA4's monetization reports.

The essentials:

• transaction_id must be unique per order
• value is the total, excluding tax and shipping
• tax and shipping are reported separately
• currency must match your property setting
• coupon tracks discount codes

Getting transaction_id wrong causes duplicate revenue. GA4 deduplicates on that field, so a repeated ID drops a real sale.

Step 5: Verify Data in DebugView and Troubleshoot GA4 Ecommerce Reports

Open DebugView before you trust any report. It shows events in real time as they fire, which catches most problems in minutes.

To use it, enable preview mode in Google Tag Manager, then open DebugView in GA4 under Admin. Click through your store and watch events appear.

Common fixes:

• No events showing: check the container is published
• Events but no items: the items array is missing or malformed
• Duplicate purchases: transaction_id is not unique
• Missing revenue: value is not mapped to the tag

For deeper checks, the Google Analytics 4 DebugView guide explains each panel. For a structured audit approach, Google's Tag Assistant documentation helps confirm tags fire in the right order.

Consent Mode, Server-Side Tracking, and BigQuery for 2026

Three upgrades separate a basic setup from one that survives scrutiny: consent handling, server-side tracking, and raw data export.

Consent Mode adjusts how tags behave based on a visitor's choices. Under Canada's PIPEDA privacy requirements, you need a lawful basis before collecting personal data. Consent Mode lets tags fire in a limited way until consent is given, preserving modeled data instead of losing it entirely.

Server-side tracking moves tag execution to a server you control. This reduces the load on the browser and gives you more control over what data leaves your site.

BigQuery export sends raw event data to a warehouse. For ecommerce teams, this unlocks custom revenue reporting, attribution modeling, and checkout funnel analysis that the GA4 interface cannot match.

For multi-store setups, add cross-domain tracking so sessions survive between your store and checkout domains. Without it, a purchase looks like it came from nowhere.

Most teams can install the tags. Far fewer can prove the data is clean, complete, and compliant when a CFO or CMO asks hard questions. That gap is where reporting quietly falls apart.

Elevated Digital builds measurement systems that hold up to that scrutiny. We handle GA4 ecommerce setup, data layer work, server-side tracking, and BigQuery export as one integrated system, not a patchwork of fixes. Our focus on rigorous remediation and seamless system integration means your analytics connect properly to the tools you already run.

Get started with Elevated Digital and turn your ecommerce data into reporting you can defend.