Connect RevenueCat with Visitors to attribute in-app purchase and subscription revenue to visitor sessions. See which pages, referrers, UTM campaigns, and devices are driving your sales.
If you manage your own Stripe checkout sessions with RevenueCat (Stripe Billing mode), follow the Stripe docs instead. This guide is for RevenueCat Web Billing where RevenueCat manages the checkout flow.
RevenueCat processes payments through Stripe, so you'll connect your Stripe account in Visitors. Once connected, RevenueCat transactions will automatically appear.
We'll then automatically create a webhook endpoint for your Stripe account and Visitors will begin receiving transaction events — including those from RevenueCat.
With RevenueCat Web Billing, RevenueCat manages the entire checkout flow. This means you can't pass the visitor cookie as Stripe metadata like you would with a custom Stripe Checkout integration.
Instead, Visitors matches the Stripe customer email to a visitor you've identified using visitors.identify(). Since RevenueCat users are typically authenticated before purchasing, this fits naturally into your existing flow.
Call visitors.identify() with the user's email when they log in. Visitors will match their email to RevenueCat purchases automatically.
visitors.identify({
id: "user_123",
email: "jane@example.com",
})When a RevenueCat charge comes through Stripe, Visitors looks up the customer email and attributes the revenue to the matching visitor session.
Learn more about identifying visitors.
If revenue is showing up but not being attributed to visitors:
If you've confirmed all of the above and attribution still isn't working, contact our support team and we'll help diagnose the issue.