- 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 Sendlane. 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.- DeduplicationOne order produces one event, so a single purchase cannot trigger the same flow twice.
- Bot and fraud filteringAutomated traffic never becomes a profile, so list quality and deliverability are not paying for it.
03 Activate
Delivered to Sendlane
Forward resolved customer events to Sendlane for retention and lifecycle flows.
See the Sendlane integration →
SendlaneWhat it receives email / phonecontact key across email, SMS and reviewsevent propertiesautomation triggersorder valueattribution
Which events reach Sendlane
Each Upstack event is mapped to the Sendlane event below before it is sent.
| Upstack event | Sent to Sendlane as | Key data on the event |
| Product view | product-viewed-upstackified | product_id, product_name, product_img_url, variant_id |
| Add to cart | added-to-cart-upstackified | line_items, subtotal, total, currency |
| Checkout | checkout-started-upstackified | checkout_id, line_items, subtotal, total, currency |
| Purchase | order-placed-upstackified | order_id, line_items, total, currency, discounts |
Upstack looks up each contact in Sendlane by email or Sendlane contact ID, and sends the event only if the contact already exists.
The catch
Storefront browse events and the hosted checkout are effectively two contexts.
Without resolution the same shopper appears in each as a different person.
Where to check in SendlaneSending you can audit
Sendlane › the contact record
where the event should appear against one person rather than creating a second contact.
What changes
What changes when BigCommerce feeds Sendlane. Two gains on the Sendlane side, two on the BigCommerce side.
Sendlane
Server-side delivery
Upstack sends events to Sendlane from its servers only, so ad blockers and browser privacy settings can’t block delivery.
Sendlane
Identity-resolved events
Events sent to Sendlane 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.
You need a Sendlane account where you can generate an API Access Token and create a Custom Integration.
Upstack dashboardExample
BigCommerce Data source Connected
Sendlane Destination Healthy
Read the full Sendlane setup guide → -
01
Connect BigCommerce
Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.
-
02
Add the Sendlane destination
Under Destinations, add Sendlane with two credentials: an API Access Token from Settings, API, and the Integration Token from a new Custom Integration under Integrations in Sendlane.
-
03
Check the contact’s activity feed
Trigger a test action on your store, such as adding a product to cart, and check the contact’s activity feed in Sendlane. Events are sent only for contacts that already exist in Sendlane.
FAQ
Questions about BigCommerce and Sendlane.
What happens if a contact doesn’t exist in Sendlane?
Upstack only sends events for contacts that already exist in Sendlane. If the visitor’s email isn’t found in your account, the event is skipped, which keeps your account clean and targets only real subscribers.
Which events does Sendlane receive?
ViewContent as product-viewed-upstackified, AddToCart as added-to-cart-upstackified, InitiateCheckout as checkout-started-upstackified and Purchase as order-placed-upstackified.
Which customer parameters are sent to Sendlane?
Upstack looks up each contact in Sendlane by email or Sendlane contact ID, and sends the event only if the contact already exists.
How do I check that BigCommerce events are reaching Sendlane?
Trigger a test action on your store, such as adding a product to cart, and check the contact’s activity feed in Sendlane. Events are sent only for contacts that already exist in Sendlane.
How long does it take to connect BigCommerce to Sendlane?
Most brands are live in under 20 minutes. Once BigCommerce is connected, every destination receives the same resolved events, Sendlane included.