TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

READING ROOM › FIELD NOTE › NOTE-048

NOTE-048 · FIELD NOTE FILED 18 NOV 2026 · REVISED 18 NOV 2026 F-301 F-101

GA4 on Magento and BigCommerce: where the dataLayer differs from Shopify.

ABSTRACT — On Magento, GA4 often shows purchases and nothing before them: the built-in module sends page views and one ecommerce event, purchase. On BigCommerce the common fault is the opposite: the native integration and Google Tag Manager both send. Where each platform's events come from, what GTM can read, what you build, and how Shopify differs.

Baris Asa, tracking consultant, London · Filed 18 November 2026 · Last checked: 18 November 2026

If a Magento store’s GA4 shows purchases but no product views, add-to-carts or checkouts, check first whether Magento’s built-in module is the only sender: it sends page views and one ecommerce event, purchase. On BigCommerce the common fault is the opposite: the native GA4 integration already sends 11 ecommerce events, and Google Tag Manager sends some of them again. Magento’s funnel has to be built; BigCommerce’s mostly has to be left alone.

Shopify works differently again, through pixels; that is covered further down. What a correct GA4 ecommerce push looks like on any platform is in How to set up GA4 ecommerce tracking with GTM.

Is this your store? A two-minute check

You need GA4 and your store admin. No code.

  1. GA4 funnel. In GA4, open Reports, Monetisation, Ecommerce purchases, for last month. Read Items viewed, Items added to cart and Items purchased.
  2. Magento edition and version. The admin footer shows the version number, for example 2.4.7. Under Stores, Configuration, Sales, Google API, an Account type option of Google Tag Manager means you are on Adobe Commerce, the licensed edition.
  3. BigCommerce senders. Settings, Data Solutions (on Multi-Storefront: Channel Manager, Edit storefront settings, Data Solutions): is Google Analytics 4 connected? Storefront, Script Manager: is there a Google Tag Manager script too? If so, look in GTM’s Tags for a Google tag or a GA4 Event tag.

What the answers mean:

  • Magento, purchases with views and add-to-carts at or near zero: the built-in module is the only sender. Nobody built the funnel.
  • Adobe Commerce 2.4.9 or earlier, Google Tag Manager option in use, funnel incomplete or empty: the integration pushes the old Universal Analytics format and misses checkout events (details below).
  • BigCommerce, GA4 connected and GA4 tags in GTM: two senders for the same events, on file as F-101 . GA4 collects only the first purchase with a given transaction ID, so the purchase report can look fine while page views and cart events count twice.
  • BigCommerce on a custom checkout, or a headless storefront other than Catalyst: the native integration sends nothing from the checkout.
ShopifyBigCommerceMagento Open Source
You get without buildingfunnel, from the Google & YouTube app11 events, checkout includedpage views and purchase
You builda custom pixel, if neededa BODL script, only with GTMevery step before purchase
Duplicates come fromapp and pixel both sendingintegration and GTM both onextension and module both on
Checkout stepspixel eventssent by the integrationone page, steps after #
What each platform gives GA4 · three platforms · compiled from platform documentation and Magento 2.4-develop source, read 18 November 2026

What does Magento’s own GA4 module send?

Page views, and purchase as its only ecommerce event. The Google GTag module came in Magento 2.4.5. Its settings sit under Stores, Configuration, Sales, Google API, Google GTag, Google Analytics4, and the two that matter are Enable and Measurement ID.

The module loads GA4 on every page, which sends page views. On the checkout success page it sends purchase with:

  • transaction_id: the order number the shopper sees
  • value: the order grand total, plus tax, shipping and currency
  • items: SKU as item_id, product name as item_name, price and quantity

No view_item, no add_to_cart, no begin_checkout. That gap is on file as F-301 . On Magento my first question is who built the funnel. Often nobody did: the module was switched on and the GA4 reports were taken as complete.

Three more things in the same code:

  • Multishipping. When one checkout ships to several addresses, Magento creates several orders. The module sends one purchase: the first order’s number and value, with every order’s products attached. The other orders never reach GA4.
  • Cookie restriction mode. If it is on, the module sends nothing until the shopper’s cookie allows the website. That is Magento’s own consent switch, not Google Consent Mode.
  • The old Universal Analytics module still ships. A separate Google Analytics group with an Account Number field sits alongside it. If a UA account number is filled in there, that is the old module, not GA4.

Reloading the success page doesn’t send a second purchase: Magento clears the checkout’s success marker from the session, so a reload goes to the cart. PayPal Express brings the shopper back to the same success page, so those orders fire too, if the shopper comes back.

How do you build the Magento dataLayer?

Two routes: an extension that writes the pushes, or a developer who writes them into the theme and checkout. Either way, three places matter:

  • Product and category pages: view_item, view_item_list and select_item from the page itself.
  • Cart and customer values: from Magento’s customer-data sections, read in the browser. Magento caches whole pages, and its developer docs say anything specific to one shopper is handled in the browser, not in the cached page. A cart total printed into a cached page can show another visitor’s cart.
  • Checkout steps: from the checkout’s own step code. The default checkout is one page with two steps, Shipping and Review & Payments. Moving between them changes only the URL fragment, the part of the address after the #. No new page loads, so a Page View trigger fires once for the whole checkout. GTM’s History Change trigger fires when the fragment changes, and its built-in New History Fragment variable says which step opened. That gives the timing; the items and value still have to come from a push.

Using an extension, read what it pushes in GTM Preview, Google’s tag debugger, before trusting it. Three checks: GA4 event names such as add_to_cart, not Universal Analytics names such as addToCart; ecommerce: null pushed before each event; and no shopper-specific values in cached pages. If the extension sends its own purchase, switch the built-in module off: one sender per event.

What changes with Adobe Commerce’s Google Tag Manager integration?

Up to 2.4.9 as shipped, it pushes the legacy Universal Analytics ecommerce format and misses several checkout events, so a standard GA4 build gets an incomplete or empty funnel. The integration is Adobe Commerce only; Adobe says it “is not available in Magento Open Source.” You set Account type to Google Tag Manager and enter the container ID.

The evidence is Adobe’s own. Its 2.4.10-alpha1 release notes list the fix: “Before the fix, ecommerce events sent to Google Analytics 4 through Google Tag Manager used the legacy Universal Analytics format and were missing several checkout events.” Its Google Analytics guide still sets the integration up with Universal Analytics triggers such as addToCart, checkoutOption and removeFromCart. The same guide says the checkout event isn’t sent for PayPal and other payment methods that redirect off the site.

Adobe sometimes ships fixes as patches for older versions, so on 2.4.9 or earlier I open GTM Preview and read what the integration actually pushes before building a single tag on it. Then one of three routes: map the old-format pushes to GA4 events in GTM, have a developer push GA4-shaped events alongside, or upgrade once 2.4.10 is generally available. It is an alpha today.

What does BigCommerce’s GA4 integration send?

The full ecommerce funnel, without GTM, as long as the store uses BigCommerce’s own theme and checkout. You connect it under Settings, Data Solutions. BigCommerce’s events reference lists 11 storefront events: search, view_promotion, view_item_list, view_item, add_to_cart, remove_from_cart, view_cart, begin_checkout, add_shipping_info, add_payment_info and purchase, which fires when the shopper completes checkout.

The conditions matter more than the list:

  • Stencil and Optimized One-Page Checkout. Stencil is BigCommerce’s standard theme system; Optimized One-Page Checkout is its standard checkout. BigCommerce: “Using a custom checkout with our GA4 integration is not supported.” Most headless storefronts aren’t tracked either. Catalyst, BigCommerce’s own headless storefront, is the exception.
  • Refunds need setup. They happen in the control panel, not the storefront, and need a GA4 Measurement Protocol API secret: a key GA4 issues for sending events from a server.
  • Consent Mode is supported. When a shopper declines, the integration sends cookieless pings instead.

On a standard BigCommerce store I’d rather keep the native integration and remove GTM’s GA4 tags than rebuild what it already sends.

How do you get BigCommerce data into Google Tag Manager?

Only if you need GTM: for example, a custom checkout, or tags the integration doesn’t cover. Turn on BODL, the Big Open Data Layer, in the control panel or through the GraphQL Admin API, on a Stencil theme. Its events arrive on window.bodlEvents, not window.dataLayer: product.pageViewed, cart.addItem, checkout.checkoutBegin, checkout.shippingDetailsProvided, checkout.paymentDetailsProvided, checkout.orderPurchased and others.

BigCommerce’s example script waits for the page to load, checks BODL exists, subscribes to each event and logs it. You replace the log with a push. For cart.addItem, a sketch using the field names in BigCommerce’s schema:

window.addEventListener("load", () => {
  if (!window.bodlEvents || !window.bodlEvents.cart) return;
  if (typeof window.bodlEvents.cart.addItem !== "function") return;
  window.dataLayer = window.dataLayer || [];
  window.bodlEvents.cart.addItem((payload) => {
    window.dataLayer.push({ ecommerce: null });
    window.dataLayer.push({
      event: "add_to_cart",
      ecommerce: {
        currency: payload.currency,
        value: payload.product_value,
        items: payload.line_items.map((item) => ({
          item_id: item.sku,
          item_name: item.product_name,
          price: item.purchase_price,
          quantity: item.quantity,
        })),
      },
    });
  });
});

product_value is the price times quantity before discounts. Log one real payload from your store before relying on it. One GA4 Event tag in GTM then sends every event the script pushes.

Load the script through Storefront, Script Manager, on all pages, since cart events fire on product and category pages, and in the footer, as BigCommerce recommends for all-pages, checkout and order confirmation scripts. Script Manager respects the shopper’s cookie choices, so give each script its honest category.

Two cautions:

  • Don’t run GTM and the native integration for the same events. BigCommerce: “To avoid data collection interference, we recommend disabling Tag Manager.” If GTM stays, BigCommerce says to switch off in GTM every event the integration supports and the automatically collected ones, page views included.
  • Checkout step names differ between BigCommerce’s own pages. The developer docs say bodl_v1_shipping_information_added; the GA4 events reference says bodl_v1_add_shipping_information, and the same for payment. Build against what your store logs in the browser console.

How is Shopify different?

Shopify’s checkout runs no theme code, so a dataLayer written by the theme stops at the cart. Checkout events come from pixels: the Google & YouTube app for GA4 and Google Ads, or a custom pixel that hands Shopify’s events to GTM inside a sandbox, a walled-off frame that can’t see the page. The purchase comes from Shopify’s checkout_completed event, usually on the Thank you page, or on the first upsell page when there is one.

So on Shopify the question is which pixel sends what: Shopify tracking apps: what each one sends and GTM in a Shopify custom pixel.

Can the purchase be sent from the server instead?

None of the three sends a GA4 purchase from the server out of the box.

  • BigCommerce: only refunds, through the API secret above. Order webhooks exist, but BigCommerce says store/order/created also fires for failed and unpaid orders, so check the order status before sending a purchase from it.
  • Adobe Commerce: events and webhooks for calling outside systems. They send nothing to GA4 by themselves.
  • Magento Open Source: nothing built in. A developer builds it, usually with Google’s Measurement Protocol and the same transaction ID the browser sends.

Server events add to browser tagging; they don’t replace it. The trade-off is in Server-side tracking explained.

How do I test it on Magento or BigCommerce?

  1. Accept the cookie banner in a private window and connect Tag Assistant, Google’s tag debugger.
  2. Walk the funnel: product, cart, each checkout step, a real order.
  3. On Magento, look for events between the page views and purchase. Page views, then purchase, and nothing between means the funnel was never built.
  4. On BigCommerce with GTM, check each event arrives once, not once from the integration and once from GTM.
  5. In GA4 DebugView, the live view of test sessions, check one purchase with the order’s own number, and value and currency matching the order.
  6. Repeat with each off-site payment method, PayPal first.

If step 3 shows that gap, or step 4 shows doubles, that is the build I do: GA4 ecommerce tracking.

Common questions

Does Magento send GA4 ecommerce events on its own?

Only one: purchase, on the checkout success page. The Google GTag module (Magento 2.4.5 and later) also sends page views. Product views, cart and checkout steps need a dataLayer from an extension or a developer.

Does Adobe Commerce’s Google Tag Manager integration push GA4 ecommerce events?

Not as shipped up to 2.4.9, according to Adobe’s 2.4.10-alpha1 release notes: before that fix it sent the legacy Universal Analytics format and missed several checkout events. Check what yours pushes in GTM Preview. The integration is Adobe Commerce only.

Which GA4 events does BigCommerce’s native integration send?

Eleven: search, view_promotion, view_item_list, view_item, add_to_cart, remove_from_cart, view_cart, begin_checkout, add_shipping_info, add_payment_info and purchase. Refund needs extra setup. It needs a Stencil theme and BigCommerce’s Optimized One-Page Checkout.

Can I use Google Tag Manager with BigCommerce’s GA4 integration?

BigCommerce recommends disabling Tag Manager. If you keep it, switch off in GTM every event the integration sends, page views included, or GA4 gets them twice.

Does BigCommerce have a dataLayer for GTM?

It has BODL, the Big Open Data Layer, on window.bodlEvents once enabled. It is not window.dataLayer: a script has to translate each event into a GA4 push.

Why does Magento’s checkout send no page views between shipping and payment?

Both steps are one page; only the part of the address after the # changes. Use GTM’s History Change trigger, or have the developer push an event when each step opens.

Sources

I have no partnership, affiliate or commission arrangement with Adobe, BigCommerce, Shopify or any extension maker.

Read on 18 November 2026:

— B.A., filed from London

CONNECTED RECORDS F-301 F-101

REVISION HISTORY — revised 18 NOV 2026.

← back to the reading room