BigCommerce to Tatari
Forward every BigCommerce event to Tatari server-side, resolved to a person against a 750M+ device graph — with restored click IDs, deduplicated conversions and delivery you can audit.
Connection
Connect BigCommerce to Tatari with Upstack Data
BigCommerce
Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.
BigCommerce integration
Tatari
Send resolved purchases to Tatari so linear and streaming TV are measured against the same order data as every other channel.
Tatari integrationWhat changes
What changes when BigCommerce feeds Tatari.
Server-side delivery
Events reach Tatari through its server API, not the browser — so ad blockers, ITP and consent banners don’t cost you conversions.
Identity-resolved events
Every event sent to Tatari carries a resolved customer, matched against a 750M+ device graph.
Every event, server-side
Storefront and checkout events are captured from BigCommerce on the server, independent of the browser.
One setup, every destination
Connect BigCommerce once and forward to every ad platform, email tool and warehouse you run.
What actually moves
What BigCommerce carries, and what Tatari needs.
BigCommerce and Tatari describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what BigCommerce can put on an event, the right is what Tatari can actually use.
BigCommerce sends
- order_id
- BigCommerce order
- email / phone
- checkout contact
- customer_id
- BigCommerce customer record
- products
- catalogue items on the order
- total_inc_tax
- order value
Tatari receives
- hashed email / phone
- match a purchase to an exposed household
- ip / user_agent
- household matching for a no-click channel
- order timestamp
- correlate against airing times
- value / currency
- feed the incrementality model revenue
- customer_type
- separate acquisition from repeat purchase
Delivery you can audit
How you know it is working.
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.
Per-event inspection
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.Deduplication
Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.Bot and fraud filtering
Automated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Where to check in Tatari
TatariMeasurementConversions. The conversion feed is the input to the lift model, so its completeness is checked here first.
Related connectors
Other places BigCommerce can send to.
- BigCommerceMeta Conversions API
- BigCommerceGoogle Ads Conversions
- BigCommerceTikTok Events API
- BigCommercePinterest
- BigCommerceSnapchat
- BigCommerceReddit
- BigCommerceMicrosoft Ads
- BigCommerceX
Other sources that feed Tatari.
- ShopifyTatari
- WooCommerceTatari
- Checkout ChampTatari
- RechargeTatari
- Custom stackTatari
- FunnelishTatari
- Lasso CommerceTatari
- Phoenix TechnologiesTatari
- SkioTatari
- Loop SubscriptionsTatari
- StripeTatari
- Everything Tatari can take12 sources feed Tatari, and the setup is the same for each one.Tatari integration
- How resolution worksEvery event matched against a 750M+ device graph before it is forwarded.Upstack Signal
- What it costsThree plans that scale with your order volume. Every connector is on every plan.See pricing
Get BigCommerce talking to Tatari.
A 15-minute walkthrough of this connector on your own account.