Play Console uses a lot of specific terms, and small differences in wording matter. "Invited" and "opted in" are not the same, and neither are "saved" and "sent for review". This glossary explains the terms you'll meet during closed testing and production access, using Google's own wording where it exists.
Terms are grouped by stage. Menu names are shown in bold as they appear in Play Console.
Accounts and verification
Personal developer account. A Play Console account registered to an individual. The testing requirement applies to personal developer accounts created after November 13, 2023. See personal vs organization developer account.
Organization account. An account registered to a company or other organization. It requires a D-U-N-S number, an organization website and a phone number. Google's testing requirement page covers personal accounts only.
Registration fee. "A US$25 one-time registration fee." You must be at least 18 years old.
Identity verification. Proof of who owns the account. Personal accounts without a verified payments profile provide an official government ID; accepted documents vary by country.
Device verification. New personal accounts must "verify that they have access to a real Android mobile device using the Play Console mobile app". The device must be a "non-rooted physical Android mobile device that runs at least the Android 10". The task appears on the Home page.
Android developer verification. A separate program, announced in August 2025, that requires apps installed on certified Android devices to come from verified developers, including apps outside Google Play. It is not the same thing as the 12-tester rule.
Tracks and releases
Track. A channel you release builds to. In order: internal, closed, open, then production. Internal, closed and open testing compares them.
Internal testing. A quick track for "up to 100 testers per app". Builds are "normally available to testers within seconds", and testers can be in any country. It does not count toward the testing requirement.
Closed testing. A track for a group of testers you choose. It requires completing app setup first. This is the only track that counts toward the requirement.
Open testing. A public testing track. For new personal accounts, it "becomes available after you gain production access."
Production. The track for your public release. It stays disabled until you meet the testing requirement and are approved.
Release. A specific version of your app, with one or more app bundles, sent to a track.
Android App Bundle (AAB). The publishing format Google requires: "From August 2021, new apps are required to publish with the Android App Bundle." See uploading your first app bundle.
Play App Signing. Google manages your app's signing key. "When publishing your app to Google Play for the first time, you must also configure Play App Signing."
Version code. An internal number for each build. Every new upload needs a higher one than the last. Updating your app during a closed test explains how it works mid-test.
Target API level. The Android version your app is built to target. From August 31, 2026, new apps and updates for phones and tablets "must target Android 16 (API level 36) or higher."
Testers and opt-in
Tester list (email list). A list of Google account emails you attach to a track. Limits: up to 200 email lists per account, each with up to 2,000 users, and up to 50 lists per track.
Google Group. An alternative to email lists, using an address like [email protected]. "Only members of the specified Google Groups can join your test."
Opt-in link. The link testers open to join. You copy it from the track's Testers tab. "The opt-in link displays only when an app status is 'Published'", and after the first publish it "can take several hours to become available to testers."
Opted in. A tester who opened the opt-in link and accepted. Being on a list only means invited. "Each tester needs to opt in using the link." See what counts as an opted-in tester.
Continuously opted in. Staying opted in without a break. "If a tester opts out and opts back in later, the 14 days must be consecutive to count."
Testing requirement. For new personal accounts: "a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days."
Tester engagement. How actively testers use the app. Google may ask for more testing because of "insufficient tester engagement during the testing period." Keeping the app installed and using it regularly is strongly advised.
Testing feedback. Private feedback from testers, found under Monitor and improve > Ratings and reviews > Testing feedback. It "won't affect your app's public rating."
License testing. A separate setup for testing purchase flows. License testers are not the same as closed testers and don't count toward the 12.
Publishing and review
Publishing overview. The page where you see pending changes and send them to Google.
Send for review. The button in Publishing overview that submits your changes. Until you click it, nothing reaches Google.
Changes not yet sent for review. Where your saved edits wait until you send them.
Managed publishing. A setting that lets you choose when approved changes go live, instead of publishing them automatically.
Countries/regions. Where a track is available. For testing tracks, "Country availability is synced with production by default"; you can Unsync countries/regions and then Edit countries. If testers are in Indonesia, the closed track must include Indonesia.
Policy and declarations
App content. The declarations under Policy and programs > App content: privacy policy, ads, sign-in details (app access), target audience and content, content rating questionnaire, permissions declarations and others. See declarations that block your review.
Data safety form. A declaration of what data your app collects and shares. Required for closed, open and production tracks, even if you collect no data. Apps only on internal testing are exempt.
Sign-in details (app access). Login credentials for reviewers. Google asks you to "provide valid, working login credentials in Play Console so reviewers can fully test your app's features."
Production access
Apply for production. The button on the Dashboard you click after the 14 days. The form has three sections: about your closed test, about your app or game, and about your production readiness.
Production access. Approval to publish to production. After it, the Production page and Open testing are unlocked.
More testing required. The outcome when Google wants you to keep testing. Listed reasons include "having fewer than 12 opted-in testers or insufficient tester engagement during the testing period."
Review time. For the application: "Review usually takes seven days or less, but can occasionally take longer." See how long the production access review takes.
Quality tools
Pre-launch report. An automatic, free report "generated when you upload an app bundle or APK". A crawler runs the app on test devices and checks stability, compatibility, performance and accessibility.
Android vitals. Quality data from users who opt in. Core vitals include the user-perceived crash rate (bad-behavior threshold 1.09% overall) and user-perceived ANR rate (0.47% overall).
ANR. "Application Not Responding": the app froze long enough for Android to show a dialog asking the user whether to wait or close it.
For the setup itself, our guide walks through adding a tester group to a closed track, and the production access guide has example answers for the form. GoPlayTester is an independent service that provides 12+ real testers for the 14-day closed test; Google makes the final decision on production access.
