Guide 3 of 7 · Updated October 2026
Where to find your closed-testing opt-in link, and how to share it so testers actually get in
Short answer: Your opt-in link is https://play.google.com/apps/testing/<your package name>. Copy it in Play Console under Test and release → Testing → Closed testing → your track → Testers → "How testers join your test"; it appears only once an email list or Google Group is attached. It works when the track's latest release is "Available" and the tester opens it signed in with an account that is on your list, from a country the track allows.
Every tester joins your Google Play closed test through one URL: https://play.google.com/apps/testing/your.package.name. This guide shows where that link lives in Play Console, what has to be true before it works, how to share it, and the five reasons testers see "this app is not available for this testing program".
Where the link is in Play Console
- Open Play Console and select the app.
- In the left menu: Test and release → Testing → Closed testing.
- Open the track. A new app has one closed track by default, named Alpha (you can rename it or create more; the name does not matter to Google's requirement).
- Open the Testers tab.
- Scroll to How testers join your test. There is a web link with a copy button. That is the opt-in link.
The link is only shown once the track has at least one tester list attached (see email lists vs a Google Group below). If you see no link, add a list first.
Not sure you copied the right one? Paste it into the free opt-in link checker: it tells you whether it is the opt-in link, the store link or the internal-testing link, and what Google answers for your package right now.
What the link looks like (and the other links)
- Opt-in link:
https://play.google.com/apps/testing/com.example.app— the package name at the end is your app's application id. This is the link testers need. - Store link:
https://play.google.com/store/apps/details?id=com.example.app— after opting in, a tester can install from this ordinary Play Store page. Before opting in it shows "not found" for a closed test, which confuses people, so share the opt-in link, not this one. - Internal testing link:
https://play.google.com/apps/internaltest/…— a different track with a different link. Internal testers do not count toward the 12. Which track does what.
What must be true before the link works
- The release is "Available". On the track's Releases tab, the latest release must say it is available to testers — not "Saved", not "In review". The first release on a closed track goes through Google's app review, which can take a few days. Until then the opt-in page says the app is not available.
- Countries are set. The closed track has its own country list (Countries / regions tab). A tester whose Play account's country is not on it cannot join. Adding all countries is the simplest.
- The tester is on a list. Closed testing is closed: the Google account opening the link must be on an email list attached to the track, or a member of an attached Google Group.
- Device compatibility. If your bundle excludes the tester's device (minimum SDK, screen, ABI), the Play Store page shows "not compatible" after opt-in. Check the release's device catalog if several testers hit this.
Email lists vs a Google Group
| Email list | Google Group | |
|---|---|---|
| Setup | Testers tab → Create email list → paste addresses (or upload a CSV) | Create a group at groups.google.com, attach its @googlegroups.com address on the Testers tab |
| Adding a tester | You edit the list in Play Console | The tester joins the group themselves (set "anyone can join") |
| Best for | Friends, colleagues, paid testers who give you their addresses | Strangers from communities — one link does everything |
| Gotcha | The address must be the one the tester's Play Store is signed in with (often not their work email) | Members must open the opt-in link with the same account they joined the group with |
You can attach several lists and a group to one track at the same time. Changes take a few minutes to reach the opt-in page.
What the tester sees and does
- They open the opt-in link in a browser or on their phone, signed in with the Google account that is on your list. The page shows your app's name and a "Become a tester" button.
- They tap Become a tester. The page now says they are a tester and offers "Download it on Google Play".
- They tap that, land on the Play Store page and install. If the Store page says the item is not found, they wait a few minutes and retry — opt-ins take a moment to propagate.
- They open the app at least once (installs and sessions are what your application answers are built on) and keep it installed for the 14 days.
- To leave later, they open the same opt-in link and tap "Leave the program". Ask them not to until you have production access.
A message template that works
Subject: Could you test my app for 2 minutes? (Google Play closed test)
Hi [name], I'm launching [app] on Google Play and Google requires 12 testers before a new developer can publish. Would you be one?
1. On your Android phone, open this link signed in with your Google account ([the address I added]):
https://play.google.com/apps/testing/com.example.app
2. Tap "Become a tester", then "Download it on Google Play" and install the app.
3. Open it once, try [one specific thing], and reply with one line of feedback.
4. Please keep it installed and stay in the test for 14 days — if you leave early, Google resets my counter.
Thank you, it really helps.
Three details make the difference: naming the Google account you added (people have several), one specific thing to try, and the sentence about 14 days.
"This app is not available for this testing program": the five causes
| What the tester sees | Usual cause | Fix |
|---|---|---|
| "Not available for this testing program" on the opt-in page | The release is not rolled out, or is still in review | Releases tab → roll out; wait for review to finish |
| Same message, release is live | The tester's account is not on an attached list / group | Add the address they are signed in with; or have them join the group with that account |
| "Item not found" on the Play Store page | Opened the store link before opting in, or opt-in not propagated yet | Open the opt-in link first; wait 5–10 minutes |
| "This item isn't available in your country" | Country not selected on the closed track | Countries / regions tab → add the country |
| "Your device isn't compatible" | Min SDK / ABI / feature requirement excludes the device | Check the device catalog; lower the requirement or accept the loss |
Checking who joined
Play Console shows the number of opted-in testers on the app dashboard's closed-testing card and on the track's Testers tab, but it does not list who they are. Keep your own list, ask testers to tell you when they are in, and take a screenshot of the count on the day it reaches 12 — that date is day 0 of your 14 days. Put it into the 14-day calculator to get your earliest application date and a reminder.