How to Set Up Google Play Closed Testing (Step-by-Step, 2026)
The Play Console UI for closed testing hasn't changed dramatically in a while, but it's still easy to get stuck on two specific screens the first time through: countries/regions, and where the opt-in link actually lives. Here's the whole flow in order.
1. Create the closed testing track
From your app in Play Console, go to Testing → Closed testing. Create a new track (the default is usually fine — you can rename it later) and upload your signed AAB. If this is your first release on this app, Google needs to review it before anyone can join as a tester, which typically takes a few days.
2. Add your testers
On the same Closed testing page, open the Testers tab. You have two ways to add people:
- Email list or Google Group — you manage a list of specific addresses; only those exact accounts can opt in.
- Shareable opt-in link — enable this and Play Console generates a public URL. Anyone with the link can view the "become a tester" page and opt in with any Google account. This is the version most closed-testing services (including us) ask for, since it doesn't require pre-registering each tester's email individually.
3. Set countries and regions — the step people skip
Still on the Testing page, there's a countries/regions selector for the track. If it's left empty or too narrow, testers outside the selected regions will hit a "this version isn't available in your country" error when they try to opt in — even with a perfectly valid link and a perfectly real account. This is one of the most common reasons a batch of testers "can't" opt in, and it has nothing to do with the testers themselves.
4. Wait for the release to be approved
Your closed testing release goes through its own review before the opt-in link becomes usable. Nothing to do here except wait — but if testers are reporting the link doesn't work yet, this is almost always why.
5. Copy the opt-in link and get testers in
Once approved, go back to the Testers tab and copy the link (it looks like https://play.google.com/apps/testing/<package_name>). Send it to your testers, or paste it into a testing service. Each tester needs to open the link, tap "Become a tester," and then actually install the app from the Play Store — accepting the invite without installing doesn't count.
6. Track the 14 days
The clock starts once a tester has opted in and installed. Play Console's Testers tab shows a running count, but it only reflects opt-in status, not usage — which is exactly the gap covered in why 12/12 opted-in testers still isn't a guarantee. Keep the track open and stable for the full 14 days; removing testers or replacing the release mid-test can reset progress.
7. Apply for production access
Once you've held 12 opted-in, active testers for 14 continuous days, a production access application option appears for the app. From there it's a standard review — see how long that typically takes.
The setup above takes maybe 20 minutes. Getting 12 people to actually use the app for 14 days afterward is the part that eats weeks — our device farm handles exactly that step once you paste the opt-in link.
See how it works — from $24 →FAQ
Where do I find my closed testing opt-in link?
Play Console → your app → Testing → Closed testing → Testers tab. Enable the shareable link option and copy the URL shown there.
Why do my testers see "not available in your country"?
The track's countries/regions selection is empty or doesn't include the tester's region. Fix it on the same Testing page, next to the tester list.
Does accepting the invite count as opting in?
No — a tester has to accept the invite and install the app from the Play Store under that same Google account for it to count toward the 12.