1. What opting in really means
A closed test is only visible to people who are in its audience. Before someone can install
your app, they have to be added to that audience and accept it. “Opting in” is the moment a
tester joins that group.
It is a two-sided action: you add or invite the person, and the person accepts. If either side
is missing, the tester will not see the build — and they usually will not tell you, because
from their side nothing appears to have happened.
2. Two ways to add testers
Email lists
You add each tester’s Google account email to the track. That gives you an exact list of who
was invited, which makes it easy to see who is missing later. The trade-off is that every
address has to be collected and typed correctly, and each person has to be invited
individually.
An opt-in link
You share a link, and people join themselves. This scales further with less manual work, but
you know less about who is joining and how many will actually stay. Because anyone with the
link can join, the group is only as controlled as the places you share it.
Practical tip: if you need a predictable group size, email lists give you
a clearer picture. If you need a bigger group quickly, a link plus a follow-up message a few
days later works better than a link on its own.
3. The steps a tester goes through
Every tester walks through the same short path. Each step is a place someone can quietly stop.
- Receive the invite or open the opt-in link.
- Sign in with the Google account you added or that the link expects.
- Accept the invitation to become a tester.
- Open the Play Store listing for the test.
- Install the build.
- Keep it installed, and use it, for the length of the window.
Steps 1 to 5 are quick. Step 6 is where the real testing happens, and it is the step with no
obvious completion — which is exactly why it gets skipped.
4. Why testers drop off
- Wrong account. They signed in with a different Google account than the one on the list, so no build ever appeared.
- Invitation never accepted. The email arrived, but the link was never clicked.
- Install, then uninstall. The app was opened once, then removed to free up space.
- Silence. They are technically still installed but have stopped using the app, so no feedback comes back.
- No clear expectation. Nobody told them how long the test lasts or what they were meant to do.
Notice that only one of these is a technical problem. The rest are communication problems, and
they are the reason a group that looks large on paper can behave like a much smaller one.
5. Keeping the group active
Testers stay engaged when the expectations are concrete. Tell them, in plain language:
- How long the test runs and when it ends.
- That the app should stay installed for the whole period.
- What you want from them — even “open it a few times and report anything odd” is enough.
- Where to send feedback, and how quickly they can expect a reply.
A short check-in partway through does more for retention than a long set of instructions at the
start. People continue doing things they are reminded about.
6. A short pre-flight checklist
- Confirm every tester knows which Google account to use.
- Confirm the invite was accepted, not just sent.
- Confirm the build is actually live on the track the testers can see.
- Confirm the end date is written down somewhere both sides can find.
A few minutes spent on these four points saves days of chasing people who were never really in
the test to begin with.
Note: the exact mechanics of adding testers, invitation limits and track
behaviour are set by Google and can change. Always follow the current guidance in Play Console
for your account.
Next step
If handling the invitations, the follow-ups and the drop-off is the part you would rather not
do, 12Testers organises the tester side of the run for you. Choose a package and order on
Upwork.