Can RevenueCat track my Stripe subscriptions?

Yes — but for a specific case: RevenueCat's Stripe integration treats Stripe as another store for ONE app, so a single product can sell web and mobile subscriptions under one entitlement system. It does not give you a portfolio view of a separate SaaS plus separate apps; for that you need a spreadsheet, a warehouse, or an aggregator that treats both as first-class sources.

How do I see web and mobile revenue in one dashboard?

Four real options: keep two dashboards and reconcile in your head (fine at 1–2 products); maintain a spreadsheet (free, roughly 1–3 hours per product per month, goes stale); build a warehouse pipeline with Airbyte/Fivetran into BigQuery (powerful, days of setup, most catalogs lack a RevenueCat connector); or use an aggregator that ingests both Stripe and RevenueCat natively.

Why don't Stripe and RevenueCat MRR match?

Because they measure different things: timezone bucketing differs (Stripe uses your account timezone), MRR definitions differ (a normalized sum of active subscriptions versus RevenueCat's own MRR metric), trials are counted differently, refunds land on different days than their charges, and app-store proceeds are net of the store's commission while Stripe reports gross. A few percent of drift is normal; document which number is your source of truth per product.

Do I need a data warehouse to combine Stripe and RevenueCat?

Only if you want custom SQL-level analysis. A warehouse pipeline costs roughly $10–100/month at indie volumes plus days of setup and ongoing maintenance, and most ELT catalogs have no RevenueCat source, so mobile revenue means custom API scripts. For 'which of my products is growing', a spreadsheet or an aggregator gets there with a fraction of the effort.

How to track Stripe and RevenueCat together

Last updated: July 22, 2026

By Matheus Mello, solo founder at Quantivo AI — a SaaS billed through Stripe and 10 subscription apps in RevenueCat, so this split-brain problem is my daily life, not a thought experiment.

If you sell anything on the web andanything in the app stores, your revenue lives in two systems that don’t talk to each other: Stripe knows about your SaaS, RevenueCat knows about your apps, and neither dashboard will ever show you the whole business. Search for a fix and you’ll mostly find RevenueCat’s own docs — which solve a differentproblem than the one most multi-product founders have. Let’s split them properly.

First: which problem do you actually have?

Problem A — one product, two platforms. Your single app should sell subscriptions on iOS, Android, andthe web, with one entitlement system. That’s exactly what RevenueCat’s Stripe integration is for: Stripe becomes another “store” inside your RevenueCat project. If that’s you, close this tab and follow their docs — it’s the right tool and you don’t need anything else.

Problem B — separate products. A SaaS billed through Stripe and apps monetized through RevenueCat, and you want one honest answer to “how is the whole portfolio doing?” RevenueCat’s integration doesn’t do this — it aggregates stores within one project, not projects within one business. Problem B is what the rest of this guide is about.

Option 1: two dashboards and your head

Genuinely fine at one or two products. The failure mode isn’t accuracy — it’s cadence. Numbers you check “when you remember” change no decisions, and the product you check less becomes the product you quietly abandon. If you stay here, put a fixed weekly review slot on the calendar.

Option 2: the spreadsheet

Free, infinitely flexible, and honest work: exporting or hand-copying Stripe and RevenueCat figures runs about 1–3 hours per product per month, and the sheet is stale the day after you update it. At one or two products that’s a fair trade — we published a free portfolio-tracker template (no email wall) and an honest breakdown of when the sheet is the right choice. At three-plus products, the ritual gets skipped the first busy week and the sheet dies. Mine did.

Option 3: the warehouse

Airbyte or Fivetran into BigQuery, Looker Studio on top. Real power, real costs: roughly $10–100/month at indie volumes, days of initial setup, SQL modeling of MRR from raw Stripe tables (subscriptions, invoices, prorations — genuinely tricky), and one detail the pipeline brochures skip: most ELT catalogs have no RevenueCat source, so your mobile revenue arrives via custom API scripts you now maintain. Right choice if you’re a data-engineer-at-heart founder who wants custom analysis; a part-time job if you just want to know which product is growing.

Option 4: an aggregator with both as first-class sources

Full disclosure: I build SoleOS, so grade this section accordingly. SoleOS connects Stripe (OAuth) and RevenueCat (OAuth, read-only scopes) as equal sources — each product gets one source of truth, and the portfolio view ranks all of them by what needs attention, with traffic and search data alongside the money. From $19/month, 7-day trial, and the demo is the real dashboard on sample data. Who should notbuy it: one-product founders (Problem A — use RevenueCat’s integration), anyone needing dunning depth on a single SaaS (see our honest Baremetrics comparison), and non-USD-primary businesses for now — we don’t convert currencies yet, and our metrics dictionary says so in writing.

Why the two numbers will never match exactly

Whichever option you pick, Stripe-side and RevenueCat-side figures will disagree a little — not because either is wrong, but because they measure different things. The five causes that explain nearly every discrepancy I’ve chased:

Cause	What you’ll see	What to do
Timezone bucketing	Daily numbers shift by up to a day between dashboards	Stripe buckets by your account timezone; most aggregators (SoleOS included) bucket by UTC. Compare weeks, not days.
MRR definition	The two MRR figures disagree by a few percent	A normalized sum of active subscriptions (yearly ÷ 12) is not RevenueCat's smoothed MRR metric. Pick one definition per product and write it down.
Trials	One dashboard counts a subscriber the other doesn't	RevenueCat tracks active trials as their own metric; trialing Stripe subscriptions shouldn't count toward MRR. Never compare subscriber counts without excluding trials on both sides.
Refund timing	Gross revenue dips on days with no visible cancellations	Refunds land on the refund day, not the original charge day. Reconcile monthly totals, not daily ones.
Proceeds vs gross	App revenue looks ~15–30% lower than expected	Apple and Google report developer proceeds (their commission already removed); Stripe reports gross before fees. Label the columns; never sum them as if they were the same unit.

Rule of thumb from living with both systems: a low-single-digit percentage of drift is normal and not worth chasing; document which system is the source of truth for each product and reconcile monthly totals, never daily ones.

The decision in one paragraph

One product needing web checkout: RevenueCat’s Stripe integration, done. One or two separate products: two dashboards or the free template, with a calendar slot. Data-engineer founder wanting custom SQL: warehouse, eyes open about the RevenueCat gap. Three-plus products and the question is “where does my attention go this week”: that’s the job aggregators exist for — mine or anyone’s.