Guide · Google Play
Play Console quota — closed-testing testers
What Google asks for closed-testing quotas, how to build a tester list, and how measurable campaigns fit — without replacing official docs.
In closed testing and other tracks, “quota” usually means: you need a minimum number of real testers linked to your app in Play Console. Google documents the requirements; this guide summarizes common ops and how a Tester Marketplace campaign can help you cover them with usage evidence.
Important: Tester Marketplace does not replace official policies or thresholds. If Play Console shows a specific number or checklist, that number wins.
Typical Play Console steps
- Create or select the track (internal / closed / open) for your phase.
- Decide how testers join: email list, link or groups.
- Upload an installable build matching the package name.
- Confirm testers accept and install (not only receive the invite).
List vs real usage
A full list closes the admin gate; sessions and events give product signal. If you only need the quota once, DIY may be enough. If you want to repeat the process across releases, define measurable rules in a campaign.
How Tester Marketplace helps
- Campaigns with a cap around ~12–14 testers (Play Quota package) or other sizes you choose.
- Telemetry for session start/end and named events.
- Optional Play Integrity to reduce fraud in the test.