App analytics

Four accounts read on a schedule, and no total that adds dollars to yen.

Not a gateway: nothing routes through it and there is no API to call. It reads what Google Play, App Store Connect, AdMob and Google Analytics publish — installs, store revenue, ad earnings, active users — and keeps every amount in the currency it was reported in.

Start free trial

14 days, no card

Where a ledger would carry a total, this says which currencies it is in.

App Store proceeds arrive in whatever the storefront charged in, and AdMob pays in your own payment currency. So every money figure is one amount per currency, and the row where a total belongs says there is none, because the total would be the sum of dollars and yen.

The same rule holds for anything that is a proportion: a conversion rate, a match rate, a click-through rate, an engagement rate and a star rating are averaged over the window rather than added up, and a day no account has delivered yet shows a dash instead of a zero.

The products traffic does pass through are the AI gateway, the storage gateway and the push gateway, which share one key and one audit trail. See the plans.

app analyticsexample

Every app, last 30 days

Installs
Play device installs, App Store units38,412
Store revenue

USD12,480.65

JPY684,200

EUR9,305.20

Totalnot added, three currencies

Ad earnings
USD3,902.11
Google Play
installs, earnings, store-listing visitors, ratings and crashes
App Store Connect
units and developer proceeds
AdMob
estimated earnings, impressions and the rates it reports
Google Analytics
active users, sessions, screen views and engagement

Figures through 21 Oct. Google and Apple publish about two days behind, and restate recent days.

What app analytics does

A screen each: Android, iOS, AdMob, Analytics
One screen per platform rather than per account, because an Android app's ad earnings are Android's figures too. Over them: an overview that crosses all four, a list of every tracked app, and a screen for any one of them.
Linking an account
Play, AdMob and Analytics connect by signing in with Google. App Store Connect takes a team key: Sales and Reports reads the money, and Admin is needed as well for impressions and product page views, because only an Admin key may request an analytics report. The first read reaches back thirty days; nothing older is backfilled.
The day it is good through
Every total says which day it reaches, because the stores publish about two days behind and restate the days before that. A day nothing was delivered for shows a dash, not a zero. Nothing here is live.
A rate is averaged, never summed
Conversion rate, match rate, click-through, engagement rate and a star rating are means over the window you asked for. Thirty days of a 3% conversion rate is not 90%, and a 4.6 rating over ninety days is not 414.
The people, not only the installs
Where an Analytics property is linked: active users over a day, a week and twenty-eight days, new users, sessions, screen views and engagement. Analytics counts people, so its figures are never added to a store's install count.
CSV export
The stored figures at the granularity they were stored at — by day, by source, by app, and by country, ad unit or version where the source broke it down — so a month can be tied to a payout statement.

What each account gives, and what it withholds

Only what Google, Apple, AdMob and Analytics publish is read, and the four do not publish the same things. Under each dashed rule is what that account holds back, so it is not here either.

Google Play

Device and user installs, uninstalls and upgrades; earnings; store-listing visitors, acquisitions and conversion rate; daily and overall average rating; crashes and ANRs. Play counts devices and users as two counts of the same event, so an install total means one of them — devices — and never the two added together.

No Crashlytics detail. Play's own crash and ANR counts are read; stack traces and crash-free users are not, because Google publishes no read API for Crashlytics.

App Store Connect

Units and developer proceeds, each in the currency the storefront charged in, broken down by country where Apple's report is.

History before you connect. Apple generates an analytics report only from the day it is asked, so App Store impressions and product page views start there rather than reaching back.

AdMob

Estimated earnings in your payment currency, ad impressions, clicks, ad requests, match rate and click-through rate, down to the ad unit and format where AdMob reports them.

No installs: AdMob reports money and ad impressions, not acquisitions. It also carries both platforms at once, so an app's ad earnings are filed under that app's platform rather than under the source.

Google Analytics

Daily, weekly and monthly active users, new users, sessions, screen views, engagement rate and average session length, from the property you pick after signing in.

No money of any kind: Analytics reports none. No retention or cohort reports, and new users are not offered as installs — a reinstall is a new user and not a new install.

Nothing to call. One file to reconcile.

There is no endpoint in front of app analytics, because it is a reader rather than a gateway. What comes out of it is the stored figures as CSV, at the granularity they were stored at.

date,source,app,metric,value,currency,country,platform,appVersion,osVersion,adUnit,adFormat
2026-09-30,PLAY,Tidepool,deviceInstalls,1284,,,ANDROID,,,,
2026-09-30,PLAY,Tidepool,deviceInstalls,206,,JP,ANDROID,,,,
2026-09-30,APP_STORE,Tidepool,proceeds,418.22,USD,,IOS,,,,
2026-09-30,APP_STORE,Tidepool,proceeds,61400,JPY,,IOS,,,,
2026-09-30,APP_STORE,Tidepool,proceeds,52100,JPY,JP,IOS,,,,
2026-09-30,ADMOB,Tidepool,ESTIMATED_EARNINGS,129.45,USD,,ANDROID,,banner_home,BANNER
2026-09-30,GA4,Tidepool,active1DayUsers,9043,,,,,,,

Two currencies on one day, never added. A blank country is the whole app and a filled one breaks that day down, so summing the value column over a mixed export counts those days twice — filter to blank dimensions for a day's totals. The Analytics row carries no platform because one property covers every stream an app has. The app and the figures above are invented.

App analytics questions

What does Penstoke app analytics read?
Four accounts a publisher already has. Google Play: installs, earnings, store-listing visitors and conversion rate, ratings, crashes and ANRs. App Store Connect: units and developer proceeds, from Apple's sales reports. AdMob: estimated earnings, ad impressions, clicks, ad requests and the rates it reports. Google Analytics: active users by day, week and month, new users, sessions, screen views and engagement. Each is read on a schedule and kept on a screen of its own — Android, iOS, AdMob, Google Analytics — over an overview that crosses all four, a list of tracked apps, and a screen for any one app.
Is app analytics part of the gateway?
No, and the distinction is worth keeping: it is a separate product on the same platform. Nothing routes through it and there is no API to call. The AI, storage and push gateways sit in front of providers your apps call; app analytics reads reports the stores and Google publish about your apps and shows them to you.
Does it add up revenue from different currencies?
Never. Every money figure is one amount per currency and there is no combined total, because App Store proceeds arrive in whatever the storefront charged in and AdMob pays in your own payment currency — a single total would be the sum of dollars and yen. A rate is averaged over the window rather than summed, so thirty days of a 3% conversion rate reads as 3% and not 90%.
How do I connect Google Play, App Store Connect, AdMob and Google Analytics?
Play, AdMob and Analytics connect by signing in with Google, and Analytics then asks which property, because one Google account commonly sees a dozen and nothing else says which one is this app's. App Store Connect takes a team key: Sales and Reports reads the money, and Admin is needed as well for impressions and product page views, because only an Admin key may request an analytics report. The first read reaches back thirty days, and nothing older is backfilled.
How current are the figures?
About two days behind, which is when Google and Apple publish them, and they restate recent days afterwards. So every figure carries the day it is good through rather than implying it is current, and a day nothing has been delivered for shows a dash rather than a zero. Nothing here is live or real-time.
Can I export the figures to reconcile a month?
Yes, as CSV at the granularity the figures were stored at: a row per day, source, app and metric, with the currency and the country, ad unit, format or version the source broke it down by. Whole-app rows and the per-country rows that break them down are both in the file, which is what tying a figure back to a payout statement needs — and why summing the value column over a mixed export counts some days twice. Filter to blank dimensions for a day's totals.
Does it include crash reports, retention or iOS conversion rate?
Only partly, and the gaps are permanent. Play's own crash and ANR counts are read, but not Crashlytics detail — no stack traces and no crash-free users — because Google publishes no read API for it. Analytics' active users, sessions and engagement are read, but not its retention or cohort reports. Apple's Analytics Reports are read alongside its sales ones, so iOS carries App Store impressions, product page views and a conversion rate — from the day the report is requested, because Apple generates no history for one. That rate is computed rather than published, and reads a little below App Store Connect's own.

Link the accounts you already have, and read them in one place.

Start free trial

14 days, no card. The first read reaches back thirty days.