One dashboard for every app and site you run

Running several products means running several dashboards. Revenue sits in Stripe, RevenueCat, App Store Connect and Google Play. Traffic sits in a separate GA4 property per product, because GA4 is built around one property at a time. Ad spend sits in each ad platform. To answer "how is everything doing", you open ten tabs and add things up in your head.

There are four realistic ways out. Each costs you something different.

Option 1: a spreadsheet#

One row per product per month: revenue, ad spend, costs, profit.

Good: free, flexible, and you understand every number in it. Bad: it's only as fresh as your last update, which is usually "end of last month, if I remembered". Copying numbers by hand also makes it easy to mix gross and net, or to count a sale twice when RevenueCat and the App Store both report it. And it never tells you anything until you open it.

Fine for two products. Painful at five.

Option 2: Looker Studio#

Google's free reporting tool connects to GA4 directly, and you can put several properties on one report, blending them into combined charts.

Good: free, live GA4 data, and you can share a link. Bad: it is built for traffic. Stripe, RevenueCat and the stores need third-party connectors or exports, and getting revenue per product next to traffic per product takes real setup and upkeep. It's a report you go and look at, not something that tells you when a product drops.

Good if your products are all websites and you mainly care about traffic.

Option 3: each platform's own dashboard#

RevenueCat's charts for subscriptions, App Store Connect for downloads, Stripe for the SaaS, GA4 for traffic.

Good: every number is first-hand, and you already have the logins. Bad: nothing is combined. No single place shows that one product makes more than the others but gets the least of your time, or that another is losing money once ad spend is counted. You become the integration.

Option 4: a per-product P&L tool#

This is what Plask does. Connect your sources once, map them to products, and each product gets revenue, ad spend, fixed costs and profit, with traffic next to it.

Good:

• Stripe, RevenueCat, App Store Connect, Google Play and GA4 in one view, refreshed four times a day.
• Every number shown as net: proceeds for the stores and RevenueCat, gross minus fees and refunds for Stripe. Gross is shown next to it where the source provides it.
• No double counting: when RevenueCat covers an app's store, the store's own revenue isn't added again.
• A missing source shows as a dash, never as a made-up zero.
• Up to three Focus cards every Monday on which product needs you, and alerts when revenue drops. Both are on Pro.

Bad: it's another subscription, $5 a month for more than one product. Ad spend and fixed costs are entered by you or synced by an AI assistant, not pulled from ad accounts. And it's built for a portfolio of small products, not for deep analysis of one large one.

How to pick#

• One or two products, mostly web: a spreadsheet plus GA4 is enough.
• Several websites, traffic is what matters: Looker Studio.
• Several products across apps and web, and you want profit, not just revenue: a per-product P&L. That's the case Plask is built for, and the first product is free with no time limit.

Whatever you choose, follow two rules: pick one revenue source per product and never add two that report the same sale, and compare proceeds with proceeds. The reasons are in App Store Connect vs RevenueCat: which revenue number is real?