Engagement data tells you whether opted-in testers are actually using the app—and whether your closed test will survive review. Personal accounts after November 13, 2023 need ≥12 opted-in testers for 14 consecutive continuous days; org/D-U-N-S accounts are exempt. Opt-in without downloads and opens is not engagement.
Types of Engagement Data
Read multiple metric families together; one green number can hide a failing test.
Activity metrics
- Daily opens / active testers
- Session frequency and time in app (when available)
- Feature usage that proves more than a splash-screen tap
Retention metrics
- Active vs opted-in headcount
- Uninstalls and reinstalls
- How many testers still participate late in the window
Pattern metrics
- Day-to-day consistency
- Trend direction across the 14 days
- Anomalies after releases or weekends
Interpreting Activity
Activity answers: “Are people using it now?”
High activity
- Most of the ≥12 cohort opens regularly
- Suggests the app is reachable and somewhat compelling
- Keep monitoring vitals so crashes do not reverse the trend
Low activity
- Possible install/opt-in failures
- Possible crash-on-open or confusing first run
- Investigate same day—do not wait for day 14
Declining activity
- Engagement fatigue or unresolved bugs
- Reminder and replacement time
- Check whether a recent update caused the drop
Interpreting Retention
Retention answers: “Are people staying long enough to finish consecutive days?”
High retention
- Testers remain installed and return
- Strong signal for a complete 14-day window
- Supports a cleaner production application story
Low retention
- Uninstalls or silent abandonment
- Often paired with crashes or weak value
- Replace lost testers early and fix root causes
Google previously required 20 testers; interpret retention against the current official 12 for 14 continuous days—not outdated headcount folklore.
What Data Tells You
Translate charts into decisions.
Positive signals
- Steady daily opens near ≥12
- Low uninstalls
- Continuous coverage intact
- Crash rates stable or falling
Warning signals
- Widening gap between opted-in and active
- Softening mid-test trend
- Growing inactivity clusters
Critical signals
- Many opted-in testers with zero use
- Mass uninstalls
- Broken consecutive-day streaks
- Engagement too weak to justify applying for production
Using Data for Decisions
Act in proportion to risk to the 14-day continuous requirement.
If data is positive
- Continue daily checks in Release → Testing → Closed testing and vitals
- Avoid risky late redesigns
- Prepare production materials with a stable build
If data is concerning
- Remind inactive testers immediately
- Fix blockers and ship a careful closed-track update
- Add backup testers before gaps compound
If data is critical
- Pause vanity changes; restore basic usability
- Rebuild a clean consecutive window if continuity is broken
- Do not apply for production on hollow opt-ins
Closed Test Pro provides organic participation tracking that makes these engagement calls easier—pair it with Play Console so you interpret engagement correctly and finish a closed test Google can trust.