How to Use GA4 with a GTM Extension for Smarter eCommerce Tracking?

On May 13, 2026, Google Analytics added an AI Assistant channel to its default channel group, so visits from tools such as ChatGPT, Gemini and Claude finally get their own line in your reports, according to Google’s release notes. A store with a half-working GA4 setup cannot answer the obvious next question: are those visitors buying?

When this guide first appeared in April 2023, the urgent story was leaving Universal Analytics. That story is over. The questions in 2026 are about consent, server-side events, revenue that matches your Magento orders, ad attribution and AI referrals. This rewrite shows how to use MageDelight’s GA4 Pro with GTM Support extension to get a Magento 2 store tracked accurately for 2026.

You will find what changed this year, the extension settings that matter, a ten-step setup, a validation matrix, and a reconciliation checklist for the day GA4 and Magento disagree. Extension details come from the product page and user manual. Google’s behaviour comes from Google’s own documentation.

What Is Different About GA4 and GTM in 2026

Five developments change how a Magento store should set up and read GA4. Dates are from Google’s release notes and developer documentation.

What the GA4 Pro Extension Does

Magento does not hand GA4 a ready-made ecommerce data layer. Without one, you need a developer to build events, tags and triggers by hand. The extension does that work from the admin panel. Based on the user manual, it provides:

• GTM head and body code fields, plus Account ID, Container ID and Measurement ID settings.

• A Generate button that exports a JSON file of GTM triggers and tags to import into your container.

• Product identifier choice (SKU or ID), base or store currency, brand attribute, and parent or child variant reporting.

• Order total options (subtotal or grand total) with switches to exclude tax and shipping, and a configurable checkout success page path.

• Up to five custom product attributes, promotion tracking, and Google Ads conversion and remarketing fields.

• A cookie consent-based tracking switch.

• Server-side Measurement Protocol events with API secret, event list, optional User-ID debug collection and scheduled log cleanup, including a Realtime Tracking Logs report in the admin.

The product page shows compatibility with Magento Open Source, Adobe Commerce and Adobe Commerce Cloud from version 2.4.0 to 2.4.9. It also confirms Hyvä compatibility. Includes a GA4 Lite option for users with simpler needs. The price listed is $179 for Magento Open Source at the time of writing. Please check the price for your edition before purchasing.

Prerequisites

• A Magento 2.4.x store (Open Source, Adobe Commerce or Cloud) and a staging site, with a backup of the web directory and database.

• A GA4 property with a web data stream and a GTM web container.

• Admin access to GA4 (Editor or above) and GTM (publish rights).

• Your consent platform and its current settings, plus a named person who owns privacy decisions.

• Your product ID convention, and the currency your finance team reports in.

Setup, Step by Step

Step 1: Prepare GA4 and GTM

1. In GA4, create a web data stream for every store domain. Take the Measurement ID.

2. In GTM, set up a web container. Write down the Account ID and Container ID.

3. In GA4 Admin, review data retention. Event-level data defaults to two months, and standard properties can extend it to 14 months.

4. Create a Measurement Protocol API secret on the data stream. You need it in Step 7.

5. Choose your product ID, currency and revenue definitions now because Step 5 depends on them.

Step 2: Install the Extension

Install the MageDelight Base Extension first, then the module, on staging. The manual’s install sequence is:

php bin/magento setup:upgrade

php bin/magento setup:di:compile

php bin/magento setup:static-content:deploy

php bin/magento cache:clean

Log out of the admin, then log back in. On Magento 2.3 and later, activation is silent and needs no license key. Not sure about your environment? According to the site banner, MageDelight offers a free professional installation call for supported extensions.

Step 3: Connect GA4 and GTM

• Enable the module, and enter the associated Google account and GA4 API key as the manual describes.

• GTM codes. Paste the head JavaScript code and the non-JS body code with your container ID.

• IDs. Enter the GTM Account ID, Container ID and the GA4 Measurement ID.

• Domain. If you use strict domain tracking, enter the domain the data stream expects.

Success looks like this: the GTM snippet is visible in the page source on every storefront page. GTM Preview successfully connects to your staging site.

Step 4: Generate and Import the GTM Container

1. Under Export Triggers and Tags, click Generate to download the JSON file.

2. In GTM, go to Admin > Import Container. Select the file.

3. Pick the workspace, then choose Merge or Overwrite so your current tags are not lost.

4. Look over the conflict summary, rename any items that conflict and confirm the import.

5. Open Preview and browse the store. Make sure the imported tags fire correctly. Publish after Step 9.

Step 5: Set the Ecommerce Data Rules

These settings decide whether your GA4 revenue and product reports match Magento. Choose them once, write them down, and do not change them mid-quarter without noting the date.

Step 6: Handle Consent

The extension includes a cookie consent-based tracking switch. The manual does not describe consent mode signals, so do not assume the switch sends them. Google’s consent mode documentation says tags need default consent states set before they load and updated states sent after the visitor chooses.

• Choose a mode. Basic mode blocks tags until consent. Advanced mode loads tags with denied defaults, sends cookieless pings, and enables more detailed modelling. This is a decision for you and your counsel.

• Wire your consent platform. Many platforms send consent states to Google automatically. Confirm yours does, or configure it in GTM.

• Test the denied state. Deny everything, browse and buy, and confirm cookies are not written, and the behaviour matches your choice.

• Ask support. Ask MageDelight how the extension’s consent switch interacts with your consent platform and with the four consent types. The cookie consent FAQ is a starting point.

This guide is not legal advice. Consent rules vary by market, so confirm requirements with a lawyer.

Step 7: Add Server-Side Events with Measurement Protocol

Client‑side tags may miss purchases if a visitor blocks scripts or leaves an off‑site payment page before the success page appears. Server‑side events can fill that gap. Google says the Measurement Protocol adds to tagging, but tagging must still be active and not replaced by the Measurement Protocol.

• Enable the feature. Enter the Measurement ID and API Secret from Step 1.

• Choose events from the Event List. Start with purchase, then add others once you have validated the first.

• Avoid double counting. Turn on Automatically Disable Data Layer for Enabled Measurement Protocol Events, so each event is sent from one channel. Google deduplicates purchase events that share a transaction ID, but other events can be counted twice.

• Send User-ID only with a privacy review. It links activity across devices and needs a lawful basis.

• Debug briefly. Enable Debug Collect while testing, then switch it off. Set Auto-Delete Logs After Days and a cron schedule so logs do not bloat the database.

• Mind session context. Google says to include a session ID within 24 hours of the session start if you want an event tied to that session’s geography and device. Ask support whether the extension does this.

• Plan ahead. The Measurement Protocol is not being retired, but Google recommends the Data Manager API for new builds. Ask MageDelight whether it is on the roadmap.

MageDelight’s server-side tracking guide covers the idea in more depth.

Step 8: Connect Google Ads

• Enable AdWords in the extension, then enter the Google Ads conversion code for GA4. For remarketing, add the Conversion ID and Label ID.

• In GA4, link the property to your Google Ads account and mark purchase as a key event.

• Remember consent: when ad_user_data is denied, Google says hashed first-party data for enhanced conversions and user IDs are not used for advertising.

• Check that your redirects, CDN and URL rewrites keep gclid, GBRAID and gad_ parameters. Google’s July 2026 diagnostic flags properties where they are missing.

• Track campaigns with consistent UTMs. MageDelight’s Campaign Performance Tracker can validate them.

Step 9: Validate Before You Publish

Use GTM Preview and GA4 DebugView, and compare against the extension’s Realtime Tracking Logs under MageDelight > GA4 with GTM > Reports. Google says purchase data needs twenty‑four hours to appear in the standard reports. For a check, use DebugView. Place a test order and walk through the entire funnel.

Publish the GTM container after every row passes. Then repeat the checks on production.

Step 10: Set Up the 2026 Reporting Layer

• Find the AI Assistant channel in your Default Channel Group. Save a comparison of its conversion rate against search.

• Mark your real conversions as key events and review attribution lookback windows against your sales cycle.

• Open Task Assistant and clear its data collection recommendations.

• Build a Dashboard that shows the five KPIs that your team reviews every week. Dashboards were launched in GA4 on September 9 2026.

• If you add a hostname include filter, list every domain that sends data, including checkout and any headless front end, and test first.

• Pair GA4 funnel data with store behaviour, for example abandoned cart versus abandoned checkout, to decide where to act.

When GA4 and Magento Do Not Match

They will never be the same, but a steady gap of more than a few per cent usually has a cause. Check these in order.

Common Mistakes and Troubleshooting

• Importing with Overwrite. It wipes existing GTM tags. Use Merge and review conflicts.

• Wrong success page path. After changing the checkout, purchases stop. Re-test after every checkout change.

• Sending the same event twice. Disable the data layer for events that you send through the Measurement Protocol.

• Publishing GTM before consent testing. Test denied and granted states first.

• Changing definitions mid-stream. Switching between SKU and ID, or subtotal and grand total, splits your history. Record the change date.

• Leaving debug on. Debug Collect and unpruned logs bloat the database.

• Show User Email on a cached store. The manual says it may not support full page cache.

• Ignoring speed. Extra tags cost load time. Review them with a Magento performance audit if pages slow down.

Which Setup Fits Your Store

• Small store, no EU or UK traffic, little ad spend: the browser-side GTM setup from Steps 1 to 5 and 9 is a sound start. Ask MageDelight whether GA4 Lite fits.

• Store with Google Ads spend: add Steps 7 and 8. Complete purchase data protects your bidding signals.

• Store with EU or UK traffic: do Step 6 before anything else, with counsel.

• Hyvä or a custom checkout: the product page lists Hyvä compatibility. Test the checkout success path and events on staging first. If you are planning a Hyvä build, see MageDelight’s Hyvä development services.

• Several languages or currencies: set the currency rule deliberately, and see translating your catalog if you run separate language stores.

• Stores adding recommendations or reviews: measure them. See the Google AI recommendations guide, and track review-driven conversions alongside Advanced Review Ratings & Reminders.

• Unsure where to start: MageDelight’s Digital Marketing Audit reviews tracking, and its support service can implement fixes.

Everything above uses the GA4 Pro extension. The FAQ page and the setup guide go deeper on individual settings, and bundle discounts are listed on the bundles page.

FAQ

Do I still need Google Tag Manager?

This path is the flexible route. The extension injects the GTM code. Creates the tags. After that, your marketing team can add tags without changing code. The extension also supports server-side events.

Will GA4 revenue match my Magento reports?

Not exactly. Consent, ad blockers, off-site payment pages order status, refunds, currency and revenue definitions all create gaps. Look at the reconciliation table to see which ones apply.

Is Universal Analytics still relevant?

No. It has been retired, and GA4 is the only current Google Analytics. The old advice to run both in parallel no longer applies.

How long until data appears?

DebugView and Realtime show events as they happen. Google says purchase data takes 24 hours to appear in standard reports and explorations.

Is the extension compatible with my Magento version?

The product page lists Magento Open Source, Adobe Commerce, and Adobe Commerce Cloud from version 2.4.0 to 2.4.9. It also mentions Hyvä compatibility. Check everything on the staging environment before moving to production.