What Counts as an “Engaged” Closed Tester?
Google asks how testers engaged with your app. Our practical definition of an engaged tester, the signals you can measure, and how to describe them honestly.
Short answer
Google doesn’t publish a numeric definition. In practice, an engaged tester uses the app regularly during the 14 days, tries its main features, and gives feedback you act on. That’s what the production access questionnaire asks about, so measure those three things and report them honestly.
What Google actually asks
Google’s requirement for eligibility is only opt-in continuity: 12 testers for 14 days. The production access application then asks about your closed test, including how you recruited testers, how they used the app and what feedback you received. “Engaged” is your evidence for those questions, not a box Play Console ticks.
A practical definition
This is our working definition, not Google’s:
| Signal | Engaged tester | Disengaged tester |
|---|---|---|
| Sessions | On most days of the 14 | Once, or never |
| Feature coverage | Tried the 2-4 core flows | Saw the first screen |
| Feedback | At least a few concrete notes | Nothing |
| Stayed opted in | Whole test | Left or uninstalled |
How to measure it
- Play Console statistics for your testing track (installs over time).
- Android vitals and crash reporting: sessions with crashes and ANRs show real use. See Android vitals during testing.
- Analytics events for your core flows (anonymous counts are enough).
- Feedback log with dates. TestersZone check-ins are timed and dated, and can be exported.
How to describe it in your application
Weak: “Testers used the app and liked it.”
Strong: “17 testers opted in. Over 14 days they recorded 210 sessions, and 14 of them completed the booking flow at least 3 times. We received 38 feedback notes and shipped 2 updates fixing the top 5 issues.”
Only state numbers you can back up. See how to apply for production access.
Frequently asked questions
Is one bug report per tester enough?
It helps, but variety matters more: some testers reporting bugs, some reporting confusion, some saying what they liked. Together that shows real use.
Can I share analytics screenshots in my application?
The questionnaire is text-based. Summarise the numbers in your answers, and keep the underlying data in case you’re asked.
Sources and how we keep this accurate
Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start freeKeep reading
Does Google Check Whether Your Testers Actually Used the App?
Do Closed Testers Need to Open Your App Every Day?
Applying for Production Access After Closed Testing
Can Testers Opt In From a Computer Instead of Their Phone?
Can You Skip Google Play’s 12 Testers Requirement?
Can One Person Be a Closed Tester for Several Apps at Once?
Browse all answers, or see the quick answers, guides and comparisons.