Skip to main content
Upstack Data

BigCommerce to Okendo

Forward every BigCommerce event to Okendo server-side, resolved to a person against a 750M+ device graph — so every touchpoint lands against one customer, not a fragment of one.

What changes

What changes when BigCommerce feeds Okendo.

Server-side delivery

Events reach Okendo 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 Okendo 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 Okendo needs.

BigCommerce and Okendo 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 Okendo 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

Okendo receives

email
who to survey
order_id
the purchase in question
product IDs
what to ask about

Delivery you can audit

How you know it is working.

Post-purchase timing is the whole product. These controls exist so requests go to the right person at the right point.

  • Per-order inspection

    Trace any request back to the order and customer it came from.
  • Deduplication

    One purchase, one request — even when the order is amended.
  • Bot and fraud filtering

    Fraudulent orders never enter the request queue.

Where to check in Okendo

Okendothe review request schedule, checked against the same day's orders.

Get BigCommerce talking to Okendo.

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