- 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 Vibe. 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 orderemail / phonecheckout contactcustomer_idBigCommerce customer recordproductscatalog items on the ordertotal_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 →
Resolved 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.
03 Activate
Delivered to Vibe
Send resolved conversions to Vibe so streaming TV campaigns are attributed to the orders they drove.
See the Vibe integration →
VibeWhat it receives hashed email / phonematch a purchase to an exposed householdip / user_agenthousehold matching for a no-click channelorder timestampplace the order inside the campaign windowvalue / currencymeasure streaming on revenueevent_iddedupe against site-side reporting
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 VibeDelivery you can audit
Vibe › Campaigns › Conversions
Matched conversions report the campaign window they were attributed inside.
What changes
What changes when BigCommerce feeds Vibe. Two gains on the Vibe side, two on the BigCommerce side.
Vibe
Server-side delivery
Events reach Vibe through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
Vibe
Identity-resolved events
Events sent to Vibe 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, Vibe included, is forwarded the same resolved events.
Upstack dashboardExample
BigCommerce Data source Connected
Vibe Destination Healthy
Read the full Vibe setup guide → -
01
Connect BigCommerce
Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.
-
02
Add the Vibe destination
Under Destinations, add Vibe. Every resolved BigCommerce event is then forwarded to it.
-
03
Check delivery to Vibe
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.
FAQ
Questions about BigCommerce and Vibe.
How do I check that BigCommerce events are reaching Vibe?
Open Vibe › Campaigns › Conversions. Matched conversions report the campaign window they were attributed inside.
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 Vibe?
Most brands are live in under 20 minutes. Once BigCommerce is connected, every destination receives the same resolved events, Vibe included.