Home
Connectors
Recharge - Okendo

Okendo

Send every Recharge event to Okendo, server-side

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

Most brands are live in under 20 minutes. Once Recharge 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 Recharge event reaches Okendo. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Recharge

Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.

See the Recharge integration

RechargeWhat it sends

subscription_idthe subscription, not the order
charge_ideach recurring charge
email / phonesubscriber contact
statusactive, cancelled, paused, reactivated
is_first_chargenew subscription versus renewal
product / frequencywhat they subscribed to and how often

02 Understand

Resolved to one person before it leaves

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

A subscriber has many charges and one relationship.

Keying post-purchase messaging off charges rather than the subscription means asking the same person for a review every month.

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

Recharge

Subscriptions as their own conversion

Send new subscriptions to the ad platforms as a distinct event, not lumped in with one-time orders.

Recharge

Renewals counted properly

Recurring charges are forwarded as real revenue, so LTV reporting reflects what the customer is actually worth.

Setup

Live in under 20 minutes.

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

Upstack dashboardExample

Recharge Data source Connected

Okendo Destination Healthy

Read the full Okendo setup guide

01

Connect Recharge

Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.
02

Add the Okendo destination

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

Check delivery to Okendo

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