Custom stack to Okendo
Forward every Custom stack 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.
Connection
Connect Custom stack to Okendo with Upstack Data
Custom stack
Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.
Custom stack integrationOkendo
Send resolved customers and orders to Okendo so review requests reach the right person.
Okendo integrationWhat changes
What changes when Custom stack 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.
Any stack, any framework
Headless, custom checkout, native app or a platform we haven’t listed — if it can make an HTTP request, it can send to Upstack.
The same event schema
Custom events are resolved, filtered and forwarded exactly like a Shopify order.
What actually moves
What Custom stack carries, and what Okendo needs.
Custom stack and Okendo describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Custom stack can put on an event, the right is what Okendo can actually use.
Custom stack sends
- event_name
- whatever you choose to call it
- user identifiers
- any of email, phone, external ID
- value / currency
- if the event carries revenue
- custom properties
- any attribute in your own schema
Okendo receives
- 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.
Related connectors
Other places Custom stack can send to.
- Custom stackMeta Conversions API
- Custom stackGoogle Ads Conversions
- Custom stackTikTok Events API
- Custom stackPinterest
- Custom stackSnapchat
- Custom stackReddit
- Custom stackMicrosoft Ads
- Custom stackX
Other sources that feed Okendo.
- ShopifyOkendo
- WooCommerceOkendo
- BigCommerceOkendo
- Checkout ChampOkendo
- RechargeOkendo
- FunnelishOkendo
- Lasso CommerceOkendo
- Phoenix TechnologiesOkendo
- SkioOkendo
- Loop SubscriptionsOkendo
- StripeOkendo
- Everything Okendo can take12 sources feed Okendo, and the setup is the same for each one.Okendo 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 Custom stack talking to Okendo.
A 15-minute walkthrough of this connector on your own account.