How to verify a tester actually opted in, in Play Console
Updated
The number that decides whether you get production access is the opted-in tester count in Play Console, and it is the only number that matters. Not how many people you invited, not how many replied "done", and not how many have the app installed.
Find it under Testing → Closed testing → your track, beside the tester list. Check it there, and treat every other source as a rumour.
Why asking does not work
People are not lying to you. They genuinely believe they are in your test, because from their side several very different actions all feel like "I installed your app":
- They tapped your opt-in link, saw a Play Store page, and installed — but never pressed the accept button on the opt-in page itself.
- They were added to a Google Group and accepted the group invitation, which is a Google Group membership, not a test opt-in.
- They searched the Play Store for your app name and installed a different app. This happens more than you would think with generic names.
- They opted in on one Google account and installed on a device signed into another.
Every one of those produces a confident "yeah I'm in" and no change to your count. This is why the reconciliation below is worth the ten minutes.
The reconciliation, step by step
- Write down who you invited. A list of email addresses, in a note or a spreadsheet. You need your own record because Play Console will tell you how many completed the opt-in, not which.
- Open Testing → Closed testing → your track and read the current opted-in count.
- Compare. If you invited 14 and the count says 9, five people are in one of the states above.
- Go back to the five with the opt-in link specifically. Not the store link, not the APK. The opt-in URL from the Testers section, and an explicit instruction: open this link, sign in with the Google account you gave me, press the button that says you accept.
- Re-check the count. Give it a few minutes — the console is not always instant.
The Google account is the identity, not the person
The requirement counts Google accounts, not humans. That means:
- The email address a tester gives you must be the one they are signed into the Play Store with, on the device they will keep the app on. A work address they never use on their phone will not work.
- A tester with two Google accounts can opt in on the wrong one and be genuinely baffled that it did not register.
- Twelve distinct accounts are required. See can I use my own accounts as testers for why filling the gap with accounts you control is a bad trade.
Collecting the correct address up front is worth being pedantic about. On TestersWiz the Google address is captured when a tester takes a seat and shown to the developer for exactly this check — you verify it against your own Play Console list before the tester counts as admitted, because that is the only verification that means anything.
Check it more than once
Play Console shows the count now. It does not keep a history, and it does not notify you when the number falls. A test that stood at 12 for nine days and dropped to 11 on day ten looks identical, on day fourteen, to one that never dipped — except that it no longer satisfies the continuous-participation rule.
Check every few days. It takes fifteen seconds, and it is the difference between noticing a drop-out on day ten and discovering it on day fourteen. What to do when the number does fall is covered in what happens if a tester opts out.
If the count is short and you cannot work out why
There are a handful of causes beyond the obvious ones — track configuration, country availability, and the difference between a Google Group that has been attached and one that has actually propagated. They are collected in your testers opted in but the count is short, which is the guide to read before you conclude that Play Console is broken.