Because adding someone to your tester list does not opt them in.
The count only moves when each person opens your opt-in link and completes the opt-in themselves. Until they do that, Play Console is correct: zero.
If you are staring at this message, nothing is broken and nothing is lost. You are one step short of the one that counts.
What that number actually counts
It counts completed opt-ins. Nothing else.
It does not count emails on your list. It does not count installs. It does not count people who promised they would do it tonight.
Google’s own description of the flow is short: after clicking the opt-in link, testers receive an explanation of tester responsibilities and a link to opt in [1]. There are two steps in that sentence, and most testers stop after the first.
Seven reasons the count is still zero
Work down this list. One of these is almost always the answer.
1. You added emails but never sent the link
This is the most common one by a distance. Adding an address to a tester list is a permissions change on your side. Google’s documentation describes no automatic invitation email to testers, and in practice none arrives.
You have to send the opt-in link yourself, by whatever means you like.
2. They opened the link but did not finish
Opening the link shows them a page explaining tester responsibilities. They then have to complete the opt-in on that page [1]. Plenty of people read it, mean to come back, and close the tab.
3. Your release is not actually published yet
The opt-in link only appears once the app status is Published. Apps in Draft or Pending publication show no opt-in link at all [1].
If you sent a link before the release went live, it did not work for anyone.
4. You used a Google Group and they have not joined it
With the Google Group method, users must join the group before opting into your test [1]. Someone who opens your link before their membership is approved gets told the app is not available.
The order matters. Group first, opt-in second.
5. They used a different Google account
The account that opts in has to be the account you added. People often have a personal address on the phone and a work address in your list, so the opt-in silently applies to nobody.
6. Their country is not on the track
Closed testing is country targeted. Testers can only access the app if their Play country is in the countries you selected for that track [2].
This one is easy to miss, because everything on your side looks correct. Check the countries on the closed testing release itself, not on your production listing.
7. It has not propagated yet
Changes to a test take time to reach everyone. Google describes this as taking several hours [1]. If you added someone twenty minutes ago, wait before assuming something failed.
| What you are seeing | Likely cause | Fix |
|---|---|---|
| Count is 0, testers say they never got anything | No link was sent | Send the opt-in link yourself |
| Count is 0, testers say they clicked the link | They did not finish the opt-in | Ask them to reopen it and complete the step |
| Testers see “not available” | Group not joined, or wrong country | Join the group first, check track countries |
| No opt-in link anywhere in Console | Release is not Published | Publish the closed testing release |
| Count is lower than the number you added | Normal. Some people never finish | Recruit more than twelve |
How long before the number updates?
Give it several hours before you worry [1].
The count is not live. A tester who opts in during the morning may not show up until the afternoon, which sends a lot of developers hunting for a problem that is already fixed.
Check once, wait, then check again. Do not resend links in a panic, because a second link does not make the first one work faster.
Does a zero count mean my 14 days have not started?
Yes, and that is the part worth acting on quickly.
The clock runs on opt-in status. Each tester needs 14 continuous days opted in, so their fortnight begins the moment they complete the opt-in, not when you added their email [3].
A tester who opts in three days late finishes three days late. If you need twelve people at once, the slowest person sets your date.
How to stop it happening again
Send one message that contains everything, rather than a bare link.
- The opt-in link, on its own line so it is easy to tap.
- Which Google account to use, spelled out, because this is where most of the silent failures come from.
- The words “you are not finished until you complete the opt-in”, because most people assume clicking the link is the whole job.
- What you need from them afterwards, which is fourteen days of opening the app.
Then check the count a few hours later, before you count day one as started. Our guide to inviting testers properly covers the full sequence.
Frequently asked questions
Why does Play Console say 0 testers currently opted in?
Because nobody has completed the opt-in yet. Adding an email address to a tester list does not opt that person in. They have to open the opt-in link and finish the process themselves before the number changes.
Does Google email my testers when I add them?
Google’s documentation describes no automatic invitation email, and in practice testers do not receive one. Sending the opt-in link is your job.
My tester says they clicked the link. Why is the count still zero?
Clicking the link only opens a page explaining tester responsibilities. There is a further step to complete on that page. If they stopped there, they are not opted in.
How long does the opted-in count take to update?
Several hours. The number is not live, so a tester who opts in this morning may not appear until later in the day.
Why can my tester not find the app at all?
Usually the release is not published yet, they have not joined the Google Group, or their Play country is not among the countries selected for the track.
Does the 14 day clock start when I add a tester?
No. It starts when that person completes the opt-in. Each tester needs 14 continuous days opted in, so a late joiner finishes late.
How many testers should I add to end up with twelve?
More than twelve. Some people never finish the opt-in, and a buffer means one slow reply does not hold up your whole test.
If chasing opt-ins is the part you are tired of
Option 1: verified testers assigned to you
- Starter, ₹999 gives you 15 verified Android testers for the full 14 days.
- Pro, ₹1,699 gives you 25 testers, plus a detailed ASO report and priority support.
- Testers assigned within 6 hours, and they complete the opt-in themselves, so the count moves without you chasing anyone.
- They open your app daily and stay active for the full period.
- Anyone who goes inactive is replaced.
- A feedback report at the end, plus pre-filled answers for the 10 production access questions.
- 100% production access or your money back.
More than 10,000 apps have reached production this way. Submit your app to start.
Option 2: join a free Pack of 16
If you would rather trade time than money, the Testers Community app puts you in a pack of 16 developers. Everyone tests each other’s apps for 16 days, opening every app daily and leaving feedback. Inactive members get replaced.
Either way, read the full requirements before you start. It is also worth knowing that every new app needs its own opt-ins, and that an uninstall does not reduce the count.
