Go to console.cloud.google.com > Select a project > New Project. Name it clearly (e.g., "Play Console Integrations"). A dedicated project keeps your Play Console credentials isolated from other Google Cloud resources.
Google Play Console
Creating and Configuring a Service Account for Google Play Automation
Detailed guide to creating a Google Cloud service account for Google Play Console automation. Configure permissions, manage keys, and set up secure access for third-party tools.
7 steps2 min read
1
Create a Google Cloud project
2
Enable required APIs
In your new project, go to APIs & Services > Library and enable the Google Play Android Developer API. If you also need build management, enable the Google Play Custom App Publishing API as well.
3
Create the service account
Navigate to IAM & Admin > Service Accounts > Create Service Account. Choose a descriptive name and ID. For Google Play automation, you do not need to assign Google Cloud IAM roles—the relevant permissions are managed in Play Console.
4
Generate and download the JSON key
Click on your new service account > Keys tab > Add Key > Create new key > JSON. The browser downloads the key file. This file contains client_email, private_key, and project_id—the three values needed for API authentication.
Tip: Store the JSON key in a secrets manager (like 1Password, AWS Secrets Manager, or Google Secret Manager) rather than in plain files on your machine.
5
Grant Play Console access
Open Google Play Console > Users and permissions > Invite new users and enter the service account's email address (client_email in the JSON key). You no longer need to link a Google Cloud project on an API access page first. Then choose permissions by what the integration does:
- Manage store presence — edit the store listing, screenshots and descriptions
- Release to production, exclude devices, and use Play App Signing — publish releases
- View app information (read-only) — read app data without changing it
- Admin (all permissions) — full control; rarely needed by an integration
Names follow Google's users and permissions reference, checked September 24, 2026. The older Release manager and Store presence roles no longer exist.
6
Scope permissions to specific apps (optional)
For security, you can restrict the service account to specific apps rather than granting account-wide access. In the invitation, open App permissions, add only the apps the integration needs and set the permissions there. This follows the principle of least privilege.
7
Test and verify
Use the JSON key with your integration tool to verify access. In AppDrift's Google setup, upload the key file and run a test connection. The tool will attempt to list your apps via the API to confirm permissions are correct. If the test fails, review the permissions in Play Console.
Common Errors & Solutions
"The project id used to call the Google Play Developer API has not been linked" error
Solution: Older setups linked a Cloud project on the API access page; Google no longer requires that. Check that the Google Play Android Developer API is enabled in the Cloud project that owns the service account, and that the service account's email is invited under Users and permissions with the permissions you need.
Service account has access but cannot modify a specific app
Solution: If permissions are scoped to specific apps, ensure the target app is included in the service account's app list in Play Console.
JSON key file not working after team member left
Solution: Service accounts are tied to Google Cloud projects, not individual users. As long as the project exists and the key is valid, it continues working. However, rotate keys when team members with access leave.
Related
Related Guides
Setting Up Google Play Developer API Access
Step-by-step guide to enabling the Google Play Developer API. Learn how to enable the API in Google Cloud Console, create credentials, and connect them to your Play Console account.
Read guideRunning A/B Tests with Google Play Store Listing Experiments
Learn how to set up and run A/B tests on your Google Play Store listing. Test icons, screenshots, descriptions, and feature graphics to optimize conversion rates.
Read guideUsing Managed Publishing for Coordinated Google Play Releases
Learn how to use Google Play Console's managed publishing feature. Control exactly when updates go live, coordinate multi-market launches, and avoid accidental releases.
Read guideFrequently Asked Questions
Automate this with AppDrift
Skip the manual work
AppDrift connects to your Google Play Console to automate metadata publishing and localization across 60+ languages. Export your screenshots and upload them manually in Play Console.
Get Started FreeFree to start · No credit card