Countries and regions for a closed testing track: why it matters

Every closed testing track in Play Console has its own list of countries and regions. By default it copies your production countries, but you can unsync it and choose the countries yourself. It matters because a tester whose country isn't on the closed track will most likely not be able to get your test, even if they are on your tester list and have the opt-in link.

This is one of the quietest mistakes in closed testing. Play Console doesn't clearly flag a missing tester country, and the tester typically just sees that the app isn't available.

How country availability works for testing tracks

Google's help on country distribution says that for testing tracks, "Country availability is synced with production by default." In other words, whatever countries you picked for your production release are also the countries where your closed test is available (Country distribution).

For a brand-new app, that default can be surprising. Many first-time developers haven't thought about production countries yet, or they picked one or two countries early on and forgot. Their closed test then inherits that short list.

You can break the link between the two:

• Unsync countries/regions lets the closed track have its own list.
• Edit countries then lets you tick exactly the countries you want for testing.

Two related points:

• Internal testing has no country targeting. Country settings don't apply to the internal track, so internal testers can be anywhere. But internal testing doesn't count toward the 12-tester, 14-day requirement. If you're unsure which track to use, see internal vs closed vs open testing.
• Open testing isn't available yet for new personal accounts. It unlocks only after you gain production access, so for now the closed track is the one to set up.

Step by step: setting countries on your closed track

1. In Play Console, select your app and go to Testing > Closed testing.
2. Find your closed track and click Manage track.
3. Open the Countries/regions tab.
4. If the list is synced with production, choose Unsync countries/regions.
5. Click Edit countries and select every country where your testers live.
6. Save.
7. Go to Publishing overview and send the changes for review, the same way you send any other track change.

Menu labels move around from time to time. If you don't see this exact path, look for the Testing section in the left menu and the track's Countries/regions tab. The rest of the track setup is covered in how to create a closed testing track.

Why this decides whether testers can join

Google's documentation describes country availability for testing tracks, but it doesn't spell out every symptom a tester sees. The reasonable reading, and what developers commonly report, is that a tester in a country you didn't select won't be offered the test version. That's an inference rather than a sentence Google publishes, so treat it as likely, not guaranteed. In practice it's not worth the risk: if a tester's country is missing, add it.

Symptoms that often point to a country problem:

• The tester opened the opt-in link and accepted, but the Play Store page shows the app as unavailable.
• Several testers in the same country fail while testers elsewhere are fine.
• Everything works for you, but you're in a country that happens to be on the list.

Account and device problems produce similar symptoms, so check those too. The tester's side of the flow is described in how testers join your closed test, and it's worth reading what counts as an opted-in tester so you know when a tester actually starts counting.

Testing countries are not a launch decision

Choosing countries for the closed track doesn't commit you to launching in those countries. After you unsync, the closed track list and the production list are separate. You can test with people in one set of countries and launch production in another set later.

A few practical rules help:

• Add countries before testers start. It's simplest when every tester's country is on the list before you share the opt-in link.
• Don't remove a country mid-test. Removing a country that your testers are in may cut them off and put their 14 days at risk.
• Re-check after editing production. If you left the track synced and later change production countries, the closed track changes too.
• Remember the review step. Saving isn't publishing. Changes wait in Publishing overview until you send them for review.

Should you just select every country?

Selecting all countries removes the risk that you forgot one tester's country. Some developers do that on purpose for testing. Others prefer a short list that matches their testers exactly, so they always know who can access the build.

Both are reasonable. What matters is that the list includes every tester's country before the test starts, and that you don't shrink it while the test runs. If your app has country-specific content or legal limits, think about those separately for production; the closed track is a test, but it still makes your app available to the people on the list.

Using testers from another country

If your testers live outside your own country, their country must be on the list even if you have no plans to launch there. GoPlayTester's testers, for example, are based in Indonesia, so our setup guide includes adding Indonesia to the closed track's countries alongside our tester group. It's a small step, and it's the one people skip most often.

Checklist

• You know whether your closed track is synced with production.
• If synced, you've checked that the production list covers all testers.
• If unsynced, every tester's country is selected under Edit countries.
• You sent the change for review in Publishing overview.
• You won't remove countries until the test and the production application are done.

Once the track, countries and testers are right, the rest is time and real use. If you need the testers, you can order a 14-day closed test from GoPlayTester. Google still makes the final decision on production access.