Integration guide
2 min read
Connect Google Play
Create a dedicated service account with app-specific viewing permissions.
Before you start
- Access to a Google Cloud project and the relevant Play Console apps.
- A person authorized to invite users in Play Console.
- Owner or admin access in Specita.
Set up the connection
Enable the two APIs
In your Google Cloud project, enable Google Play Android Developer API and Google Play Developer Reporting API.
Create a dedicated service account
Open IAM & Admin → Service Accounts and create an account for Specita. Project Owner or Editor is not required for this integration.
Grant Play Console app access
Open Play Console → Users and permissions → Invite new users. Enter the service account email, choose the intended apps, and grant the viewing permissions listed above. Leave release, financial, order-management, and admin permissions disabled.
Create and upload a JSON key
Open the service account’s Keys → Add key → Create new key → JSON, following your organization’s key policy. In Specita → Integrations → Google Play, upload that service-account
.jsonfile and connect. An OAuth client JSON is a different credential type.Map and sync the Android app
Match the app’s package name to your product. Run Sync from the Android workspace or App stores, then check the result for each track.
Check your setup
- The intended package appears among accessible apps.
- At least one requested track sync succeeds; read the per-track errors for partial results.
- The page displays the last successful sync rather than assuming observations are current.
Troubleshooting
App not listed or access denied
Check the exact service-account email, selected Play Console apps, viewing permissions, and both enabled APIs. Do not solve this by granting Admin.
Cloud policy blocks JSON keys
Ask your Cloud administrator about an approved dedicated key. Specita currently requires a service-account key; do not bypass your organization’s policy.
Rollout percentage missing
The read-only release-summary endpoint does not provide an exact percentage. Specita does not infer one.
Credential safety
The JSON includes a private key. Upload it only in the connection form, keep it out of source control, and rotate or revoke it in Google Cloud if compromised.