Home
Connectors
Stripe - Okendo

Stripe

Okendo

Send events from your Stripe-billed app to Okendo

Q: How do I check that Stripe 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 Stripe to Okendo?

Most brands are live in under 20 minutes. Once Stripe events reach Upstack, 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 Stripe event reaches Okendo. Sent from your app, resolved to a person, then forwarded.

01 Capture

Captured from Stripe

For apps that bill through Stripe, send payment and subscription events to Upstack with the Upstack Pixel and JavaScript SDK, resolved to a customer before they reach the tools you spend on.

See the Stripe integration

StripeWhat it sends

subscription_initial_purchaseyou fire it for the first subscription order
subscription_recurring_purchaseon invoice.paid for an existing subscription
payment_succeededmaps to invoice.paid or charge.succeeded
payment_refundedmaps to charge.refunded
amount / currencyamount in cents, with invoiceId and subscriptionId

02 Understand

Resolved to one person before it leaves

Every Stripe 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

Stripe customer records are created per integration path, not per human.

The same buyer paying through a hosted checkout and later through a saved card can produce two records, and neither carries the full purchase history a review request should reference.

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 Stripe feeds Okendo. Two gains on the Okendo side, two on the Stripe 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.

Stripe

Subscription purchases as events

Fire subscription_initial_purchase for the first order and subscription_recurring_purchase each time a renewal is paid, so first orders and renewals are reported separately.

Stripe

Payments and refunds

payment_succeeded, payment_failed and payment_refunded each map to a Stripe event (invoice.paid or charge.succeeded, invoice.payment_failed, charge.refunded), so money events reach Upstack when your app fires them.

Setup

Live in under 20 minutes.

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

Upstack dashboardExample

Okendo Destination Healthy

Read the full Okendo setup guide

01

Install the Upstack Pixel and SDK

Add the Upstack Pixel to your app, then fire the subscription and payment events with the JavaScript SDK when Stripe reports them, such as subscription_recurring_purchase when invoice.paid fires for an existing subscription.
02

Add the Okendo destination

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

Check delivery to Okendo

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