Skip to main content
  1. Home
  2. Connectors
  3. BigCommerce - X
BigCommerce X

Send every BigCommerce event to X, server-side

Each event is resolved to a person against a 750M+ device graph before it reaches X, with restored click IDs, deduplicated conversions and delivery you can audit.

US device IDs in the graph
750M+
Match rate on events
90%+
Identity window, per customer
Lifetime
Most brands are live
<20 min

How it flows

How a BigCommerce event reaches X. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from BigCommerce

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

See the BigCommerce integration
BigCommerceWhat it sends
  • order_idBigCommerce order
  • email / phonecheckout contact
  • customer_idBigCommerce customer record
  • productscatalog items on the order
  • total_inc_taxorder value

02 Understand

Resolved to one person before it leaves

Every BigCommerce event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.

How resolution works
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.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

03 Activate

Delivered to X

Server-side conversions to the X Conversions API, resolved to a person and deduplicated against the browser pixel.

See the X integration
XWhat it receives
  • hashed email / phoneidentity matching on arrival
  • twclidcredit the click that drove it
  • external_idstable person across sessions
  • event_iddedupe against the browser pixel
  • value / currencyvalue-based bidding

The catch

BigCommerce's hosted checkout limits what a browser tag can see at the moment of purchase, which is exactly the moment that matters for conversion tracking.

Where to check in XDelivery you can audit

X Ads Tools Events Manager

The events table separates browser and server events, so a deduplicated pair shows as one conversion.

What changes

What changes when BigCommerce feeds X. Two gains on the X side, two on the BigCommerce side.

X

Server-side delivery

Events reach X through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

X

Identity-resolved events

Events sent to X carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

BigCommerce

Every event, server-side

Storefront and checkout events are captured from BigCommerce on the server, independent of the browser.

BigCommerce

One setup, every destination

Connect BigCommerce once and forward to every ad platform, email tool and warehouse you run.

Setup

Live in under 20 minutes.

Connect BigCommerce once and every destination, X included, is forwarded the same resolved events.

Upstack dashboardExample
BigCommerce Data source Connected
X Destination Healthy
Read the full X setup guide
  1. 01

    Connect BigCommerce

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

  2. 02

    Add the X destination

    Under Destinations, add X. Every resolved BigCommerce event is then forwarded to it.

  3. 03

    Check delivery to X

    Every conversion is inspectable from the moment it fires to the moment the platform confirms it.

FAQ

Questions about BigCommerce and X.

How do I check that BigCommerce events are reaching X?

Open X Ads › Tools › Events Manager. The events table separates browser and server events, so a deduplicated pair shows as one conversion.

Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

How long does it take to connect BigCommerce to X?

Most brands are live in under 20 minutes. Once BigCommerce is connected, every destination receives the same resolved events, X included.

Related connectors

See all 408 connectors

Get BigCommerce talking to X.

A 15-minute walkthrough of this connector on your own account.

21-day free trial, no card. Month to month.