Connect Google Play · Sprid docs

Before you start

Owner or Admin access in Play Console, and a Google Cloud project where you can create a service account. The project does not need to be linked to Play Console.

Set it up

A. Google Cloud

Open Google Cloud and select or create a project.
APIs & Services → Library: enable Google Play Android Developer API. For statistics reports, also enable Google Play Developer Reporting API.
IAM & Admin → Service Accounts → Create service account. Name it sprid-play, click Create and continue, then Done. Leave Cloud roles empty.
Open the account → Keys → Add key → Create new key → JSON → Create. Save it as play-sa.json and keep it private.
Copy the service account’s email.

B. Play Console

Open Play Console → Users and permissions → Invite new users. Enter the service account’s email; leave access expiry unset.
App permissions → Add app: select your app, then Apply.
Enable View app information (read-only) and Reply to reviews. Add Manage store presence to update listing copy. Leave financial access off.
Click Invite user → Send invite.

Find the package name

Copy it from beneath your app’s name on its Play Console Dashboard, such as com.example.app. Run sprid init if your Sprid app profile lacks it.

For download reports, copy the Cloud Storage URI from Download reports → Statistics into playExportBucket in .sprid/app.json. These also need the account-level View app information and download bulk reports (read-only) permission.

Connect to Sprid

Run in your terminal

sprid connect play --key ~/Downloads/play-sa.json

Use your own file path. Keep its contents out of chat.

Check the connection

Run sprid status, then ask your agent: “Check that Sprid can read this app’s Play reviews and download reports. Tell me what is missing.” The review email only arrives when there are new reviews.

Status reflects saved configuration and collection errors. To re-test a saved key in chat, run sync_store_reviews for the app (discover it with find_tools if needed). Its connected count reports successful review reads, including empty results. Check downloads separately with get_insights or get_marketing_review, including the latest reported date. Review access does not verify download access or permission to reply.

If something goes wrong

503 or another temporary server error: retry the read with the key already saved in Sprid. This failure alone does not establish a key or permission problem. Sprid retries review reads with bounded backoff and collects again on its scheduled run. If it keeps failing, contact hello@sprid.studio.
Permission denied: check the service account appears under Users and permissions with your app selected. New permissions can take time; integrators report up to 24 hours, which Google’s docs do not confirm.
Google Play’s API is switched off: enable Google Play Android Developer API in the service account’s Cloud project. Sprid’s error message links to it.
Reviews are empty: Google’s API only returns recent reviews with written text. Older reviews and star-only ratings stay visible in the store but not to Sprid.

Investigate with this connection

Reads reviews and report_rows for the pinned package. Reviews are limited by Google’s history window; report rows need the saved export bucket.

Run in your terminal

sprid marketing-review capabilities --app <slug> --source play --json

See connected queries.

Sources and verification

Prefer your terminal? sprid docs google-play reads this same guide.

← App Store Connect

Google Search Console →