Google Play Testers Not Counting? Causes and Fixes
Testers added but not counted? The opt-in mistakes behind it and how to fix each one before your 14 days run out.
Read the guide →What to Do If Testers Leave Your Google Play Test
Quick answer If testers leave your closed test, replace them immediately. A tester who opts out before 14 days does not count, and every replacement needs a full 14 days of their own.
Halfway through your closed test, the number on your Dashboard drops. Someone has opted out, or never really opted in. Do you start from zero? Do you still have a chance of applying on time? The answer depends on how Google counts testers and on how quickly you replace people. This guide explains the counting rules, gives you a recovery plan for each stage of the test, and shows how to stop it from happening again.
How does Google count testers who leave?
Google's testing requirements page sets the baseline: at least 12 testers who have been opted in to your closed test, continuously, for at least 14 days. Two further points matter when people leave:
- A tester who opts in, tests for fewer than 14 days and then opts out does not count toward the requirement.
- The 14 days must be consecutive. Leaving and rejoining does not preserve earlier days.
In short, only people who are opted in today and have been opted in continuously for 14 days are counted. The same rule is behind most reports of testers not counting.
What a departure costs
| When the tester leaves | What it costs you | What to do |
|---|---|---|
| Day 1 to 3 | Almost nothing. You have 11 days of slack. | Add a replacement the same day. |
| Day 4 to 7 | The replacement finishes on day 18 to 21. | Replace now and tell everyone to stay opted in. |
| Day 8 to 12 | Up to two weeks of delay if you are right at 12. | Replace at once. If you have a buffer, you may lose no time at all. |
| Day 13 to 14 | The final day of the test is at risk. | Check that all other testers remain in. Extend the test if under 12. |
| After day 14, before you apply | You must be at 12 again before you apply. | Do not apply until the count is correct. |
The cost is far lower when you started with a buffer. With 18 testers, losing three still leaves 15, and the clock never stops. See how many testers to recruit.
Recovery plan by day
- Check the countOpen Testing > Closed testing and compare the opted-in number with your sheet.
- Find who leftAsk each person to confirm they are still in. Silence often means they left.
- Ask leavers to returnIf someone left by accident, ask them to re-join. They start again from the day they return.
- Recruit replacementsSend the link to your reserve list. See how to share the link.
- Update your sheetWrite the new start date for every replacement.
- Recalculate your finish dateLatest replacement's start date plus 14 days.
- Apply only when all 12 qualifyThen follow how to apply for production access.
How do you replace testers who left?
| Source | Speed | Reliability | Notes |
|---|---|---|---|
| Reserve list (people who said yes but have not joined yet) | Same day | High | Ask for a reserve list at the start |
| Friends and family | 1 to 2 days | Medium | Brief them clearly |
| Communities and testing groups | 2 to 5 days | Medium | Ask for Android users with Gmail |
| A testing service | Same day to 2 days | High | Real testers on real devices. See how to get 12 testers |
Add them in Play Console exactly as before. Remember that a new CSV upload overwrites the old list, so upload everyone. See email list vs Google Group.
Message templates
To a tester who left
Template: Hi [name], I noticed you are no longer in the test. If that was a mistake, could you open this link and join again: [opt-in link]? Please stay in until [date]. Thanks so much!
To a possible replacement
Template: Hi [name], I am short of one tester for my Android app. Could you help for 14 days? It takes 2 minutes to join and a minute a day to open the app. Use the Google account [email]. Link: [opt-in link].
Prevention schedule
| Day | Action |
|---|---|
| Before day 1 | Recruit 15 to 20. Tell people the test lasts 14 days and they must not leave. |
| Day 1 | Send the link. Ask for a reply. |
| Day 3 | Reminder: open the app, try one feature. |
| Day 7 | Check the count. Replace anyone missing. |
| Day 10 | Reminder: stay in. Four days left. |
| Day 13 | Final count check. |
| Day 14 | Confirm 12 or more qualified testers, then apply. |
Why testers leave
- They did not understand that leaving cancels their contribution.
- They cleaned up their phone and uninstalled the app, then opted out of the test.
- They changed phones or Google accounts.
- They forgot. Silence for a week is the usual reason.
- They had a problem with the app and gave up. Ask for feedback and fix it.
If you see a pattern, change the briefing. Telling people why 14 days matters reduces exits far more than reminders alone. If your problem is instead a link that never worked for some people, read the link troubleshooting guide.
Our guarantee: 12AppTesting testers stay opted in for the whole period, and we replace anyone who leaves. Every package includes the 100% Production Access Guarantee.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
Sources
- Google Play Console Help: App testing requirements for new personal developer accounts
- Google Play Console Help: Set up an open, closed, or internal test
Frequently asked questions
What happens if a tester opts out before 14 days?
Google says that if a tester opts in, tests for fewer than 14 days and then opts out, they do not count toward the requirement.
If a tester leaves and rejoins, do the days still count?
Google says the 14 days must be consecutive. A person who leaves and comes back should be treated as starting again.
Should I replace testers right away?
Yes. A replacement needs their own 14 days, so each day you wait is a day added to your finish line.
How many extra testers should I recruit?
A buffer of roughly 30 to 60 percent is common. For 12 required testers, 15 to 20 is a sensible range.
Does the whole 14 days restart when one tester leaves?
Google does not describe it that way. What matters is that at least 12 testers have been opted in continuously for 14 days. Replacing one person affects that person's count, not everyone's.
What if I am under 12 on day 14?
Keep the test running, recruit replacements and wait until at least 12 testers have been opted in for 14 days in a row before applying.
