All docs
Connect

Google Play: connect a Play Console user and read reviews, vitals and products

TL;DR

Google Play signs in with Google and asks for two permissions: androidpublisher (Google's one permission for the Play publishing API, reads and writes alike) and playdeveloperreporting (read-only vitals). Each app the user can see becomes its own connection. 11 reads and 1 write. Firebase and Google Play are in Google's verification review: today only pilot workspaces can connect them, and every other workspace sees the card marked "In review". Everything described here is built; it opens to every workspace once Google verifies the permissions.

What you need

  • A workspace in the pilot (the card says In review elsewhere).
  • A Google account that is a user in your Play Console developer account, with the app permissions the reads need: View app information (vitals, track status), View financial data (products, subscriptions, voided purchases) and Reply to reviews (reviews and replies).

Connect step by step

  1. 1Open Integrations → Google Play → Connect.
  2. 2Sign in with the Play Console user's Google account and allow the two Google Play permissions.
  3. 3Agent Planners lists the apps that user can see through Play Developer Reporting and saves one connection per app (by package name).
  4. 4Press Refresh accounts after a new app is published or the user gains access to more apps.
Re-authorize updates the same connections in place. Disconnect deletes the stored Google tokens (encrypted) and the app rows; you can also revoke access at myaccount.google.com/permissions.

Permissions

PermissionUsed forWhat is never done with it
androidpublisherReviews and the reply, one-time products, subscriptions, voided purchases, track statusNo release, track, rollout, price, product, listing or purchase change, and no upload
playdeveloperreportingListing your apps; crash rate, ANR rate, error countsRead-only

What works, and the limits

  • Reviews: roughly the last week only (Google's limit). Reviewer names are masked, emails and phone numbers removed, the text treated as data.
  • Vitals: daily values in America/Los_Angeles calendar days, ending at the latest day Google has finished; a rate is a share of distinct users, and distinct users are never summed across days.
  • Voided purchases: the last 30 days at most, counted by reason and source; purchase tokens are never returned.
  • Track status: read without opening an edit, so nothing is left half-changed in Play Console.
  • A reply to a review always waits for a person — it is public. Plain text, at most 350 characters; longer is refused, never cut.

Troubleshooting

  • No apps found. The user sees no apps in Play Developer Reporting — check their Play Console access, then Refresh accounts.
  • 403 on a read. The answer names the Play Console permission missing for that read (for example View financial data).
  • Old reviews are missing. Google's API returns only recent reviews; use Play Console's review export for history.

Frequently asked questions

Why does Google Play need androidpublisher?
It is the only permission Google publishes for the Play publishing API — there is no read-only variant. Agent Planners uses it for reads and for review replies a person approves, and calls no release, price or listing write.
Can I connect apps from several developer accounts?
Yes, if the signed-in user can see them; each app is its own connection. Another person's sign-in can be added the same way.

Related