You add an email address to the tester list. The tester opts in with a Google account. Those two things need to match.
That sounds obvious until a tester says, "I opted in," and the Console count does not move. Nine times out of ten, the email on the list and the Google account on the phone are not the same.
The two roles
The tester email is the identifier you add in Play Console. It tells Google who is invited.
The Google account is what the tester uses in the Play Store to accept the invite and install the app. It must be able to receive the invitation and access Google Play.
For most people, the email address is the Google account. For others, it is an alias, a work account, or a second address that forwards mail.
Why a mismatch breaks the test
If you add alex@example.com but Alex opts in with alex.personal@gmail.com, Google may not connect the opt-in to the invitation. The tester may see an error, or the app may not appear.
The Console count stays the same. The tester insists they did everything right. Both can be true.
Common mismatch cases
- A tester uses a work Google account instead of the personal one you added.
- A tester has two Gmail accounts signed in and the wrong one is active in Play Store.
- The email you added is an alias that forwards to a different Google account.
- The tester changed their Google account after you added them.
- A managed Google Workspace account restricts Play Store access.
- The tester typed the email with a typo when you added it.
How to fix it
- Confirm the exact email on the tester list.
- Ask the tester which Google account is active in the Play Store app.
- If they differ, either add the correct account or ask them to switch accounts.
- Send a fresh opt-in link after the list is correct.
- Check the Console count.
If you remove and re-add a tester, their 14-day clock can reset. Do it only when necessary.
What not to ask for
Do not ask for the tester's password, recovery codes, or full account access. You do not need to sign in as them.
A screenshot of the account shown in Play Store and the opt-in screen is enough to diagnose most problems.
A note on work and school accounts
Some Google Workspace accounts are managed by an organisation and may not be able to install apps from outside their allowed list. If a tester is using a work account, ask whether Google Play access is restricted.
A personal Google account is usually the simplest choice for a closed test.
The short version
- The tester email is the invitation identifier.
- The Google account is what actually opts in and installs.
- They should match.
- Most "opted in but not counted" problems are account mismatches.
- Fix the list or the account, then resend the link.
Next: tester opted in but not showing in Play Console? or how to add testers in Play Console.
Our team’s note
If this answered the question but your situation still feels messy, send us the screenshot or the rejection email. Some things are easier to solve in a two-minute conversation than another article.