How to Add Testers to Google Play Console, Step by Step
Create an email list, upload a CSV, share the opt-in link and fix the most common tester problems.
Read the guide →
You added 12 email addresses to your closed test, but Play Console does not seem to count them. This is one of the most common problems with closed testing, and it nearly always has a simple cause: a tester has not really opted in, used the wrong Google account, or left the test. Here is how to find the problem and fix it.
For personal developer accounts created after November 13, 2023, your closed test needs at least 12 testers opted in continuously for 14 days. Google's help page is clear about two rules: testers who opt in, test for fewer than 14 days and then opt out do not count, and if a tester leaves and rejoins, the 14 days must be consecutive. The details are on the Play Console Help page for testing requirements.
So being on your list is not enough. A tester counts only while they are opted in. If you want the full background, read the 14-day requirement explained.
This is the number one reason. Adding an email to your list gives permission to join, but the tester must open your opt-in link and join the test.
If the email on your list is not the account the tester is signed in with, Google shows them a message that they cannot join. Ask them to switch accounts in the browser or the Play Store, then open the link again.
You can create the list, but the closed testing track has to use it. Open the Testers tab of your closed track and make sure your email list is ticked, then save. This is easy to miss. Our guide on adding testers to Google Play Console shows each step.
Testers can install only after your release on the closed track has been rolled out. If it is still a draft or waiting for review, they may see that the app is not available. After the first publication, the opt-in link can also take several hours to start working.
If the tester is in a country that is not targeted on your closed track, they will not be able to join. Check the Countries/regions tab of the track.
Testers who leave before 14 days do not count. People often leave by accident when they clear the Play Store or switch phones. Remind them to stay in.
If you use a Google Group instead of an email list, people must join the group before they can opt in to the test.
Open your app in Play Console, go to the closed testing track and look at the Testers tab and the production access section of your Dashboard. Check that the number of testers opted in is at least 12, and compare it with the people on your list. Anyone on the list who is missing from the opted-in count is a tester to chase.
If your app is already past the first few days and you are worried about the count, see what to do if production access is rejected.
| Pattern | Likely cause |
|---|---|
| Everyone is missing | List not ticked, release not available, or the link is too new |
| Only some are missing | Wrong accounts, wrong country, or they never opted in |
| Count rose then fell | Testers opted out |
| Group members missing | They never joined the Google Group. See email list vs Google Group |
Once the count is right, protect it with reminders. If the link itself fails, go to the link not working guide.
Adding an email address to a tester list only gives that person permission to join. They still have to open your opt-in link with the same Google account and click to join the test.
Google's requirement is that testers stay opted in for 14 continuous days. Engagement is looked at in the production questionnaire, so we recommend that testers keep the app installed and open it regularly.
No. They must open the opt-in link signed in with the Google account whose email address is on your tester list.
Google says the 14 days must be consecutive to count toward the minimum of 12 continuous opted-in testers. Someone who leaves and rejoins can break the count, so ask testers to stay in.