Coming soon - currently in BigCommerce App Marketplace review

Server-side conversion tracking for BigCommerce

Your BigCommerce pixel loses 20-40 % of purchases to ad blockers, Safari ITP, and iOS App Tracking Transparency. AxiTrace installs a free BigCommerce app that captures purchases from the store/order/statusUpdated webhook and forwards server-side events to Facebook CAPI, TikTok, Google Ads, GA4, Reddit, OpenAI Ads, Pinterest and LinkedIn - no theme edits, no GTM container, no checkout scopes required.

The app is pending marketplace review. Request early access or get notified when it launches:

Get notified → info@axitrace.com
  • 10,000 free visits / month, all nine platforms
  • Free app, no BigCommerce billing required
  • Webhooks bypass ad blockers & iOS ATT
  • BODL-powered storefront events, no theme edits

Why BigCommerce purchase tracking quietly breaks

BigCommerce admin shows every order correctly, but Facebook Ads Manager, TikTok Events Manager and Google Ads report 20-40 % fewer purchases. That gap is the difference between a pixel-only setup and a server-side one. Here is where it leaks on BigCommerce specifically.

Ad blockers and ITP

Roughly 30 % of shoppers run an ad blocker. Safari shortens 1st-party cookie lifetime to 7 days under ITP. Both silently cut the Purchase rate Meta and TikTok see, with no error shown in your BC admin.

No official Meta CAPI app

BigCommerce does not ship a native Facebook Conversions API connector. Merchants stitch it together with GTM, which iOS ATT and uBlock then block alongside everything else loaded by the tag manager.

BODL disabled by default

The BigCommerce Order Data Layer is not enabled by default. Most pixel setups work around it with theme edits, which break on theme updates and create maintenance overhead for every plugin.

Checkout JS restrictions

BigCommerce’s checkout iframe restricts third-party JavaScript. Custom scripts that fire a Purchase pixel on checkout completion often fail silently, especially on non-default checkout themes.

The fix: stop relying on the visitor’s browser to confirm the purchase. AxiTrace receives the store/order/statusUpdated webhook from BigCommerce and forwards the Purchase event server-side to Meta, TikTok, Google Ads, GA4, Reddit, OpenAI Ads, Pinterest and LinkedIn - de-duplicated against your browser pixel if one fired.

Webhook + BODL dual tracking

Server-side purchase via store/order/statusUpdated plus BODL storefront events for full-funnel visibility. Both are deduplicated automatically.

Recover lost conversions

Server-side events reach Facebook, TikTok, Google Ads, GA4, Reddit, OpenAI Ads, Pinterest and LinkedIn even when the browser pixel is blocked, declined in consent, or stripped by Safari ITP.

One app, nine platforms

Facebook CAPI, TikTok Events API, Google Ads (Enhanced Conversions), GA4 (Measurement Protocol), Reddit CAPI, OpenAI Ads, Pinterest CAPI and LinkedIn CAPI from a single BigCommerce app - no GTM container to maintain, no sGTM mappings, no per-platform code.

What the app tracks

The server-side transaction.charge event is the one that matters for ROAS - the rest are BODL client-side signals that help with audiences, retargeting and funnel analysis.

Event Trigger Source
transaction.charge BC store/order/statusUpdated webhook on order creation Server
product.view BODL product_viewed event Browser
product.addToCart BODL cart_item_added event Browser
begin_checkout BODL begin_checkout event Browser
page.view Every storefront page load Browser

Each event is deduplicated by event_id. If a BODL browser pixel already fired the purchase confirmation, the server event reconciles against it - Meta, TikTok and Google Ads count one conversion, not two.

How to set it up

  1. 1 Enable BODL in BigCommerce admin → Settings → Analytics → Hosted Analytics → toggle on BigCommerce Order Data Layer and save
  2. 2 Open Apps → App Marketplace, search AxiTrace, click Install
  3. 3 Review the four OAuth scopes on the BigCommerce consent screen and click Confirm
  4. 4 After redirect, find your workspace public key in the AxiTrace App Extension panel (BC admin sidebar)
  5. 5 Optionally configure a custom tracking domain (CNAME pointing to stat.axitrace.com) in the App Extension panel
  6. 6 Connect Facebook CAPI, TikTok, Google Ads, GA4, Reddit, OpenAI Ads, Pinterest and LinkedIn in the AxiTrace dashboard - one click each via OAuth
  7. 7 Place a test order - the purchase event lands in the dashboard within ~1-2 minutes

Full step-by-step walkthrough including BODL setup, OAuth scopes, custom domain, and webhook troubleshooting: BigCommerce setup guide →

AxiTrace vs other BigCommerce tracking approaches

Most BigCommerce merchants land on one of four setups. Here is how they compare on the things that actually move ROAS.

Approach Bypasses ad blockers No theme edits Setup time Maintenance
AxiTrace app ✓ ✓ ~10 min None
Browser pixel only (GTM Web) × × 1-2 h Frequent
Server-side GTM (sGTM / Stape) ✓ Partial 1-3 days High
Custom webhook integration (DIY) ✓ ✓ 2-6 weeks High

See also: AxiTrace vs Stape, vs Elevar, vs Littledata, managed server-side GTM hosting.

Built for BigCommerce stores that need real data

Mid-market DTC brands

US-based merchants on BigCommerce Pro and Enterprise who need accurate ROAS reporting for Facebook and TikTok without a developer-intensive sGTM setup.

Stores with high ad-blocker rates

Tech-savvy audiences (B2B, SaaS-adjacent, developer tools) where ad-blocker penetration often exceeds 40 %. Server-side webhooks are immune.

Agencies managing multiple stores

OAuth install flow, App Extension iframe, and per-workspace keys mean one AxiTrace account can manage tracking for many BigCommerce stores with no shared credentials.

Headless BigCommerce

Server-side purchase tracking via webhooks works regardless of the frontend stack (Next.js, Nuxt, custom). Browser SDK can be wired manually to the BODL data layer.

Under the hood

The integration is built on two independent data paths that reinforce each other.

  • • Receives store/order/statusUpdated webhooks from BigCommerce; HMAC-SHA256 signature verified before any processing.
  • • Enriches the minimal webhook payload via BigCommerce REST API v2 (GET /v2/orders/{id}) - line items, revenue, currency, customer details.
  • • Generates a deterministic UUID v5 event_id per order (bigcommerce_order:{orderId}) so retries are idempotent and pixel deduplication works across server and browser paths.
  • • Registers the AxiTrace BODL script via the Script Manager API on install; removes it on uninstall. No theme edits, no leftover code.
  • • App Extension iframe in the BC admin sidebar shows connection status, public key, webhook health, and custom domain config.
  • • Hourly webhook health-check re-activates dormant webhooks before BC’s 90-day auto-deactivation removes them.
  • • All tokens encrypted at rest with AES-GCM; no PII stored on AxiTrace servers beyond what is needed for event forwarding.

Frequently asked questions

Which BigCommerce plans does AxiTrace support?

AxiTrace works on all BigCommerce plans (Essentials, Plus, Pro, Enterprise) that support the App Marketplace and Script Manager API. There are no plan restrictions from the AxiTrace side.

How is server-side tracking different from a normal BigCommerce pixel?

A normal pixel runs in the visitor's browser, so it is blocked by uBlock / AdGuard / Brave, silenced by Safari ITP and iOS App Tracking Transparency, and gated by cookie consent banners. AxiTrace subscribes to the BigCommerce `store/order/statusUpdated` webhook on the server and POSTs a `transaction.charge` event to Facebook CAPI, TikTok, Google Ads, GA4, Reddit, OpenAI Ads, Pinterest and LinkedIn directly from PHP. There is no browser involved in the purchase event, so the conversion reaches the ad platforms regardless of what the visitor blocks.

What is BODL and why do I need it?

BODL (BigCommerce Order Data Layer) is a first-party data layer from BigCommerce that exposes standardised storefront events (product_viewed, cart_item_added, order_purchased) to third-party scripts. AxiTrace subscribes to these events for client-side tracking. BODL must be enabled in Settings → Analytics → Hosted Analytics. Without BODL, only server-side purchase events (via webhooks) work; storefront funnel events like product views and add-to-carts will not fire.

Does it work with custom BigCommerce themes (Stencil)?

Yes. The AxiTrace script is registered via the BigCommerce Script Manager API - it is injected into every storefront page automatically, with no theme edits required. Any Stencil theme (Cornerstone, marketplace themes, custom builds) that emits BODL events will work out of the box. Headless / composable frontends (Next.js, etc.) need to subscribe to BODL events manually using the AxiTrace JavaScript SDK init.

Does it support multi-storefront (MSF) configurations?

Multi-storefront support is planned for a future release. The current version tracks one storefront per AxiTrace workspace. Contact info@axitrace.com if your store uses MSF - we will prioritise based on demand.

What OAuth scopes does the app request?

Exactly four scopes - all read-only except Script Manager: store_v2_orders_read_only (order enrichment), store_v2_customers_read_only (hashed PII matching for Facebook EMQ and TikTok match quality), store_v2_information_read_only (store metadata at install), and store_content (Script Manager API to register and remove the tracking script). The more sensitive store_content_checkout scope is not requested, avoiding the mandatory BC security review while still capturing the order_purchased BODL event on the confirmation page.

Will it conflict with my existing Google Tag Manager setup?

No. AxiTrace fires events with a unique event_id and Facebook / TikTok / Google all deduplicate against that ID, so running AxiTrace alongside a Web GTM container or a server-side GTM / Stape container produces a single counted conversion, not a duplicate. Most merchants remove their legacy Web Pixel and sGTM Purchase tags once AxiTrace is live, because there is nothing left for them to add. If you would rather not maintain your own server container at all, AxiTrace's Business and Custom plans can host Google's official sGTM container for you on your existing tracking domain - see the setup guide.

How long until events appear after a purchase?

Client-side events (page views, product views, add-to-cart, checkout, browser-side purchase confirmation via BODL) appear instantly. Server-side purchase events appear within 1-2 minutes - the delay is BigCommerce webhook delivery plus AxiTrace REST API enrichment. Once events are in the AxiTrace pipeline they fan out to Facebook CAPI, TikTok, Google Ads, GA4, Reddit, OpenAI Ads, Pinterest and LinkedIn in real time.

Is the app free? Where is the catch?

The BigCommerce app is free to install. Billing is on the AxiTrace SaaS at axitrace.com only - the Free plan covers 10,000 visits per month, all nine ad platform integrations, and one workspace. Paid plans start at $99 / month billed annually when your visit volume grows. There is no per-store surcharge, no BigCommerce-specific upcharge, and no feature gated by the app itself.

When will the app be available on the BigCommerce App Marketplace?

The app is currently pending review in the BigCommerce App Marketplace. Review timelines are typically 3-6 weeks. To request early access while the review is in progress, email info@axitrace.com with your BigCommerce store URL.

Looking for the step-by-step install? Read the BigCommerce setup guide, or compare against Shopify, WooCommerce, Magento 2 and Shopware 6.

Ready to track conversions
accurately?

Join e-commerce teams who stopped guessing and started measuring. Free plan, no credit card, setup in minutes.

Start Free - No Credit Card Required

10,000 free visits/month · All 9 ad platforms · Full dashboard