Google Play Tester Not Showing as Active: Why and How to Fix It

Your tester says they completed everything. You can see them in the Google Group. But Play Console still shows the same number — or worse, they're not counting toward your 12. This is one of the most common issues in the closed testing process, and it has several distinct causes.

First: understand what "active" actually means

Google counts a tester as active when all of the following are true:

1. Their email address is in your Google Group (or Workspace domain)
2. They clicked the opt-in link on an Android device and tapped "Become a tester"
3. The app is installed on that device

All three conditions must be met simultaneously. A tester who has done steps 1 and 2 but hasn't installed the app is not active. A tester who installed the app directly from a previous source without going through the opt-in link is not active.

Reason 1: Play Console hasn't updated yet

Play Console updates tester counts with a delay — this can range from a few hours to over 24 hours. If your tester just completed the opt-in steps, wait before assuming something is wrong.

What to do: Wait 24 hours and check again. If the count still hasn't updated after 24 hours, the issue is real and one of the causes below applies.

Reason 2: Tester opened the opt-in link on desktop

The opt-in link only works on Android. If your tester opened it on a computer, they may have seen a success message or a Play Store web page — but they won't be counted as active because there's no Android device linked to the action.

How to identify it: Ask the tester if they clicked the link on their phone or computer. Many people see the link on desktop and click it there by mistake.

What to do: Ask the tester to open the opt-in link again, this time directly on their Android device. They should see a page with a "Become a tester" button and then be directed to the Play Store to install the app.

Reason 3: Tester joined the Google Group but skipped the opt-in link

Being in the Google Group is a prerequisite, not the opt-in itself. Some testers accept the Google Group invite and assume they're done. They aren't.

How to identify it: Ask the tester to describe what they did step by step. If they say "I accepted the email invite" but can't describe clicking "Become a tester" in the Play Store, they skipped the opt-in.

What to do: Send them the opt-in URL again (find it in Play Console under your closed testing track) and ask them to open it on their Android phone and complete the process from scratch.

Reason 4: Tester is using a managed Google Workspace account

Corporate or school Google accounts (managed accounts) often cannot participate in consumer app testing. This is the most frustrating cause because the tester has no visible error — the opt-in process appears to work, but the tester doesn't count.

How to identify it: Ask if the email address they used ends in a custom domain (e.g. @company.com instead of @gmail.com), or if it's a school or work account. Managed accounts look like regular Google accounts from the user's perspective.

What to do: Ask the tester to use a personal Gmail account instead. They'll need to be added to your Google Group with their personal email, then redo the opt-in process with that account on their device.

Reason 5: Tester's device isn't compatible

If the tester's Android device doesn't meet your app's minimum requirements (API level, screen size, hardware features), they can complete the opt-in but won't be able to install the app — and without the install, they're not active.

How to identify it: Ask the tester if they were able to find and install the app from the Play Store after opting in. If the Play Store showed "This app isn't compatible with your device," that's the issue.

What to do: Either relax your app's minimum requirements (if possible) or replace this tester with someone on a compatible device. Expanding compatibility requirements mid-test doesn't affect the 14-day counter.

Reason 6: Wrong Google account on the device

Testers often have multiple Google accounts on their Android phone. If they're signed into the Play Store with a different account than the one in your Google Group, the opt-in won't work — the Play Store won't recognize them as a tester.

How to identify it: Ask the tester to check which account is active in the Play Store. On Android, open the Play Store, tap the profile icon in the top right, and check the account name at the top. It must match the email you added to the Google Group.

What to do: Ask the tester to switch to the correct account in the Play Store before opening the opt-in link. On most Android devices, you can switch accounts by tapping the profile icon and selecting a different account.

Reason 7: App not yet available in tester's country

If you've set geographic restrictions on your app, testers in excluded countries won't be able to install it even after opting in.

How to identify it: Check your app's country availability in Play Console under Store presence → Store settings. If you've restricted countries, confirm your testers are in an included region.

What to do: Expand country availability to include all countries, or find testers in your target regions.

The fastest way to verify a tester is properly active

Ask your tester to do this on their Android phone:

1. Open the Play Store
2. Search for your app by name
3. Check if they can see and install your app (if they weren't in closed testing, they'd see "not available" or nothing at all)
4. Confirm the app is installed and opens successfully

If they can search and find your app in the Play Store, they're likely properly opted in. The count in Play Console should update within 24 hours of them completing the install.

Frequently asked questions

Related articles