What it means
Google requires at least 12 testers who have been opted in continuously for at least 14 days. The period belongs to each tester, not to your test track.
- Testers who opt in, test for fewer than 14 days and then opt out don't count toward the requirement.
- If a tester opts out and opts back in later, the 14 days have to be consecutive: the earlier days don't add up.
- Google recommends telling testers they need to stay opted in for at least 14 days.
In practice, the clock for the whole test starts when your 12th tester opts in, and it only holds if at least 12 stay opted in until the end.
Why it happens
- Counting from the first tester: the test started 14 days ago, but the 12th tester only joined a week in.
- Mid-test drop-outs: a few testers left the test or the Google Group, so fewer than 12 reached 14 continuous days.
- Re-joins: testers who left and came back restarted their own count.
- Replacing testers late: a new tester who joins on day 10 needs their own 14 days.
- Cleaning up too early: removing the tester list, the Google Group or the track right after applying can drop testers out while Google is still reviewing.
- Applying on the last possible day: with no margin, a single missing day is enough.
How to fix it
Find your real start day
Note the date the 12th tester opted in. That's day 1 for the requirement, not the day you published the track.
Keep at least 12 opted in all the way
Recruit a buffer above 12 and ask every tester to stay opted in until you're approved. Don't remove testers or change the tester list during the test.
Replace drop-outs early
If someone leaves, add a replacement as soon as possible and count their 14 days from the day they opt in.
Keep the test alive while Google reviews
Leave the closed track, the tester list and the Google Group in place until you have Google's decision.
Add a margin before applying
Wait a day or two past the 14-day mark and check the numbers in Play Console again. Then apply with answers that describe the full period: our free answer helper can help.
How TestBunny helps
- Personal 14-day periods: each tester's own period is tracked day by day, so you can see when you really cross the line.
- Daily check-ins: testers confirm they're still in the test every day; testers who go quiet are flagged and replaced.
- Clear reminders: testers are told to stay opted in until the campaign ends, and not to leave the group.
- Fast start: first testers join within 6 hours of recruiting, so the clock starts early.
- Free re-test guarantee: if Google rejects production access after a completed campaign, you get one free re-test per campaign. Claim it within 30 days of completion.
The campaign report shows each tester's active days and the daily count against Google's minimum. See a sample report.
Opt-ins on our side are reported by testers; always confirm the count in your Play Console. Nobody can guarantee approval, and we don't.
Frequently asked questions
Does the 14-day period restart for everyone if one tester leaves?
No. Each tester's continuous period is their own. You need at least 12 testers who each reached 14 days; one person leaving only matters if it takes you below 12.
Can I keep updating my app during the 14 days?
Yes, and Google recommends it. Publishing new builds to the closed track doesn't reset testers' opt-in.
Should I end the closed test once I apply?
No. Keep it running with testers opted in until Google has made its decision. You may need to continue the test anyway.
Sources
Technical details were checked against the official documentation below. Menus and defaults change between versions; when in doubt, the official page wins.
Draft your application answers
A free, private helper that walks you through Google's three sections and turns your notes into well-structured drafts. Nothing leaves your browser.
Open the free helperSee what a well-documented test looks like
Daily participation, devices, scenarios, bugs and feedback, in the same report a TestBunny campaign produces. Demo data from a fictional app.
See a sample report