What are Google Play tracks?

Every release in Play Console belongs to a track. Google describes three testing tracks and production:

• Internal testing: up to 100 testers per app, listed by email, for quick quality checks. You can start it before the app’s setup is finished.
• Closed testing: a wider group you choose. Play Console gives you one closed track to start and lets you create more.
• Open testing: anyone can join, and the test version is visible on Google Play, so the store listing has to be ready.
• Production: everyone on Google Play.

Testers opt in to a track, and Google lets you run several closed tests and one open test at the same time. Someone who opted in to your internal test can’t get a closed or open test until they opt out of it. Google also says developers with personal accounts created after November 13, 2023 must meet its testing requirements before an app can reach production.

Each track has its own releases, so the same build can move from internal testing to production by being promoted from one track to the next in Play Console.

In VibeView. Choose the Track in the Submit dialog (Internal testing, Closed testing, Open testing or Production), or pass --track internal, alpha (closed testing), beta (open testing) or production to vibeview submit; the default is internal. A release to Production never goes out by default: the command makes it a draft, and the dialog starts on Save as draft. Promoting a release to another track is done in Play Console. See Where it goes.