Recharge to Yotpo
Forward every Recharge event to Yotpo 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 Yotpo with Upstack Data
What changes
What changes when Recharge feeds Yotpo.
Server-side delivery
Events reach Yotpo 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 Yotpo 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 Yotpo needs.
Recharge and Yotpo 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 Yotpo 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
Yotpo receives
- who to ask for the review
- order_id
- which purchase the request is about
- product IDs
- which product is being reviewed
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 Yotpo
YotpoReviewsthe request queue, which should now contain the orders that previously had no email attached.
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 Yotpo.
- ShopifyYotpo
- WooCommerceYotpo
- BigCommerceYotpo
- Checkout ChampYotpo
- Custom stackYotpo
- FunnelishYotpo
- Lasso CommerceYotpo
- Phoenix TechnologiesYotpo
- SkioYotpo
- Loop SubscriptionsYotpo
- StripeYotpo
- Everything Yotpo can take12 sources feed Yotpo, and the setup is the same for each one.Yotpo 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 Yotpo.
A 15-minute walkthrough of this connector on your own account.