Skip to main content
Request a demo
  1. Home
  2. Integrations
  3. BigCommerce
Upstack Data

BigCommerce integration: every order captured server-side and resolved to a person

Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.

Request a demo Start free trial
Role
Source
Category
E-commerce
Pre-built connectors
34 destinations
Plans
All plans

What Upstack captures

Every BigCommerce event leaves resolved to a person. Captured on the server, resolved to a person, then sent.

In: from BigCommerceWhat it carries
  • order_idBigCommerce order
  • email / phonecheckout contact
  • customer_idBigCommerce customer record
  • productscatalog items on the order
  • total_inc_taxorder value

Storefront and checkout events, resolved.

Upstack DataResolved before it is sent
  • IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
  • customer_typeNew or returning, resolved before send.
  • DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
  • Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Out: to Meta Conversions API1 of 34 destinations
  • em, ph (SHA-256)raise Event Match Quality
  • fbclid / _fbpcredit the click that drove it
  • external_idstable person across sessions
  • event_iddedupe against the browser pixel
  • value / currencyvalue-based bidding

Conversions API with higher Event Match Quality.

See the set-up reference See all 34 destinations How resolution works

About BigCommerce

BigCommerce’s hosted checkout protects you from PCI scope and hides the purchase from browser-side scripts.

Upstack reads the order server-side instead, so the limitation stops mattering, then resolves the customer against the device graph before forwarding. Multi-storefront accounts resolve against one graph rather than per store, so a shopper who buys from two of your regions is one customer everywhere downstream.

What BigCommerce is

BigCommerce is a hosted commerce platform used by mid-market and enterprise merchants who want a storefront and checkout without running the infrastructure themselves.

Its APIs expose the storefront and checkout events that matter for acquisition (cart, checkout and order), which is what makes a clean server-side feed possible.

How BigCommerce works

BigCommerce hosts the storefront and checkout and exposes them through a REST Management API plus a webhook system covering carts, orders and customers. Stores can run headless, with BigCommerce serving as the commerce engine behind a front end you control. Checkout is hosted, which keeps PCI scope down but also limits what a script running in the page can observe at the moment of purchase. The order object (totals, line items, customer) is available server-side regardless of how the storefront was built.

What you can do with it

Three jobs BigCommerce does once it is connected.

01

Capture every order server-side

BigCommerce events are captured from the server rather than the shopper’s browser, so ad blockers and ITP stop deciding which of your conversions get counted. Nothing depends on a script surviving the page.

02

Resolve each event to a person

Every BigCommerce event is matched against a 750M+ device graph before it leaves, so a phone browse and a desktop checkout resolve to one customer rather than two strangers. Returning buyers are recognized as returning.

03

One setup across storefronts

Several BigCommerce storefronts or regions can run under one account, with events resolved against the same graph rather than siloed per store.

Pre-built connectors

BigCommerce forwards to 34 destinations. Connect BigCommerce once. Every destination is already wired.

See all 34 BigCommerce connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for BigCommerce as a source, next to the BigCommerce developer docs.

FAQ

BigCommerce integration questions.

What does Upstack capture from BigCommerce?

Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.

Which plans include the BigCommerce integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which destinations can BigCommerce send to?

34 destinations, including Meta Conversions API, Google Ads Conversions, TikTok Events API, Pinterest, Snapchat and Reddit. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other sources to connect.

See all integrations

Get BigCommerce tracking right.

A 15-minute walkthrough tailored to your stack and channels.

Request a demo Start free trial