Recharge to Okendo
Forward every Recharge 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 Recharge to Okendo with Upstack Data
Recharge
Bring subscription events into the same resolved customer — new subscriptions, renewals, churn and reactivation.
Recharge integrationOkendo
Send resolved customers and orders to Okendo so review requests reach the right person.
Okendo integrationWhat changes
What changes when Recharge 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.
Subscriptions as their own conversion
Send new subscriptions to the ad platforms as a distinct event, not lumped in with one-time orders.
Renewals counted properly
Recurring charges are forwarded as real revenue, so LTV reporting reflects what the customer is actually worth.
What actually moves
What Recharge carries, and what Okendo needs.
Recharge and Okendo describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Recharge can put on an event, the right is what Okendo can actually use.
Recharge sends
- subscription_id
- the subscription, not the order
- charge_id
- each recurring charge
- email / phone
- subscriber contact
- status
- active, cancelled, paused, reactivated
- is_first_charge
- new subscription versus renewal
- product / frequency
- what they subscribed to and how often
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 Recharge can send to.
- RechargeMeta Conversions API
- RechargeGoogle Ads Conversions
- RechargeTikTok Events API
- RechargePinterest
- RechargeSnapchat
- RechargeReddit
- RechargeMicrosoft Ads
- RechargeX
Other sources that feed Okendo.
- ShopifyOkendo
- WooCommerceOkendo
- BigCommerceOkendo
- Checkout ChampOkendo
- Custom stackOkendo
- 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 Recharge talking to Okendo.
A 15-minute walkthrough of this connector on your own account.