How do I track Gumroad sales next to my SaaS MRR?
Last updated: November 16, 2026
SoleOS: One dashboard for revenue, traffic and live signals across every app, game and website you run. Start 7-day trial →
From the SoleOS answers series — written about our own product space; grounded in published definitions and documented behavior, never invented numbers.
Gumroad doesn't have subscriptions in the same sense Stripe or RevenueCat do, so there's no MRR field to pull. The honest fix is to treat Gumroad sales as gross revenue events on a separate line, then build one blended "total monthly revenue" view that keeps one-time sales and recurring MRR clearly labeled instead of silently merged.
That sounds like a small distinction, but it's the difference between a dashboard you trust and one that quietly lies to you every time a Gumroad product has a good launch week.
Why Gumroad and MRR don't mix automatically
MRR is a forecasting number. It exists because subscriptions renew on a predictable cadence, so this month's number is a reasonable proxy for next month's, barring churn. A $500 Gumroad week for a one-time ebook or Figma template pack tells you nothing about what next week looks like. If you add that $500 straight into your "MRR" total, you've created a number that looks like it predicts the future but doesn't.
This matters more the bigger your portfolio gets. A founder running one SaaS and one Gumroad product can eyeball the difference. A founder running two SaaS apps, a Gumroad store, and an app-store product needs the tool to keep the categories separate for them, because manual mental math breaks down past three or four revenue sources.
Set up two tracks, not one blended number
Track 1: Recurring revenue (MRR/ARR) This is Stripe, RevenueCat, Paddle, or Play/App Store subscriptions — anything with a renewal cycle. This is the number you use for growth rate, churn, and projections.
Track 2: One-time / gross sales revenue This is Gumroad, Lemon Squeezy one-time purchases, physical merch, or anything bought once with no renewal. You still want to see this on a monthly basis (revenue per calendar month), but label it distinctly — "Gumroad gross sales," not "Gumroad MRR."
Then build a combined view for the number that actually matters to your bank account: total revenue this month, which is Track 1 + Track 2. That's your real cash picture. Just don't use it to compute a growth rate as if it were all recurring — a single viral Gumroad day will make your "MRR growth" look fake-good, and the following flat month will look like churn that never happened.
If you want the formula-level detail on what counts as MRR versus gross revenue and where the edge cases live (refunds, trials, proration), the metrics dictionary spells out exact definitions and the caveats around each one.
Pulling Gumroad data in practice
Gumroad has a sales API and CSV export, but it isn't in SoleOS's connector list today — the current metrics connectors cover Stripe, RevenueCat, PostHog, GA4, Search Console, Bing Webmaster, App Store Connect, and Google Play, with AdMob planned. For Gumroad specifically, your options right now are:
- Manual monthly entry. Pull the Gumroad sales total once a month and log it as a one-time revenue line next to your subscription numbers. Tedious at scale, fine if Gumroad is a minor line in your portfolio.
- CSV import into a spreadsheet alongside your subscription exports, until a direct integration exists. This is slower but keeps you from mixing categories by accident.
- Watch for native support if Gumroad tracking matters enough to your portfolio that manual entry is costing you real time each month.
Whatever you choose, the principle doesn't change: keep the one-time number visibly separate from the recurring number, even if they live in the same spreadsheet tab or dashboard screen.
What "total portfolio revenue" should actually show you
Once you have both tracks, the useful view for a multi-product founder is per-project rows with two columns: recurring (with growth rate) and one-time (with raw total), plus a portfolio sum at the bottom. This lets you answer two different questions correctly:
- "Is my subscription business actually growing?" — look at Track 1 only.
- "How much did I make this month across everything?" — look at Track 1 + Track 2.
This is the same discipline that applies when mixing Stripe and RevenueCat data, or when adding ad revenue from AdMob — anything that isn't a renewing subscription needs its own lane so it doesn't distort the trend line everyone actually cares about.
When you don't need a tool for this at all
If Gumroad is a side hustle generating a few hundred dollars a quarter next to one real SaaS, a spreadsheet with two tabs is genuinely enough — don't reach for a dashboard tool to solve a problem a 10-minute monthly CSV pull already solves. SoleOS vs a spreadsheet covers roughly where that line tends to sit for most solo founders: it's usually somewhere around three-plus revenue sources or multiple products, not one.
Disclosure: SoleOS is a portfolio dashboard built by its own founder, so naturally this post leans toward "track things separately in one place" — take that bias as a given.
Frequently asked questions
Should I ever count Gumroad sales toward MRR?
No. MRR should only include revenue you have reasonable confidence will recur next month under the current subscription terms. A one-time purchase, regardless of size, breaks that assumption and will distort your growth rate the month it spikes and again the month after when it reverts.
What if I sell a Gumroad subscription product?
Gumroad does support recurring billing for some products (membership-style offers). If you're using that feature, that revenue behaves like real MRR and can reasonably sit in Track 1, not Track 2 — the distinction is about renewal behavior, not which platform processed the payment.
How often should I pull Gumroad numbers manually?
Monthly is usually enough for portfolio-level tracking, right after you close the books on your subscription revenue for the same period. If Gumroad is a meaningful chunk of revenue (say, 20%+ of total), weekly pulls make the picture current enough to act on.
Does this same logic apply to Lemon Squeezy or Paddle one-time sales?
Yes — any payment processor that sells both subscriptions and one-time products needs the same split. Paddle's own subscription revenue slots into Track 1 the same way Stripe's does; see tracking Paddle revenue alongside other apps for the processor-specific details, if that's part of your stack too.
Can I see what this looks like before connecting real accounts?
Yes — the live demo uses sample data so you can see how recurring and one-time revenue get separated in a multi-project view without signing up or connecting anything.