Closed Testing: Email List or Google Group? Which to Choose
Published Oct 5, 2026
Also available in: 中文
When you set up closed testing in Play Console, the Testers tab asks you to choose one option: Email lists or Google Groups.
Most people pick email lists without thinking twice. That's why test-for-test posts are full of "send me your email": you send your Gmail, they add it to their list, then they send you theirs.
Both options can get you through the 12 testers / 14 days requirement, but they work very differently, and once you pick one, switching mid-test is tricky. It's worth deciding before you start.
How each option works
Email lists: you manually add every tester's Gmail in Play Console. Only people on the list can join the test.
Google Groups: you create a Google Group and enter only the group's address in Play Console. Testers join the group themselves and become eligible automatically. You don't add anyone one by one.
With groups, there's also a shortcut at the opt-in step that a lot of people don't know about. We'll cover it separately below.
Side-by-side comparison
| Email lists | Google Groups | |
|---|---|---|
| Adding testers | Ask every new tester for their Gmail, then add it by hand | Testers join the group themselves, nothing for you to do |
| Speed | Takes effect almost immediately | A newly added group needs review, about 10 minutes |
| Switching later | Switching to groups means your list stops applying | Add as many groups as you like, existing testers stay |
Here are the points that matter most.
Group members can install directly, and that counts as opting in
A common belief is that, whichever option you use, testers must first open the web opt-in link (play.google.com/apps/testing/<package>) and tap "Become a tester" before installing from the Play Store.
After testing this many times, we found that with Google Groups, this step isn't needed. A tester who is already in the group can open the app's Play Store page (play.google.com/store/apps/details?id=<package>) and install it right away. Once installed, they're automatically counted as opted in.
With groups, that means:
- One less step for testers, and one less thing to go wrong
- When you share your app, the Play Store link is enough
- The web opt-in link still works, so the old flow is fine too
Privacy: the point most people overlook
Testing through email lists means sending your Gmail to stranger after stranger, and collecting a pile of strangers' addresses in return. Those emails sit in chat histories, and you have no control over what happens to them later.
With a Google Group, nobody has to hand over an email. They just join the group. Just make sure the group is set up properly:
- Open your Google Group and go to Group settings
- Find Who can see members
- Choose Group managers
Now people who join can't see the member list, so they can't see each other's emails.
Switching later: why it's best to start with a group
Email lists and Google Groups are either/or. If you start with an email list and later switch to groups, the people on your list are no longer on the tester list.
Google hasn't said publicly whether this resets the 14 days. To be safe:
- You haven't started yet, or only have a few testers: just go with a group, you lose nothing.
- You've been testing with an email list for several days: create your own group first, add everyone from your list using the group's Add members, confirm they're in, and only then switch to groups in Play Console.
Groups are much more flexible the other way around: Play Console lets you enter several groups at once. You can add another group next to your existing one at any time, and your current testers aren't affected at all.
One group per app, or one shared group?
Once you've chosen groups, there's one more decision: create a group just for your app, or share one with other developers?
| Each app has its own group | Everyone shares one group | |
|---|---|---|
| Groups a tester has to join | One group for every app they test | Join once, test every app |
| Waiting for sync | Wait again after joining each new group | Wait only once, the first time |
| What the developer does | Create a group, approve join requests, send the link to everyone | Add the shared group's address to your testers |
| "Item not found" | More groups means more wrong accounts and missed groups | One group, far fewer chances to get it wrong |
Separate groups per app are common in test-for-test communities, but every new app means another group to join and another sync to wait for. That's where a lot of "Item not found" errors come from: the wrong account joined the group, a group hasn't synced yet, or one was simply missed.
Common beginner mistakes
These come up again and again when we help people troubleshoot:
- The account that joined the group isn't the one signed in to the Play Store. This happens most on phones with several Google accounts. Tap your avatar in the top-right of the Play Store and make sure it's the same account you used to join the group.
- Changing tester settings but forgetting to send them for review. After adding a group or changing countries/regions in Play Console, go to Publishing overview and click Send changes for review. Otherwise the changes don't take effect.
- The closed testing track isn't available in all countries/regions. Closed testing has its own countries/regions setting, separate from production. Even if you only plan to launch in one country, you can safely select all of them for the testing track. Otherwise testers elsewhere will see "Item not found" or "This item isn't available in your country".
Summary
- Haven't started yet: go with Google Groups. Adding testers is easy, testers can install directly, and nobody has to swap emails with strangers.
- Already a few days into an email list: move your testers into your own group first, then switch.
- Want to skip joining group after group and waiting for each sync: share one group with other developers.
That's exactly how BetaLobby works: every tester shares one group, [email protected], and members can't see each other's emails. Add this group to your closed test (it can sit right next to your existing group), join it once yourself, and you can test with every other developer on the platform. Installs and daily check-ins are verified and recorded automatically by the app, so nobody has to send screenshots every day.