- 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 Yotpo. 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 ordersubscription_recurring_purchaseon invoice.paid for an existing subscriptionpayment_succeededmaps to invoice.paid or charge.succeededpayment_refundedmaps to charge.refundedamount / 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.
03 Activate
Delivered to Yotpo
Enrich post-purchase touchpoints in Yotpo with identity-resolved order data.
See the Yotpo integration →
YotpoWhat it receives emailwho to ask for the revieworder_idwhich purchase the request is aboutproduct IDswhich product is being reviewed
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 YotpoDelivery you can audit
Yotpo › Reviews › the request queue
which should now contain the orders that previously had no email attached.
What changes
What changes when Stripe feeds Yotpo. Two gains on the Yotpo side, two on the Stripe side.
Yotpo
Server-side delivery
Events reach Yotpo through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
Yotpo
Identity-resolved events
Events sent to Yotpo 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, Yotpo included, is forwarded the same resolved events.
Upstack dashboardExample
Yotpo Destination Healthy
Read the full Yotpo 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 Yotpo destination
Under Destinations, add Yotpo. Every resolved Stripe event is then forwarded to it.
-
03
Check delivery to Yotpo
Trace any request back to the order and customer it came from.
FAQ
Questions about Stripe and Yotpo.
How do I check that Stripe events are reaching Yotpo?
Open Yotpo › Reviews › the request queue, which should now contain the orders that previously had no email attached.
Will a customer be asked twice about one order?
No. One purchase, one request, even when the order is amended.
How long does it take to connect Stripe to Yotpo?
Most brands are live in under 20 minutes. Once Stripe events reach Upstack, every destination receives the same resolved events, Yotpo included.