CONNECTIONS / BigCommerce
BigCommerce orders, delivered from any storefront.
BigCommerce's native Meta and Google sales channels cover pixel-based tracking for a single storefront. Signals adds server-side delivery to every platform you buy on, works the same way across headless storefronts, and turns customer lists into hashed audiences.
- ● bigcommerce :: signals live
- > Order placed value=482.00 USD
- > Checkout started step=shipping
- hash sha256(email,phone) pii=cleared
- route meta · google · tiktok · pinterest · reddit
- ✓ 5 destinations synced · match 81%
The signal BigCommerce yields.
Every kind of signal that moves between BigCommerce and the platforms, through one hashed, deduplicated route.
- Web conversions
- Every checkout a BigCommerce storefront completes, Stencil or headless, reaches Meta, Google, TikTok, Pinterest, and Reddit server-side, deduped against whichever pixel is already installed.
- Offline conversions
- In-store, phone, and wholesale orders that never touch the online checkout post as offline conversions, matched by hashed identifier instead of a click.
- Custom audiences
- A refunded or partially credited order is reconciled against the original event so reported revenue reflects what was actually kept.
Pick your platform. Every use case for it, in one place.
Every way BigCommerce data moves, grouped by platform and ranked by how many use cases BigCommerce supports.
Google 4 
Meta 4 
Snap 3 
TikTok 3 
LinkedIn 2 
OpenAI 2 
Pinterest 1 
Reddit 1 
X 1 - Web conversions Google Enhanced Conversions Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Web conversions Meta Conversions API Web events delivered as conversions, matched with hashed identifiers.
- Web conversions Meta Messenger Conversions API Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Web conversions Snapchat Conversions API Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Web conversions TikTok Events API Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
From authorization to delivered signal.
-
Install
Signals app installed from the BigCommerce marketplace with a scoped API-account token covering orders, checkout, and customer events, on a Stencil or headless storefront.
-
Map
Order, checkout, and customer events mapped to each destination's event or audience schema in the visual mapper, including offline and refund events where they apply.
-
Hash and dedupe
Identifiers hashed with SHA-256 and deduped against any existing pixel or tag before anything leaves BigCommerce.
-
Deliver
Server-side delivery to every mapped destination, verified in the live debugger before campaigns rely on it.
BigCommerce questions, answered.
Do we remove BigCommerce's native Meta and Google sales channels?
No. Keep them for catalog listings and basic pixel coverage on a single storefront. Signals adds server-side delivery to every platform you buy on, offline and in-store revenue, and audience sync on top, deduped against whatever pixel is already installed so nothing double counts.
Does this work with a headless BigCommerce storefront, like one built on Catalyst?
Yes. Headless storefronts built on the GraphQL Storefront API or a Catalyst frontend send order and checkout events through the same server-side path as a Stencil theme, since capture reads from BigCommerce's order and webhook data rather than a theme script, so there is no tracking pixel to reattach after a rebuild.
We run BigCommerce's Multi-Storefront feature. Does each storefront route separately?
Yes. Each storefront carries its own channel ID, so orders and checkouts from one storefront can route to different ad accounts and destinations than another storefront sharing the same catalog, without any extra configuration on BigCommerce's side or a second app install per storefront.
Will a custom checkout built on the Checkout SDK still fire events?
Yes. Capture reads from BigCommerce's order and checkout webhook data rather than a script embedded in the checkout page, so a custom Checkout SDK build fires the same events a default checkout would, and a checkout redesign does not require remapping anything.
Are refunds reported back to the ad platforms?
Where a destination supports it, yes. A refunded order is reconciled against the original event so reported revenue reflects what was actually kept, not what was briefly charged at checkout, whether the refund is full, partial, or issued days after the original purchase.
NEXT STEP
See your BigCommerce data working in every ad platform.
Ready to enable a use case, or still mapping what BigCommerce data could do? Our team helps you find the right place to start.
