BigCommerce Tracking Guide: GA4, GTM and Conversions in 2026

BigCommerce is the cleanest major ecommerce platform for tracking installation. Unlike Shopify, you don't need to edit theme files. Unlike Wix, custom code is allowed on every plan. The platform has a dedicated Script Manager that handles tracking script injection cleanly, and a powerful API for ecommerce events. This guide walks through the standard setup.

Step 1: Open the BigCommerce Script Manager

BigCommerce introduced the Script Manager specifically to handle tracking script installation without forcing merchants to edit theme files. To get there:

Log into your BigCommerce admin
Click Storefront in the left sidebar
Click Script Manager
Click + Create a Script

Step 2: Add the Google Tag Manager Script

In the script creation form, fill in:

Name of script: Google Tag Manager (or whatever you want to call it)
Description: Loads GTM on all pages (optional, just for your reference)
Location on page: Header
Select pages where script will be added: All pages
Script category: Essential (or Functional, depending on your cookie consent setup)
Script type: Script
Script contents: Paste your GTM <head> snippet here

Click Save. The script is now live on every page of your storefront, including the checkout pages - which is something Shopify can't do without Plus.

Why "Essential" category? BigCommerce's cookie consent integration uses script categories to decide which scripts to block until consent is given. If you use BigCommerce's cookie consent banner, "Essential" scripts always run, while "Functional" or "Advertising" scripts only run after consent. Set the category based on your privacy compliance needs - for many regions, GTM itself can be Essential, but the tracking pixels inside it should be loaded conditionally.

Step 3: Add GA4 Inside GTM

This part is the same as for any platform: open your GTM workspace, create a new Google Tag with your GA4 Measurement ID, set the trigger to All Pages, save and publish. Within minutes, GA4 will start receiving pageviews from your BigCommerce store.

Tracking BigCommerce Ecommerce Events

BigCommerce has a major advantage over Shopify here: it includes a built-in data layer on every page. The data layer is called BCData and contains all the information about the current product, cart, customer, and order. This makes ecommerce tracking dramatically easier than on platforms where you have to scrape data from the DOM.

For example, on a product page, you can access the current product's information like this:

BCData.product_attributes.price - current price
BCData.product_attributes.sku - SKU
BCData.product_attributes.stock - stock level

This means a "view product" tracking script can read this data directly and send it to GA4 with all the right parameters, without having to parse HTML or guess at element selectors.

Tracking Add-to-Cart on BigCommerce

BigCommerce dispatches a custom JavaScript event called cart-item-added when a product is added to the cart via AJAX (which is the default in modern themes). You can listen for this event and fire your tracking when it happens. The event detail includes the product information, so you can pass cart value, item ID, and quantity directly to GA4.

For the more traditional form-based add-to-cart (used in older themes), the standard form submit listener works, just like for any other ecommerce platform.

Tracking Purchases

BigCommerce shows the purchase confirmation on a URL like /checkout/order-confirmation. You can fire your purchase tracking on this page by triggering on the URL pattern in GTM. The order data is available in BCData.order with all the fields you need: order ID, total, currency, line items.

One caveat: the order confirmation page is a server-rendered page, not a single-page-app navigation, so the standard page view trigger fires correctly. No need for History Change triggers like you might use on a SPA.

Adding Meta Pixel, Google Ads, and Other Channels

Once GTM is set up, you don't need to use the BigCommerce Script Manager again. Add every other tracking script (Meta Pixel, Google Ads conversion tags, LinkedIn Insight Tag, Microsoft UET) as tags inside your GTM container. This gives you a single place to manage every pixel, with full version control via GTM's workspace history.

TrackingCoder generates GTM containers that include all the channels you select with all the right base scripts and event tags pre-configured. For BigCommerce specifically, it uses the BCData object to populate ecommerce parameters, so the tracking is more accurate than what generic tutorials produce.

Common BigCommerce Tracking Mistakes

Adding tracking scripts to both Script Manager and theme files. Some merchants paste the same Meta Pixel into the theme's base.html file and add it through Script Manager. This double-fires every event. Use one or the other, never both.
Forgetting the checkout pages. Always confirm your tracking fires on the order confirmation page, not just the product and cart pages. Shopify users especially get tripped up here - BigCommerce makes this easier, but you still need to verify.
Not categorising scripts for cookie consent. If you have a privacy banner, mis-categorising tracking scripts means they either don't fire when they should, or they fire before consent is given (a GDPR violation in the EU).