RevenueCat integration
RevenueCat MRR combined with Stripe, without double counting
If you sell on the web through Stripe and in your app through RevenueCat, no billing dashboard shows your real MRR. Joinsight combines both, counts a shared subscription once and keeps the web and mobile split.
No card required. The trial clock starts when your first revenue source connects.
What Joinsight answers with RevenueCat
- Combined MRR across web and mobile, with the split by source
- One customer per person when the same user pays on web and mobile, with MRR summed
- Trials started and new MRR next to App Store page views and downloads
- Which web pages and campaigns led to mobile subscriptions, when your app calls identify() with the same user ID
What it reads
- Subscriptions and customers through a RevenueCat API v2 secret key and project ID
- Webhook events for renewals, cancellations and billing issues, as they happen
- The Stripe subscription ID RevenueCat stores, to deduplicate subscriptions billed on the web
Good to know
- MRR is gross, before App Store and Google Play fees.
- RevenueCat's charts API is rate limited, so some historical figures are pulled nightly in batches.
Setup
- Create an API v2 secret key in RevenueCat and copy your project ID.
- Paste both in Joinsight. Subscription history is imported on connect.
- Add the webhook URL and Authorization header shown on the card to RevenueCat's webhook settings.
- Use the same user ID in RevenueCat, Stripe metadata and identify() so one person stays one customer.
Questions
How does deduplication work?
A subscription visible in both Stripe and RevenueCat counts once, from Stripe, matched on the Stripe subscription ID that RevenueCat stores. A person paying on web and mobile is one customer when user IDs match.
Do I need Stripe to use RevenueCat with Joinsight?
No. A mobile-only app can connect RevenueCat alone, plus App Store Connect and Search Console for the store and web side.
Works well with
- Stripe
Connect Stripe with a read-only restricted key and see which landing pages, Search Console queries and channels brought your paying customers, next to accurate MRR and movements.
- Google Search Console
Join Google Search Console with Stripe and RevenueCat to see revenue per landing page and modeled revenue per query, plus keyword opportunities ranked by what they could earn.
See what makes you money.
Connect Stripe or RevenueCat and Search Console, and you see combined MRR and 16 months of search history on day one. Page and keyword revenue follow as the snippet collects first touches.
No card required. The trial clock starts when your first revenue source connects.