How to Remove Inactive Testers from Google Play

Opted-in but never installed. Installed once, never opened. Joined the Google Group but gone silent. Inactive testers are a normal part of Google Play closed testing — here's how to identify and remove them without disrupting your 14-day window.

Why inactive testers matter

Testers who opted in but never installed the app don't count toward your 12 active testers. They're taking up a spot in your Google Group and potentially inflating your expectations about how close you are to the 12-tester requirement.

Knowing who is genuinely active — and removing or replacing those who aren't — helps you manage your testing pool accurately and avoid surprises late in the process.

How to remove a tester via Google Group

If you're managing testers through a Google Group (the standard setup), removing someone from the group removes their access to the testing track:

1. Go to groups.google.com
2. Open your testing group
3. Click Members in the left sidebar
4. Find the member you want to remove
5. Click their name, then click Remove from group

Their access to the testing track is revoked automatically. They won't receive an error message — they'll just no longer be able to update the app through the testing track.

How to remove a tester via Play Console

If you added testers by individual email address in Play Console (rather than through a Google Group), you can remove them directly:

1. Open Play Console
2. Go to your app → Testing → Closed testing
3. Click Manage testers
4. Find the tester's email in the list
5. Remove them using the delete/remove option next to their email

Will removing an inactive tester reset the 14-day counter?

This is the most important question, and the answer is: only if they were counted as active and removing them drops you below 12.

A tester who opted in but never installed the app is not counted as active. Removing them has zero effect on your counter — they weren't contributing to your 12 in the first place.

A tester who installed and opened the app is counted as active. If removing them brings your active count from 12 to 11, your 14-day counter pauses until you get back to 12.

Rule of thumb: before removing anyone, check your active tester count in Play Console. If you're at exactly 12, don't remove anyone without a replacement lined up.

How to identify who is actually active

Play Console shows your total active tester count but doesn't provide a per-tester breakdown. You can't see a list of "who installed" vs. "who only opted in." This is a real limitation in Play Console's reporting.

Workarounds developers use:

• Ask testers directly to confirm they installed and opened the app. Simple, but relies on them responding.
• Use in-app analytics (Firebase, etc.) to see unique users. If you have 12 Google Group members but only 8 unique users in Firebase, 4 people opted in without installing.
• Compare Group members vs. active count in Play Console. If you have 15 Group members but only 10 active testers, 5 people opted in without installing.

What to do with inactive testers

Option 1: Remove and replace

If you have replacement testers available, remove the inactive ones and bring in people who will actually install. Make sure your count stays at 12+ while you do this.

Option 2: Send them a reminder first

Sometimes testers mean to install but forget. A direct message with the opt-in link and a reminder to open the app after installing recovers a portion of them. Give it 24–48 hours before deciding to remove.

Option 3: Leave them in place if you're above 12

If you have 16 members in your group and 13 active testers, the 3 inactive ones aren't hurting anything. No need to remove them — they might still install, and removing them carries no benefit.

How many testers should you have in total?

The standard advice from developers who've been through this: aim for 14–16 testers, not exactly 12. The buffer gives you room for:

• Testers who opt in but don't install (1–3 per batch is common)
• Testers who install but uninstall mid-test
• Testers whose accounts run into issues
• Testers who switch devices or Google accounts

With 15 testers, you can absorb 3 dropouts and still maintain the 12 required for your 14-day window. With exactly 12, a single dropout resets everything.

Frequently asked questions

Related articles