How I track revenue across AdMob, AdSense, YouTube, and RevenueCat without ten tabs

HaveAGoodOne — Sun, 28 Jun 2026 09:51:58 +0000

If you earn from more than one source, you already know the ritual. Open AdSense. Switch tabs. Open AdMob. Another tab for YouTube. Open RevenueCat. Repeat for every account you manage. You do this every morning, and you still cannot answer one simple question: how much did I make yesterday, across everything?
I ran into this managing several AdMob and AdSense accounts alongside subscription revenue. After enough mornings lost to tab-switching and mental math, I started treating it as a real problem instead of a chore. Here is what I learned, and the approach that finally fixed it.
The actual problem is not earning, it is reconciliation
The money is not the hard part. Trusting the total is. Three things make a combined number surprisingly difficult to get right.
First, every platform reports on its own timeline. AdSense, AdMob, and YouTube all show estimated earnings that get revised before payout. RevenueCat subscription revenue lives in a completely separate system with its own refund and proration logic. The number you see at 9am is rarely the number that lands.
Second, the data is fragmented by design. Native dashboards are siloed on purpose. There is no single place that shows ad revenue and subscription revenue side by side, so you stitch it together yourself.
Third, multi-account makes it worse fast. The moment you run a second AdMob account, or a separate Google login for a different property, you lose the single view entirely. Each account is its own login, its own report, its own export.
This is the fragmentation tax. It is the daily gap between what your accounts show and what you will actually receive.
Track at the account level, not the platform level
The single most useful shift for me was to stop thinking in platforms and start thinking in accounts.
When your total moves, "AdSense is down" is not actionable. "AdSense account 2 on the recipes site is down 30 percent while account 1 is flat" is. Revenue problems almost always live in a specific account, not a whole platform, so that is the level you want visibility at. Build your tracking so you can answer "which account moved" in seconds, not after ten minutes of digging.
The options, from cheapest to most complete
For a single account, the official AdMob app or the AdSense report is genuinely fine. Do not overbuild.
For a few sources, a spreadsheet plus the reporting APIs gets you far. AdMob and AdSense both have APIs that return revenue, impressions, clicks, and eCPM per account and per ad unit. RevenueCat has a clean API too. You can pull these into one sheet on a schedule. The cost is maintenance, because every account adds another connection to babysit.
For many accounts or genuinely mixed revenue, the spreadsheet becomes the problem it was meant to solve. At that point you want a layer that aggregates everything into one view and keeps it in sync for you.
What I ended up building
I built Aperio because nothing covered ad revenue and subscription revenue together. It connects AdSense, AdMob, YouTube, RevenueCat, Shopify, and Patreon read-only, and shows combined revenue across every account in one mobile view, with drill-down by account and asset so you can see exactly which one moved. Read-only and OAuth-only, so it reads your numbers and never touches the accounts.
It is free on iOS (https://apps.apple.com/il/app/aperio-all-revenues-one-view/id6778547730) and Android (https://play.google.com/store/apps/details?id=com.aperio.get) if you want to skip the spreadsheet stage.
However you solve it, the principle is the same: one combined number, tracked at the account level, that you can trust without opening ten tabs. If you manage more than one revenue source, I would genuinely like to hear how you handle it today.

AI Has Hands Now. You Should Decide What It Can Do.

HaveAGoodOne — Mon, 04 May 2026 14:05:24 +0000

⚠️ Example

An AI agent with access to your tools can already:

delete your production users table
send emails to real customers
trigger payments or workflows

In most systems today — these actions just execute.

No checkpoint. No approval.

We’ve crossed a line.

AI is no longer just generating text.

It’s starting to take actions.

await deleteUser(userId);
await sendEmail(customer);
await transferFunds(amount);

If the agent decides to do it — it just runs.

That’s fine in a demo.

It’s not fine in production.

Where things break

Once AI touches real systems, you’re exposed to:

accidental destructive actions
prompt injection leading to unintended behavior
over-permissioned tools
zero auditability of decisions

You don’t need a malicious AI.

You just need:

a slightly wrong decision, at the wrong time

The missing layer

Every action should be checked before it runs.

Not after.
Not in logs.

Before execution.

What Runplane does

Runplane sits between your AI and real-world execution.

Every action becomes:

✅ ALLOW
❌ BLOCK
⏸ REQUIRE APPROVAL

Example

Without control:

await deleteUser(userId);

With Runplane:

await runplane.guard(
  "delete_user",
  "production-db",
  { userId },
  async () => {
    return deleteUser(userId);
  }
);

Now:

destructive actions can be blocked
risky actions can require approval
everything is logged and auditable

Where this fits

If you're building:

AI agents
MCP tools
automation workflows
internal copilots
API-driven systems

You already have this risk.

You just haven’t hit it yet.

Try it

There’s a free developer tier:

https://runplane.ai/auth/sign-up?mode=developer

You can plug it into a real flow and immediately see:

actions being blocked
approvals being triggered

Final thought

We’re moving from:

“AI suggests actions”

to:

“AI executes actions”

Execution without control is risk.

AI has hands now.

You should decide what it’s allowed to touch.

DEV Community: HaveAGoodOne