Home
Connectors
Skio - Okendo

Skio

Okendo

Send every Skio event to Okendo, server-side

Q: How do I check that Skio events are reaching Okendo?

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

Q: Will a customer be asked twice about one order?

No. One purchase, one request, even when the order is amended.

Q: How long does it take to connect Skio to Okendo?

Most brands are live in under 20 minutes. Once Skio is connected, every destination receives the same resolved events, Okendo included.

Each event is resolved to a person against a 750M+ device graph before it reaches Okendo, so every touchpoint lands against one customer, not a fragment of one.

Request a demo Start free trial

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 Skio event reaches Okendo. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Skio

Capture Skio subscription events server-side, with the first charge distinguished from every renewal that follows it.

See the Skio integration

SkioWhat it sends

subscription_idthe Skio subscription, stable across charges
email / phonesubscriber contact
charge_typefirst charge, renewal, swap or skip
line_itemsproducts on this charge
total / intervalcharge amount and billing cadence

02 Understand

Resolved to one person before it leaves

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

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

03 Activate

Delivered to Okendo

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

See the Okendo integration

OkendoWhat it receives

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

The catch

Review requests fire on every charge unless the first is separated out, so a subscriber is asked to review the same product monthly.

Where to check in OkendoDelivery you can audit

Okendo the review request schedule

checked against the same day's orders.

What changes

What changes when Skio feeds Okendo. Two gains on the Okendo side, two on the Skio side.

Okendo

Server-side delivery

Events reach Okendo through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

Okendo

Identity-resolved events

Events sent to Okendo carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

Skio

Every event, server-side

Storefront and checkout events are captured from Skio on the server, independent of the browser.

Skio

One setup, every destination

Connect Skio once and forward to every ad platform, email tool and warehouse you run.

Setup

Live in under 20 minutes.

Connect Skio once and every destination, Okendo included, is forwarded the same resolved events.

Upstack dashboardExample

Skio Data source Connected

Okendo Destination Healthy

Read the full Okendo setup guide

01

Connect Skio

Capture Skio subscription events server-side, with the first charge distinguished from every renewal that follows it.
02

Add the Okendo destination

Under Destinations, add Okendo. Every resolved Skio event is then forwarded to it.
03

Check delivery to Okendo

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