Skip to main content
TrackingConsultingFree audit
BigCommerceFor BigCommerce stores

Get your BigCommerce tracking to 95%+ accuracy guaranteed in writing.

Out of the box, BigCommerce passes barely any customer data to Meta and Google. Your Event Match Quality is stuck at 4–5 instead of 9+. Smart Bidding can't optimize, Lookalikes shrink, CPMs rise. We rebuild your BigCommerce tracking server-side with a real Stencil-aware dataLayer that ships every signal Meta and Google need.

Get my free conversion tracking auditSee what we check

Free30 minutesNo obligation

By Ariful IslamHow BigCommerce works ↓

BigCommerce · what breaks

Why BigCommerce stores lose conversion data

  1. 01

    Native pixels are minimal

    BigCommerce's built-in Meta and Google integrations pass barely any customer data. EMQ stays at 4–5 instead of 9+.

  2. 02

    Stencil theme variability

    Custom themes break the default order confirmation page tracking. Half the BigCommerce sites we audit have broken Purchase events.

  3. 03

    B2B price visibility breaks values

    B2B Edition stores often fire events with $0 because logged-out users can't see prices. Optimization signals are useless.

  4. 04

    Multi-storefront duplicate firing

    If you run multiple storefronts with shared GTM, events double-fire across stores. Reported revenue inflates.

BigCommerce · the fix

What we deliver — BigCommerce

  • Stencil-aware dataLayer

    Custom Handlebars helpers + theme injection that emits clean events on every page including custom themes.

  • CAPI + Enhanced Conversions

    Full advanced matching, deterministic dedup, EMQ 8+.

  • B2B-aware event values

    Events use the actual customer-visible price (or list price) so optimization signals stay meaningful.

  • Multi-storefront safe routing

    Single sGTM container with storefront-aware tag firing — no double-counting.

BigCommerce · architecture

How a BigCommerce order should reach the ad platforms

BigCommerce splits into two very different worlds: the Stencil storefront where you control the theme, and the hosted checkout where you largely do not. Tracking has to be built for both.

  1. 1

    Click identifiers captured at first touch

    Click IDs are captured in the Stencil theme at landing and persisted to a first-party cookie before the customer reaches the hosted checkout, which sits on a different path and does not carry your query parameters forward.

  2. 2

    The browser sends the fast, fragile copy

    Stencil templates emit the browsing and cart events. Checkout is where the browser path gets thin — the hosted checkout limits what scripts can run, and the order confirmation page is the only reliable browser-side purchase hook.

  3. 3

    The order itself is the source of truth

    The BigCommerce order, retrieved through the store API or delivered by an orders/created webhook, is the truth. The confirmation page can be refreshed and is not always reached.

  4. 4

    A server container sends the authoritative event

    The orders/created webhook posts to a GTM server container on your own subdomain, which forwards the purchase keyed on the BigCommerce order ID.

  5. 5

    Customer identity raises match quality

    The order carries billing email, phone, name and address. Hashed server-side, these lift match quality well past what the hosted checkout can supply from the browser.

BigCommerce · events

The event set we build on BigCommerce, and where each one comes from

Script Manager placement matters as much as the event definitions on BigCommerce — a script scoped to the wrong page set is the most common reason an event never fires.

view_itemA Stencil product template rendersitem_id, value, currency, event_idBrowser + server, deduped
add_to_cartThe cart AJAX call returns successitem_id, quantity, value, currency, event_idBrowser + server, deduped
begin_checkoutThe hosted checkout loads with a non-empty cartvalue, currency, num_items, event_idBrowser + server, deduped
purchaseThe orders/created webhook fires against the order recordorder_id, value, currency, items[], hashed email/phone/name/address, event_idServer authoritative
refundA refund is recorded in the control panelorder_id, value, currencyServer only

BigCommerce · normal or broken

BigCommerce behaviors people mistake for faults

Most BigCommerce confusion comes from the split between the theme you control and the checkout you do not.

Normal, not a fault

  • Checkout pages carrying fewer custom scripts than the rest of the site

    The hosted checkout restricts this deliberately. It is a platform boundary, not a misconfiguration.

  • Script Manager scripts not appearing in preview

    Placement scoping means a script can be entirely correct and simply not scoped to the page you are looking at.

  • Ad platforms report more conversions than you have orders

    Meta credits a 7-day click and 1-day view; Google credits on click date. Two platforms can each claim the same sale. Compare each one to your order records separately and never add them together.

  • Recent days always look worse than they finish

    Conversions are credited back to the date of the click, so yesterday's return on ad spend is understated and will keep improving for several days. This is attribution working, not data arriving late.

Actually broken

  • Purchase firing on the confirmation page with no order guard

    Refreshing the page fires it again. The order ID has to be checked against an already-tracked flag.

  • Script Manager and a theme edit both installing the same pixel

    Two paths, one order, doubled conversions — and the theme copy is invisible from Script Manager.

  • Multi-storefront setups sharing one pixel configuration

    Conversions from every storefront land in one account with no way to separate them, so per-storefront performance cannot be measured at all.

BigCommerce · prove

How we prove the BigCommerce build is correct

The tag firing proves the tag fires. These prove the numbers are right.

Source of truth

BigCommerce order records

  • The orders/created webhook confirmed delivering, with retry behavior tested.
  • A refresh of the order confirmation page confirmed to produce no second conversion.
  • Script Manager placements audited against the theme, confirming exactly one firing path per event.
  • Purchase count within a few percent of bigcommerce order records for a fully closed week, matched on order ID rather than on totals.
  • No order ID appearing twice in any platform's event log.
  • Deduplication confirmed at every destination that supports it.
  • Test and staff orders excluded, with the exclusion confirmed active rather than merely configured.
  • The same reconciliation repeated 30 days later, because a setup that works once and then drifts is the harder failure to catch.

BigCommerce · free audit

What we check in the free audit

  • Native pixels are minimal
  • Stencil theme variability
  • B2B price visibility breaks values
  • Multi-storefront duplicate firing

Checked against

BigCommerce order records

Get my free conversion tracking audit

Free30 minutesNo obligation

BigCommerce · when not to buy

When a BigCommerce rebuild is not what you need

We would rather say this now than three weeks into an engagement.

  • You run a single storefront under about $2,000 a month in ad spend. The native channel integrations will cover most of it.
  • Your checkout is entirely on BigCommerce's default and your reconciliation gap is already small. Verify it, then leave it.
  • You are mid-migration to another platform. Rebuild after the move.

BigCommerce · what we deliver

Deliverables — BigCommerce

  • Server-side GTM container

    Hosted on subdomain or Stape.

  • Stencil dataLayer module

    Custom theme-friendly script that hooks into BC's storefront events without breaking on theme updates.

  • Meta CAPI + Google EC + TikTok

    Full advanced matching, dedup, modeled conversions ready.

  • GA4 e-commerce events

    view_item, view_item_list, select_item, add_to_cart, begin_checkout, add_payment_info, purchase — all schema-clean.

  • QA report + handover

    Notion runbook + 30-day support window.

Written guarantee

95%+ tracking accuracy

Measured against BigCommerce order records. Miss it and we keep working at no cost.

Get my free conversion tracking audit

Pricing

Pick the package that fits your ad spend

Browser-side starter

$400One-time fee · lifetime ownership

Foundation pixel install for your BigCommerce store. Honest disclosure: this is a starting point only. If you spend $1K+/month on paid media you should be on the 1st-party server-side tier — rather than quote you a recovery percentage, we'll show you how to measure your own gap: compare what the platforms reported against the orders in your backend for the same week. That ratio is the entire argument, and it's yours to check — see trackingconsulting.com/measurement-accuracy-methodology.

  • One-time fee · zero monthly · zero SaaS lock-in
  • BigCommerce dataLayer (clean spec)
  • GA4 e-commerce events
  • Meta Pixel · Google Ads tag
  • TikTok Pixel · Microsoft UET
  • Consent Mode v2 banner integration
  • QA test orders + 7-day support
  • No CAPI · no iOS recovery
Lock in the one-time price

1st-party server-side

Recommended

$800One-time fee · most popular

The done-for-you package every BigCommerce store running paid ads should start with. We build the entire 1st-party server-side stack on your subdomain — Meta, Google, TikTok, Microsoft, LinkedIn all fed from the server. Recovers the conversions iOS, Safari ITP, ad blockers and cookie deprecation hide today. You don't lift a finger. Built in 2–4 days · accurate data in 7 days.

  • One-time fee · save vs SaaS subscriptions over 5 years
  • Fully recovered + built in 2–4 days · accurate data in 7 days
  • Everything in browser-side starter
  • 1st-party server-side GTM (your subdomain)
  • Meta CAPI · full advanced matching · 8+ EMQ
  • Google Enhanced Conversions (Web + Leads)
  • TikTok Events API · Microsoft UET server
  • Deterministic browser ↔ server deduplication
  • Live EMQ verification + screenshots
  • Notion runbook + 30-day support · zero recurring
Lock in the one-time price

Full 1st-party stack

$1,800One-time fee · lifetime ownership

Every paid-media channel running 1st-party server-side, end-to-end. For BigCommerce brands spending $30K+/month who can no longer afford attribution leaks. Pay once. Own everything. Includes Pinterest + Snap + Reddit + LinkedIn CAPI, Klaviyo identity stitching, BigQuery + Looker Studio.

  • One-time fee · save 6-figure SaaS subscriptions over 5 years
  • Everything in 1st-party server-side tier
  • Pinterest · Snapchat · Reddit · LinkedIn · X CAPIs
  • Klaviyo identity stitching (if used)
  • BigQuery export (server logs + GA4)
  • Looker Studio attribution dashboard (branded)
  • Multi-region / multi-currency / EU residency
  • GDPR-audit-ready Consent Mode v2 wiring
  • 60-day support · optional retainer · no lock-in
Lock in the one-time price

FAQ

BigCommerce questions, answered

Yes — we have a separate React/Next.js dataLayer module for Catalyst that integrates with the GraphQL Storefront API.

More on BigCommerce

Free · 30 min

Free BigCommerce tracking audit

Book a free audit WhatsApp

Free30 minutesNo obligation