On October 21, 2026 a tester on one of PeerPlay's paid campaigns sent me a support email with two screenshots. One card said "Bonus 13/12 days", but no bonus had arrived. The other, for a new app he had just joined, said "joined day 2", even though he had joined the evening before.
Both questions came down to the same thing: which day counts. It is the most confusing part of Google Play's 12 testers, 14 days rule, for testers and developers alike, so here is what that email taught me.
What happened
He joined the campaign late in the evening. His first recorded test came after midnight, so PeerPlay counted him from campaign day 2. On his card, day 1 was grey and marked "before you joined".
PeerPlay's paid campaigns run on one shared 14-day calendar for every tester. Joining on day 2 does not give you your own 14 days, but the day before you joined does not count as missed either. He could still earn the full bonus by testing on 12 of the remaining 13 days, including day 13 or 14.
The bonus question had a simpler answer. The bonus is not paid the moment a tester reaches 12 days. The server pays it once, after day 14 of the campaign has ended, with a 12-hour margin for time zones. "13/12" meant he had already done enough and the campaign was still running.
Google counts your test, not each tester
The same logic applies to Google's own rule, and it is where many developers get confused. For newer personal developer accounts, Google asks for at least 12 testers opted in to your closed test for 14 days in a row before you can apply for production.
As far as Google documents it, that is a count on your test, not a personal 14-day streak for each tester. A tester who joins on day 5 does not have to stay until their own day 14. What matters is that on every one of those 14 days you had at least 12 people opted in. Google does not publish every detail of how it counts, so watch the numbers in Play Console rather than assuming.
That also means a late joiner can rescue your count. If someone drops on day 6 and a new tester joins the same day, your total can stay at 12 or above.
Midnight is not the same for everyone
Your testers do not share your clock. A tester who opens your app at 11 pm in one country is opening it the next morning somewhere else. Any system that counts days, Google's or a testing app's, has to pick a time zone or allow a margin, and that is where a test right around midnight can land on a different day than the tester expects.
For testers, the fix is boring: test at the same time every day, well away from midnight. Morning or early evening works. For developers, it means not panicking when a tester's count looks off by one day. It usually is the boundary, not a lost day.
What to do as a developer
Count from the day you first have 12 opted-in testers, not from the day you share your opt-in link. Testers join at different speeds, and your 14 days only really start once you are at 12.
Recruit above 12. A buffer covers late joiners, early drop-outs and the odd day that lands on the wrong side of midnight.
Tell testers when the test started and how long it runs, in plain dates. "The test runs from the 3rd to the 16th" leaves less room for confusion than "14 days".
Check Play Console every day and log the opted-in count. If something looks wrong, you will see it on the day it happens, not on day 15.
