Magento GA4 tracking that matches your orders

Magento GA4 tracking tends to be built in layers. A store moves from Universal Analytics to GA4, adds an extension for the dataLayer, switches on Adobe Commerce's Google Tag Manager setting, and nobody removes the previous layer. The result is purchases sent twice, revenue sent as text, and cart data that belongs to someone else. This page covers how tracking works on Magento Open Source and Adobe Commerce, the mistakes behind wrong numbers, and how to set up Adobe Commerce Google Tag Manager and GA4 properly.

How Magento GA4 tracking works

Magento offers three routes to GA4, and you should use one per event:

• The native Google integration. From release 2.4.5 the integration uses Google's gtag APIs, and the Magento_GoogleGtag module implements GA4 and Google Ads. You enable it under Stores > Settings > Configuration > Sales > Google API, in the Google Analytics4 section, with your measurement ID.
• Google Tag Manager in Adobe Commerce. Adobe documents GTM as an Adobe Commerce-only feature, provided by the Magento_GoogleTagManager module. In the same Google API section you set the account type to Google Tag Manager and enter the container ID. The integration publishes ecommerce events to the dataLayer for GTM to use.
• A third-party extension or custom code. Common on Magento Open Source, which has no built-in GTM setting, and on stores that need a dataLayer shaped differently from the native one.

Versions before 2.4.5 only offered the Universal Analytics integration. Universal Analytics stopped processing data in July 2023, so a store still relying on it needs an upgrade or an extension, not a configuration change.

What full page cache means for the dataLayer

Magento serves most pages from full page cache, usually Varnish. Adobe's documentation separates public content, cached and shared by all visitors, from private content such as the cart and customer name, which is loaded in the browser through the customer data sections. For tracking this matters in one specific way: anything specific to a visitor, such as cart contents, customer group or a hashed email for enhanced conversions, must come from that private content. If an extension prints it into the HTML of a cached page, the next visitor receives the previous visitor's data.

The common mistakes

The duplicate case deserves care. GA4 only merges purchases from the same user with the same transaction ID, so two installations with slightly different IDs or client IDs get through. Our guide on duplicate purchase events shows how to find them by transaction ID.

How to set up Adobe Commerce Google Tag Manager and GA4

1. Inventory the current setup. Check the Google API configuration at every scope (default, website, store view), installed tracking extensions, and theme templates for hard-coded gtag or GTM snippets.
2. Choose the source. If GTM will send GA4 events, disable the native GA4 sending for the same property. On Adobe Commerce, use the GTM account type; on Open Source, choose one extension.
3. Check your version and patches. On 2.4.5 or later the gtag-based integration is available. If revenue arrives as strings, apply the relevant quality patch or upgrade.
4. Agree the dataLayer. Write down which events the store pushes, their names and their parameters, ideally in a dataLayer specification. If the native events do not match GA4's ecommerce names, map them in GTM or ask the developer to push GA4-shaped events.
5. Build the GTM side. GA4 event tags with Custom Event triggers, dataLayer variables for ecommerce fields, and Consent Mode defaults that your cookie banner updates.
6. Test real orders. Place orders with a card and with each offsite payment method, check the success page in Tag Assistant and GA4 DebugView, and compare transaction IDs with the order numbers in the Magento admin.

The purchase GTM expects follows Google's ecommerce reference, with numbers as numbers and the order's increment ID as the transaction ID:

dataLayer.push({ ecommerce: null });
dataLayer.push({
  event: "purchase",
  ecommerce: {
    transaction_id: "000012345",
    value: 129.9,
    tax: 22.55,
    shipping: 4.95,
    currency: "EUR",
    items: [
      { item_id: "MJ01-S-Blue", item_name: "Beaumont Summit Kit", price: 62.5, quantity: 2 }
    ]
  }
});

Use the same increment ID in the Google Ads conversion tag and the Meta pixel, so each platform can deduplicate. If the store runs several store views with different currencies, send each order's own currency, not the base currency.

Magento conversion tracking for Google Ads

The native integration covers Google Ads through gtag as well, which makes it easy to end up with two primary purchase conversions: one from the Google Ads tag and one imported from GA4. Keep one primary and set the other to secondary, and pass the increment ID as the transaction ID.

What Tracking Whisper does on a Magento store

Tracking Whisper does not connect to the Magento admin and does not change the store's configuration, extensions or theme. It works through GTM, GA4 and the live site:

• Audit. A fixed set of checks on the GTM container, including duplicate GA4 configurations, purchase tags without currency or transaction ID, and leftover Universal Analytics tags. See the GTM audit.
• Build. GA4 and Google Ads tags, triggers and variables in its own GTM workspace, published only after a person approves the version.
• Developer guide. Where the store must push different data, it writes the dataLayer guide and measurement plan for your Magento developer.
• Browser checks. It opens key pages in a real browser and checks the dataLayer, the hits and the consent state, which shows string values and double hits directly.
• Monitoring. It watches container versions, key pages and GA4 numbers, and alerts when purchases stop or leave their usual range. See monitoring.

Next step

Connect your GTM container and GA4 property to Tracking Whisper and run an audit of your Magento or Adobe Commerce setup. Agencies running several stores can see how client access levels work on the agencies page.