What a closed testing track is, how the process runs from build upload to opt-in, how long testing lasts, and where most campaigns go wrong.
The console gives you several release tracks. Closed testing sits between a private list you control and a public beta anyone can find. Which one you use decides who counts as a tester.
Who can join
Up to 100 accounts you add by email address
How they join
No listing, no opt-in link, fastest to publish
Where it counts
Useful as a gate before a closed test, but it is a different track. Confirm which one satisfies the rule for your account.
Who can join
Only the Google accounts you invite to the track
How they join
An opt-in link, plus a tester limit per track
Where it counts
This is the track the production access requirement refers to, which is why participation is the number that matters.
Who can join
Anyone who finds the listing and chooses to join
How they join
Publicly discoverable, no invitation required
Where it counts
Good for volume and early feedback, poor for controlling who is counted as a tester.
A track holds the testers, the countries and the release together. Reusing an existing track across releases keeps the tester list intact, which is what lets a second campaign avoid rebuilding the roster.
Look atAn existing track already carries its tester list and its active release, so a new window can start without re-inviting anyone who stayed opted in.
Testers go in as individual email addresses or as a Google Group. Each address fills one slot, and only the account that was invited is able to opt in to the track.
Look atThe address entered here is the address that has to open the opt-in link. A tester who signs in with a different Google account fills nothing, however willing they are.
Availability is configured per track, country by country. Leaving a tester's country out locks them out of the opt-in link even though their address is on the list.
Look atEvery country you add is a country your testers can install from. Your app's own availability rules still apply on top of the track's.
Tester changes and the release are submitted together. Until that submission clears review, the track still carries the previous release and testers have nothing new to install.
Look atChanges sit here waiting to be sent. A campaign that starts counting days before this clears is counting days in which nobody received the build.
Nearly every closed testing campaign that goes wrong goes wrong for one of these reasons, and none of them are technical.
A tester who opts in with a different Google account than the one invited does not fill the slot you thought they filled. Duplicate addresses have the same effect.
An invitation is not an opt-in. People agree in conversation and then never open the link, and the gap stays invisible unless somebody is watching the roster.
Nobody announces they have stopped opening the app. The interruption only becomes visible if activity is tracked through the window rather than checked at the end.
When the application asks you to account for the testing, the dates and participation numbers have to come from somewhere. Reconstructing them from memory is where accuracy is lost.
Register, create the app and choose a tester count. The campaign then tracks opt-ins and daily participation across the testing window.
We never ask for access to your Play Console account.
