Server-side attribution for BigCommerce, headless-ready

{
  "scope": "store/order/created",
  "store_id": "1025647",
  "data": {
    "type": "order",
    "id": 45109
  },
  "producer": "stores/bc-store",
  "hash": "9d6a0d7d2f3a..."
}

{
  "event_name": "Purchase",
  "event_time": 1776942360,
  "event_id": "bigcommerce_45109",
  "action_source": "website",
  "event_source_url": "https://store.com/checkout/order-confirmation",
  "user_data": {
    "em": ["a8f5f167f44f4964..."],
    "ph": ["c8d96c5a0e9b2c49..."],
    "fbc": "fb.1.1776942000.IwAR3...",
    "client_ip_address": "203.0.113.42",
    "client_user_agent": "Mozilla/5.0 ..."
  },
  "custom_data": {
    "currency": "USD",
    "value": 248.00,
    "storefront_id": "sf_uk_b2c",
    "content_ids": ["SKU-441", "SKU-908"],
    "content_type": "product"
  }
}

Stencil vs Catalyst?

TrackLayer supports both. Stencil storefronts can use the theme script path, while Catalyst storefronts can use the Next.js integration with the BigCommerce GraphQL Storefront API.

Are B2B Edition quote events supported?

Yes. Quote lifecycle events can be normalized separately from checkout purchases, and price-list-aware pricing is included when event destinations support custom fields.

Does it work with headless storefronts on Vercel or Netlify?

Yes. Headless Next.js storefronts can run the TrackLayer script in the app shell and send server-side context from Vercel, Netlify, or any Node-compatible deployment.

How are multi-currency storefronts handled?

TrackLayer keeps the original storefront currency, normalized order value, and storefront identifier together so ad platforms and internal reporting can reconcile each conversion.

Where is BigCommerce data stored?

Workspaces can be provisioned in EU or US regions. Hashed identifiers, consent state, event logs, and destination routing stay aligned with the selected data residency region.