How to Track App Revenue Across Google Play, App Store, and AdMob in One Place
I got tired of jumping between three dashboards just to figure out how much my apps were actually making. Here's what I learned about unifying revenue data.
If you publish on both the App Store and Google Play and run ads through AdMob, you know the routine. Check App Store Connect for iOS revenue. Switch to Google Play Console for Android numbers. Open AdMob for ad earnings. Maybe copy everything into a spreadsheet. Probably forget to do it tomorrow.
I did this for months before I realized I had no idea what my apps were actually making on any given day.

Each platform reports differently (and it’s annoying)
This is the part that frustrated me the most. It’s not just that the data is in three places. Each platform was designed to report only on its own ecosystem, and they all do it differently. I wrote a separate post comparing App Store Connect and Google Play Console reporting if you want the full breakdown.
App Store Connect uses Apple’s custom fiscal calendar. Their year is divided into months that are 28 or 35 days long. So “January revenue” in App Store Connect doesn’t mean January 1-31. It means some fiscal period that roughly overlaps with January, maybe starting December 29 and ending January 25. Payouts arrive about 33 days after a fiscal month closes.
Google Play Console is more straightforward - standard calendar months, revenue updates near real-time, payouts on the 15th of the following month. But Google reports everything in UTC, uses different terminology (they say “installs” where Apple says “downloads”), and the numbers just don’t line up neatly when you try to compare.
AdMob is its own thing entirely. eCPM, fill rates, estimated earnings that jump around daily based on advertiser demand. And these numbers don’t show up in either App Store Connect or Google Play Console, so if you’re not checking AdMob separately, that revenue is basically invisible.
Try to combine these three in a spreadsheet and you’ll run into timezone mismatches, fiscal period boundaries that don’t line up, and the tedium of manually exporting CSVs. Most solo developers I’ve talked to stop doing it after a few weeks.
The real cost of not seeing the full picture
Convenience aside, the actual problem is that you can’t see your profit.
Take a developer running a freemium app on both platforms:
- iOS subscriptions: $3,200/month through App Store Connect
- Google Play subscriptions: $1,800/month
- AdMob ads: $900/month across both platforms
$5,900/month total. That looks good. But if they’re spending $2,100/month on Google Ads and $800 on Apple Search Ads, the actual profit is $3,000 - roughly half the headline number.
Without costs sitting right next to revenue, it’s easy to celebrate the $5,900 while ignoring the $2,900 going out the door. And you definitely can’t tell which platform or which ad campaign is actually paying for itself.
The spreadsheet approach (and why it falls apart)
Everyone starts with a spreadsheet. Download reports weekly or monthly, paste into tabs, build formulas to combine things.
It works for a while. Then you miss a week. Then the formulas break because Apple changed their report format slightly. Then you realize 15 minutes of daily data entry adds up to over 90 hours a year, and you have better things to do.
Some developers build custom scripts using each platform’s APIs. App Store Connect API, Google Play Developer API, AdMob API - they’re all publicly available. But maintaining three separate API integrations is a real engineering project. Authentication alone is a headache: Apple wants JWT tokens, Google uses OAuth2, and the AdMob reporting API has its own flow. Every time one of them deprecates an endpoint or changes their auth, you’re back to fixing plumbing instead of building features.

What actually works
What I wanted was dead simple: pull data from all three platforms automatically, normalize it to daily numbers, and show everything in one place. Revenue by source, costs by channel, profit calculated automatically. Filtering by app if you have more than one.
That’s why I built Apps Finboard. It connects to Google Play, App Store, and AdMob for revenue, plus Google Ads and Apple Search Ads for costs. Data syncs three times daily - no exports, no CSVs, no spreadsheet formulas. Just charts that show revenue, costs, and profit side by side.
Why consistent data matters more than you’d think
The real payoff isn’t just saving time. It’s the questions you can answer once you have a few months of clean, consistent data.
Is my Google Ads spend generating enough Play Store revenue to be worth it? Is AdMob revenue growing or shrinking as my user base changes? Which platform actually has better economics for my app?
You can’t answer any of that when your data lives in three dashboards and a spreadsheet you last updated two weeks ago. But when everything flows into one place automatically, these become easy to check - and the answers might surprise you.
Apps Finboard Team
We build Apps Finboard so indie developers can stop juggling five dashboards and actually see their profit.