- URL: https://asomaster.app/docs/google-play/ - Updated: 2026-10-27 - Summary: Create a Google Cloud service account, invite it in Play Console and connect it to ASOMaster to read listings and statistics and publish listing changes. # Google Play Console Updated 27 October 2026 Google Play apps work without a console connection: ASOMaster reads the public store page. Connect a service account to list your own apps, read their listings in every language, see Play statistics and publish listing changes. ## What a connection adds - **Your apps.** The ones whose package names you enter are verified and offered in Add app. - **Your listings.** Title, short description and full description for every language you publish. - **Publishing.** Listing Studio writes your chosen text through a Play edit: it opens an edit, patches only what changed, validates it and commits. If any step fails, the edit is deleted and your live listing stays as it was. Google may review listing changes before they appear. - **Statistics (optional).** Store listing visitors and acquisitions from Play Console's monthly reports. ## 1\. Create a service account and key 1. In [Google Cloud](https://console.cloud.google.com/iam-admin/serviceaccounts), pick or create a project and open **IAM and Admin › Service accounts**. Create a service account; it needs no Google Cloud roles. 2. In the same project, enable the **Google Play Android Developer API** (APIs and Services › Library). 3. Open the service account, then **Keys › Add key › Create new key › JSON**. A `.json` file downloads. It contains `"type": "service_account"` and the account's email address. ## 2\. Give it access in Play Console 1. In [Play Console](https://play.google.com/console), open **Users and permissions** and invite the service account's email address. 2. Give it access to the apps you want ASOMaster to manage. To read, it needs to view app information; to publish listings, it also needs permission to edit the store listing. 3. Save. Google can take a little while to apply new permissions; if the first test fails, try again in a few minutes. ## 3\. Connect it in ASOMaster 1. Open **Settings › Store consoles** and choose Google Play. 2. Drop the `.json` key. 3. Enter your apps' package names, one per line (for example `com.example.app`). Google's API can't list the apps a service account can see, so ASOMaster checks each name you give it. 4. Optionally add a label, then connect. ## Play statistics Google shares store listing statistics as monthly reports in a Cloud Storage bucket that belongs to your developer account. In Play Console open **Download reports › Statistics** and copy the Cloud Storage URI (it starts with `gs://pubsite_prod_`). Paste it in the app's Store analytics view for the app, and make sure the service account can view app information. Google doesn't export store impressions or traffic sources, so those stay App Store only. ## Where the key goes - The JSON key is stored in your operating system's keychain, never on our servers. - ASOMaster exchanges it for short-lived tokens with Google and talks only to Google's official API hosts. Redirects are never followed. - Agents connected through MCP pass the key as a file path (`serviceAccountPath`); it is never returned to them. ## Troubleshooting **"Use a service account key file"** The file isn't a service account key. Download a JSON key from Google Cloud › IAM and Admin › Service accounts › Keys, not an OAuth client file. **A package name is rejected** The service account can't see that app. Check the invitation in Play Console › Users and permissions covers it, and that the package name is spelled exactly as in Play Console. **The API isn't enabled** Enable the Google Play Android Developer API in the Google Cloud project that owns the service account, wait a minute and connect again.