Tester Exchange Open Tester Exchange

How to set up a closed testing track in Play Console, step by step

Updated November 2026

Before your 14-day clock can start, you need a closed testing track that is published, has testers attached, and gives you an opt-in link that works. Most problems later on, such as testers seeing "app not available", come from a step missed here. This guide follows the current Play Console menus (Test and release, then Testing, then Closed testing) and Google's Help Center.

Real people open your app on their own phones for 14 days. Pay once, or test other apps for free.Get 12 testers

Before you start

  • A Play Console developer account with identity verification finished.
  • Your app created in Play Console, with the store listing, content rating, target audience, data safety and other App content declarations filled in. Play Console won't let you send a release for review while required items are missing.
  • A signed Android App Bundle (.aab) with a package name you are happy to keep forever. You can't change it later.
  • A plan for your testers: at least 12, ideally 15, real people with Android phones and Google Accounts.

1. Open or create the closed track

  1. In Play Console, pick your app.
  2. Go to Test and release, then Testing, then Closed testing.
  3. Play Console gives you a default closed track (often called Alpha). Use it. You can create extra closed tracks, but one is all you need for the requirement.
  4. Click Manage track.

2. Choose countries and regions

Open the Countries / regions tab and add the countries where your testers live. A tester in a country you didn't select will not be able to install the app.

Google notes that changes to distributed countries apply across tracks, and that additional closed tracks don't support their own country targeting. If your testers are spread around the world, the simplest choice is to add every country you can legally ship to.

3. Add testers: email list or Google Group

Open the Testers tab. You have two options, and you can use both on one track.

  • Email list: click Create email list, name it, then type addresses or upload a CSV. Google allows up to 2,000 users per list. Uploading a CSV overwrites the addresses already in that list. Every address must be the Google Account the tester uses on their phone's Play Store.
  • Google Group: enter the group's address, such as yourgroup@googlegroups.com. Only members of the group can join your test, and they must join the group before they opt in. Adding someone to the group is all you do; you don't touch Play Console again.

If you use Tester Exchange, add the group testerexchange-testers@googlegroups.com under Google Groups and save. That one address lets every tester we send install your app. See also the guide on Google Group vs email list.

4. Add a feedback channel

On the same Testers tab, add a feedback URL or an email address. Testers see it when they join. You will need to summarize tester feedback in the production access form, so make it easy: a short Google Form or a dedicated email address works.

5. Create the release and send it for review

  1. On the closed track, click Create new release.
  2. Upload your .aab. Let Play App Signing manage your key unless you have a reason not to.
  3. Add a release name and short release notes, for example "First closed test build".
  4. Click Next, fix any errors, then Save.
  5. Go to Publishing overview and send the changes for review. If managed publishing is on, you also have to click Publish after approval.

Closed test releases on new accounts are reviewed before they go live. Times vary from hours to several days.

7. Check that the 14 days are counting

Your Dashboard shows the closed testing requirement and how many testers are opted in. Check it every couple of days. If the number falls under 12, recruit replacements straight away, because the requirement counts 12 testers opted in continuously.

During the test, upload at least one new build to the same track. It shows Google you acted on feedback, and testers on the track get the update automatically.

Frequently asked questions

Can I use internal testing instead?

No. The requirement needs a closed test. Google also says people opted into your internal test can't join a closed test until they leave the internal one.

Should I use an email list or a Google Group?

A Google Group is easier when testers come and go, because you never edit the track. An email list is fine for a fixed group of friends. You can use both.

Why don't I see the opt-in link?

It only shows once the release on the closed track is published. Check Publishing overview for pending review or changes not yet sent.

Does a tester need a Google Account?

Yes. Google says users need a Google Account or Google Workspace account to join a test, and it must be the account on their phone's Play Store.

Can I make the closed test app paid?

You can, but Google says testers must buy paid apps in closed tests. Keep the test app free to avoid losing testers.

Real people open your app on their own phones for 14 days. Pay once, or test other apps for free.Get 12 testers

More guides