Syphnosys Analytics
Syphnosys Analytics is a private reporting dashboard that shows the Syphnosys team how our own mobile apps are performing — bringing figures from Google Play, AdMob, Firebase, Google Analytics and Google Ads together in one place instead of five.
What it does
Syphnosys publishes mobile apps. The figures that describe how those apps are doing arrive from five different Google products, each with its own dashboard, its own definitions and its own date handling. Syphnosys Analytics reads those figures through Google's official APIs, stores them, and puts them side by side — so that installs, ad earnings, advertising spend, crashes and audience numbers for one app can be read together on one screen.
It is an internal tool. It has no public sign-up, sells nothing, and is used only by employees of Syphnosys who have been given an account. Every account connected to it is one that we own.
Which Google data it reads, and why
Every scope requested is read-only. The application never creates, edits or deletes anything in a connected Google account, and it never reads data belonging to anyone other than the account owner who connected it.
| Platform | Sign-in | Access requested | Why |
|---|---|---|---|
| AdMob | OAuth | admob.readonly, admob.report |
Read estimated earnings, impressions, clicks, ad requests and fill rate for the apps belonging to the signed-in account owner, to show them in reports. |
| Google Ads | OAuth | adwords |
Read campaign cost, impressions, clicks and conversions for the campaigns belonging to the signed-in account owner, to show what advertising spend returned. |
| Google Play | Service account | playdeveloperreporting, devstorage.read_only |
Read install, uninstall, rating, crash and ANR figures for apps belonging to the account owner. |
| Firebase | Service account | firebase.readonly, bigquery.readonly |
Read Crashlytics crash counts from the BigQuery export belonging to the account owner. |
| Google Analytics | Service account | analytics.readonly, bigquery.readonly |
Read aggregate audience and engagement figures for the GA4 property belonging to the account owner. |
Only AdMob and Google Ads use OAuth, and so only those two involve the Google consent screen. The other three are connected with a service-account key that the account owner creates and supplies themselves; no consent screen and no end-user sign-in is involved for those.
What it does not do
- It does not read anything belonging to your app's end users — only aggregate figures already visible in the Google dashboards for the connected account.
- It does not sell, rent, share or transfer any data obtained from Google APIs.
- It does not use Google API data for advertising, and does not build profiles.
- It does not write to, or change, any connected Google account.
How access is stored
Credentials — refresh tokens and service-account keys — are stored encrypted, are readable only by the application, and are never displayed back after being saved. Access can be withdrawn at any time from the connected Google account, and removing an account here deletes its stored credentials.
Contact
Questions about this application or the data it reads: support@syphnosys.com. Our privacy policy sets out how information is handled in full.