Google Play closed testing, explained

Who it applies to

Google requires a closed test from personal developer accounts created after 13 November 2023. If yours is an organisation account, or if it was created before that date, this step does not apply to you.

In practice: you cannot apply for production access until your app has been tested, on a closed track, by enough testers and for long enough.

What Google actually requires

You need 12 testers opted in continuously for 14 days. Three things matter in that sentence:

• 12: it was 20 testers until June 2025; Google moved it to 12 after that.
• opted in: the tester opened your closed-test link and agreed to join the track, then installed the app. An address on a list is not enough.
• continuously: fourteen days in a row, without the number ever dropping below 12.

How the count works

The count starts on the day 12 testers have opted in and installed the app. Until you get there, you are recruiting: the days do not count.

If a tester leaves the track, uninstalls, or drops off the list, and you fall back below 12, the count restarts from zero. That is the most frequent reason developers find themselves in their third month of closed testing: they recruited exactly twelve people, and two went quiet on day 9.

Recruit more than twelve testers. Fifteen who install beat twelve who promise: where to find them.

Setting the track up

• In the Play Console, open Testing › Closed testing and create a track.
• Add your testers by email address, or through a Google group if you would rather keep the list elsewhere. The address must be the Google account the person uses on the Play Store on their phone.
• Publish a release on that track and wait for it to become available.
• Send the opt-in link to your testers. Until that link is opened and accepted, they will not see your app in the Play Store.

After the 14 days

Once the condition is met, the Play Console offers to let you apply for production access. A form asks what you tested, what your testers reported and what you did about it: precise answers, with examples of bugs you fixed, land better than a vague sentence.

Which is also why your fourteen days should produce something to send — and not just twelve silent installs. The seven mistakes that restart your 14 days are worth reading before you publish your first release.

What ekko changes

ekko brings you real testers, who have declared their devices, and follows what actually happens: the first time each tester opens your app, then every session after that. Seven days without a sign of life and the tester is reminded automatically. You read “Day 6 / 14, 12 active testers” instead of counting by hand.

And because the SDK is in your app during the campaign, every “it doesn’t work” comes in with the annotated screen capture, the console, the network requests and the device. Open a campaign, the first one is free.

ekko cannot see the Play Console: it counts what it sees from your app. Google counts from the Play Console: check your track’s dashboard before requesting production access.

Questions and answers