A closed test counts Google accounts, not people. If a tester is on your list as one Gmail address but opts in or installs with another, Play Console sees the wrong account, or no tester at all. The fix is to line up three things: the address on your tester list, the account that accepts the opt-in, and the account the Play Store app uses on the phone.
Why this happens so often
Most Android users have more than one Google account: a personal Gmail, a work account, an old account from school. Browsers and the Play Store app quietly pick one of them. When a tester taps your opt-in link, it opens with whichever account the browser considers active. That may not be the one you invited.
Google's help says "Users need a Google Account or a Google Workspace account to join a test." In practice, testers must use the Google account you added to the list (or the account that is a member of your Google Group). Any other account is most likely not recognized as your tester.
The symptoms
Account mismatch shows up in a few typical ways:
- The tester says the opt-in page shows an error or says the test isn't available, while other testers can join fine.
- The tester opted in, but the Play Store on their phone shows no install option for the test.
- Your tester count in Play Console is lower than the number of people who say they joined. See how to check how many testers have opted in.
- A tester joined your Google Group with one address and opted in with another.
How to fix it: step by step
1. Confirm which address is invited
Ask the tester for the exact email address they gave you, then check it against your email list or Google Group members. Typos are common, and so are addresses that look alike, such as a dot in a different place or a different domain.
2. Check the browser account before opting in
Ask the tester to open the opt-in link and look at the profile picture or email shown in the top corner. If it's the wrong account, they should switch to the invited one. If switching is confusing, the simplest route is a private or incognito window: open the link there and sign in with the invited account only.
3. Accept the opt-in with the right account
Google's flow shows an explanation of tester responsibilities and then a link to opt in. The tester must complete that step while signed in as the invited account. Our article on what the opt-in flow looks like for testers shows each screen.
4. Match the Play Store app
On the phone, open the Play Store app, tap the profile picture and switch to the same account. If that account isn't on the phone, add it in the phone's account settings first. Then open the app's Play Store link again and install.
5. Confirm the count
Once the tester is in with the right account, check your opted-in tester count again. Don't assume it worked until you can see the tester counted.
What about the days already lost?
This part surprises people. The 14 days belong to the account, not to the person. If the tester's opted-in account isn't the one on your list, it was never counted as your tester, so none of those days apply. The right account starts its own count on the day it opts in. The right account starts its own count on the day it opts in.
Google's rule also says that if a tester opts out and opts back in later, "the 14 days must be consecutive to count". So switching accounts in the middle of the test, or opting out and back in, means a new start for that tester.
That's why it pays to catch mismatches in the first day or two. If a fix will push a tester's 14 days past your planned date, consider adding a replacement tester as well. Our article on the closed testing timeline explains how the dates add up.
Should you add the "wrong" account instead?
Sometimes the easier fix is to add the account the tester actually used to your email list. That can work, as long as:
- it's still a real person's own account, on their own device
- you save the list and send the change for review in Publishing overview
- you accept that, for counting purposes, the account starts fresh from when the change is live and it is opted in
Don't use this to pad your numbers with extra accounts that belong to the same person. The requirement is about real testers, and Google can ask for more testing if engagement looks insufficient.
How to prevent it
- Ask testers for the Gmail address that is signed in to the Play Store app on their phone. That's the account that matters most.
- Send the instructions in writing, with the exact address you invited.
- Tell testers to open the link on their Android phone, where the browser and the Play Store usually share the same main account.
- Check the opted-in count on day one, not day ten.
A Google Group can make this easier, because testers join the group with the account they will use. It isn't a cure, though: they still have to opt in with that same account. If you are choosing between the two methods, see email list or Google Group.
Key takeaways
- The account on the list, the account that opts in and the Play Store account must all be the same.
- The 14 days are counted per account, and a switch starts a new count.
- Catch mismatches on day one by checking the opted-in count.
GoPlayTester testers join through our Google Group with the same accounts they test with, and our setup guide shows how to add the group to your track. If you'd rather not manage tester accounts at all, you can order a 14-day test.
