12testers
The threshold that gets cited
Written against testers who are opted in to the closed test. Not invitations sent, not accounts added to the track.
How Many Testers Does Google Play Closed Testing Need?
Google Play asks for 12 testers opted in, not 12 invitations sent. Where testers actually come from, and what quietly resets your count.
12testers opted in
The figure the Play Console itself states against your app. It is a threshold on testers who are opted in, which is why twelve invitations is not twelve testers.
Read from the production access screen in your own account, and stated in App testing requirements for new personal developer accounts. Google sets this figure and can change it. Policy content reviewed 2026-09-27.
The numbers people mix up
Every one of these is a real count from a campaign. The problem is that teams report the wrong one.
14days
The continuous period
Continuity is the operative word. Fourteen days that contained a dip below the threshold is not fourteen continuous days at or above it.
2separate counts
Invitations and opt-ins
Two facts, tracked separately. Collapsing them into a single number is the most common way a campaign looks healthier than it is.
4states
What a tester can be
Invited, opted in, active and reporting. Only one of them is the number you report, and only one of them is the number worth acting on.
Four states, counted separately
A tester moves through these in order, and it is possible to stop at any of them. Which one you are counting decides what you can honestly claim.
Invited
The address is on the roster and the invitation has gone out. This is the number that looks impressive and proves nothing.
Not the reported number
Opted in
The invited Google account opened the link and accepted. This is the number the requirement is written against.
The number you report
Active
The tester has opened the build recently enough to count as participating. This is the number worth acting on during the window.
Not the reported number
Reporting
The tester has raised at least one finding against the current build. Not required by any rule, and the clearest sign the test is doing something.
Not the reported number
Both numbers, in the product
The count you report and the count you act on, read from the same roster rather than derived from memory.
The mistakes that cost the most time
None of these are technical, and every one of them has a boring fix.
- Inviting the wrong Google account, so the tester signs in with their personal account while the invite sits unused on a work address.
- Duplicated addresses, which gives you a roster of twelve containing eleven testers.
- Treating a conversation as an opt-in. Verbal agreement does not install anything.
- Checking participation once, at the end, by which point every fix is a restart.
- Replacing testers without checking the effect on continuity, when a gap can break the continuous period you are relying on.
Questions about testers
Get the Roster Right From Day One
Tell us how many testers you need and when the window should start. We will build the roster, track opt-ins and flag anyone who goes quiet while there is still time to act.
Policy statements on this page reviewed 2026-09-27. Always confirm current requirements with Google.