惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - 司徒正美
Jina AI
Jina AI
Microsoft Azure Blog
Microsoft Azure Blog
博客园 - 三生石上(FineUI控件)
宝玉的分享
宝玉的分享
MyScale Blog
MyScale Blog
I
InfoQ
爱范儿
爱范儿
Microsoft Security Blog
Microsoft Security Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
Stack Overflow Blog
Stack Overflow Blog
T
Tailwind CSS Blog
D
DataBreaches.Net
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
T
The Blog of Author Tim Ferriss
B
Blog
阮一峰的网络日志
阮一峰的网络日志
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
月光博客
月光博客
雷峰网
雷峰网
Recent Announcements
Recent Announcements
量子位
B
Blog RSS Feed

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
How I track revenue across AdMob, AdSense, YouTube, and R...
HaveAGoodOne · 2026-06-28 · via DEV Community
Cover image for How I track revenue across AdMob, AdSense, YouTube, and RevenueCat without ten tabs

HaveAGoodOne

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.