How do I see Dodo Payments revenue in a portfolio dashboard?
Last updated: November 18, 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.
Dodo Payments is a merchant-of-record checkout built for indie and small SaaS founders, but as of now it isn't on the native connector list of most portfolio dashboards — including SoleOS. The practical path today is to export or pipe Dodo's revenue into a tool that already has a generic ingestion method, or track it manually in a spreadsheet alongside your other apps until a native integration exists. None of this requires giving up on a unified view — it just takes one extra step.
Why Dodo isn't a one-click connector (yet)
Most portfolio tools build native connectors in order of demand: Stripe and RevenueCat first because they cover the overwhelming majority of indie SaaS and mobile subscription revenue, then analytics (GA4, PostHog) and app store consoles. Dodo Payments is newer and growing fast among solo founders who want merchant-of-record tax handling without Stripe Tax complexity, but its install base is still small enough that most dashboards — SoleOS included — haven't built a direct OAuth connector for it.
That's a temporary gap, not a permanent one. The question is what to do in the meantime.
Option 1: Check if Dodo has a Stripe-compatible export
Some merchant-of-record platforms let you export transaction data in a CSV format close enough to Stripe's that you can hand-massage it into a spreadsheet import, or route it through a middleware tool. Check Dodo's dashboard for:
- A CSV or API export of settled transactions, refunds, and subscription status
- Webhook support (most MoR platforms have this) that you could pipe into a lightweight database like Supabase, which several portfolio tools — SoleOS among them — do connect to as a general-purpose data source
- Any existing Zapier/Make integration that could forward revenue events somewhere more connectable
If Dodo supports webhooks into Supabase or a similar store, you can effectively build your own bridge: Dodo → webhook → Supabase table → portfolio dashboard reads Supabase. It's more setup than a native OAuth click, but it means you're not maintaining numbers by hand every week.
Option 2: Manual entry as a bridge, not a forever-solution
If you run one or two apps on Dodo and the rest on Stripe or RevenueCat, the fastest fix is simply logging Dodo's monthly revenue number into a spreadsheet row next to the auto-synced numbers from your other tools. This isn't elegant, but it's honest: a once-a-month five-minute task beats no visibility at all. If you want a starting structure for this instead of building one from scratch, SoleOS vs a spreadsheet (free template) covers the tradeoffs of this exact approach — when a spreadsheet is genuinely enough and when it starts to break down as you add products.
The failure mode to watch for: manual entry quietly stops happening once you're six weeks into an app that matters less this quarter. If you go this route, put a recurring calendar reminder on it, not a mental note.
Option 3: Ask directly, and watch connector lists
Every portfolio tool's connector roadmap is driven by what founders actually ask for. If you use Dodo and want it in a dashboard, the fastest way to make that happen is to tell the vendor directly — support inboxes get weighted by request volume more than you'd think for a tool built by a small team. You can see what SoleOS connects to (scopes + revocation) for the current state of connectors and what's planned next; AdMob, for instance, is listed as planned rather than live, which gives you a sense of how these lists evolve.
What matters more than the connector itself
Whichever bridge you use, the numbers worth getting right are the same ones you'd want from any revenue source:
- Gross vs net. Merchant-of-record platforms like Dodo typically remit revenue after handling tax collection, which changes what "revenue" means compared to a raw Stripe charge. Decide up front whether your portfolio view should show gross transaction value or your net payout, and be consistent across every product so cross-app comparisons aren't distorted.
- Refunds and disputes. These should decrement the same month's revenue, not get buried in a separate report you check quarterly.
- Currency. If Dodo settles in a currency different from your base reporting currency, pick a conversion approach (spot rate at settlement vs a monthly average) and stick with it — swapping methods mid-year makes trend lines lie.
- Cadence. Decide if you're tracking daily, weekly, or monthly figures. If you're combining a manually-updated Dodo number with auto-synced Stripe/RevenueCat data, monthly cadence is usually the only one you can keep honest without automation.
For a rundown of how to define these consistently once you do have multiple revenue sources flowing into one place, the metrics dictionary (exact formulas + caveats) spells out exactly what counts as MRR, net revenue, and how refunds factor in — useful even if you're building the bridge yourself rather than using a specific tool.
If you already mix Stripe or RevenueCat with another processor
If Dodo is one of several payment rails in your portfolio — say Stripe for web and RevenueCat for mobile subscriptions — the harder problem isn't Dodo specifically, it's reconciling multiple revenue definitions into one number you trust. We've written about this exact pattern in tracking Stripe and RevenueCat together, and the same principles (pick one source of truth per product, don't double-count trial conversions, decide on gross vs net once) apply directly to adding a third processor like Dodo into the mix.
Where SoleOS fits, honestly
SoleOS is portfolio intelligence for multi-product founders, and this post is written by the team building it — that's a disclosure, not a pitch. Dodo Payments is not a native connector today; Stripe and RevenueCat are, along with PostHog, GA4, Search Console, Bing Webmaster, App Store Connect, Google Play, Firebase, and Supabase. If your portfolio runs entirely on Dodo with no other connected source, SoleOS won't give you much value yet beyond what you'd get from a spreadsheet — don't pay for a dashboard that can't see your main revenue stream. If you run a mix — some apps on Stripe, some on RevenueCat, one experimental product on Dodo — a Supabase bridge plus the connected sources at least gets you most of the picture automatically, with Dodo as the one row you still fill in by hand. You can see this kind of mixed setup in the live demo (sample data, no sign-up), or compare the full approach in real numbers from a 10-app portfolio.
Frequently asked questions
Does Dodo Payments have its own analytics dashboard?
Yes, Dodo provides its own merchant dashboard with transaction and subscription data, similar to Stripe's dashboard. The question this post addresses is specifically about combining that data with revenue from your other products in one unified portfolio view, since Dodo's own dashboard only shows Dodo.
Will SoleOS add a native Dodo Payments connector?
Connector priority is driven by demand and the connector itself is nontrivial to build well — proper OAuth scoping, revocation, and consistent net-revenue handling take real engineering time. Check what SoleOS connects to (scopes + revocation) for the current list and ask support@soleos.app directly if Dodo matters to your portfolio; that's genuinely how these decisions get prioritized.
Can I use Supabase as a workaround for any payment processor without a native connector?
Yes, this is one of the more useful patterns for founders on niche or regional payment rails. If the processor supports webhooks, you can forward events into a Supabase table and connect that table as a signals source. It takes upfront setup but then runs automatically, unlike pure manual entry.
Should I track gross revenue or net payout from a merchant of record?
Pick one and be consistent across every product in your portfolio. Net payout (after MoR tax handling and fees) is usually closer to your actual cash position, but gross transaction value is what customers paid and may match how you track revenue from Stripe elsewhere. The important thing is not switching definitions mid-year.
Is it worth paying for a portfolio dashboard if most of my revenue runs through Dodo?
Not yet, if Dodo is your only or primary revenue source and you have no connected processor or analytics source feeding the dashboard automatically. A spreadsheet will do the same job with less overhead until either Dodo adds broader integration support or you add products on processors that are natively connected.