Okendo integration: resolved customers and orders, sent server-side

Send resolved customers and orders to Okendo so review requests reach the right person.

Request a demo Start free trial

Role: Destination
Category: Reviews & support
Pre-built connectors: 12 sources
Plans: All plans

What Upstack sends

Every order reaches Okendo attached to one customer. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources

order_idShopify order and checkout token
email / phonecustomer contact from checkout
customer_idShopify customer record, if they have one
line_itemsproducts, variants and quantities
total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

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 purchase, one request, even when the order is amended.
Bot and fraud filteringFraudulent orders never enter the request queue.

Out: to OkendoOn every event

emailwho to survey
order_idthe purchase in question
product IDswhat to ask about

Review requests that reach the right person.

See the set-up reference See all 12 sources How resolution works

About Okendo

Okendo’s yield is a function of how many orders carry a resolved customer.

Upstack raises that number by matching every order against the device graph before forwarding, so requests reach people who bought on one device and read email on another. Responses then attach to a single customer record rather than a fragment.

What Okendo is

Okendo is a customer-marketing platform centered on reviews, ratings and post-purchase surveys, used heavily by Shopify brands.

The value of a review program is a function of how many of the right customers get asked, which depends on order and identity data being complete.

How Okendo works

Okendo schedules review and survey requests against orders, timed relative to fulfillment, and asks product-specific questions based on what was in the order. Responses attach to a customer record and become attributes that can be segmented on and syndicated back to the storefront and to ad platforms as review content. The program’s yield is a direct function of how many orders carry a usable customer and email.

What you can do with it

Three jobs this connector does inside Okendo.

Send complete conversions

Conversions reach Okendo through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

Optimize on the customer you want

Map any order attribute to the conversion Okendo receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

Ask the right customer

Review requests reach the person who actually bought, matched across the device they bought on and the one they read email on.

Pre-built connectors

12 sources connect to Okendo. Whichever of these you run, Okendo is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for Okendo as a destination, next to the Okendo developer docs.

FAQ

Okendo integration questions.

What does Upstack send to Okendo?

Send resolved customers and orders to Okendo so review requests reach the right person.

How do I check that events are reaching Okendo?

Open Okendo › the review request schedule, checked against the same day's orders.

Which plans include the Okendo integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which sources can send events to Okendo?

12 sources: Shopify, WooCommerce, BigCommerce, Checkout Champ, Recharge, Custom stack, Funnelish, Lasso Commerce, Phoenix Technologies, Skio, Loop Subscriptions and Stripe. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other destinations to send to.

See all integrations

Get Okendo tracking right.

A 15-minute walkthrough tailored to your stack and channels.

Request a demo Start free trial