Reading Closed Testing Engagement Metrics in Play Console

Where is the 14-Day Progress Bar?

Google Play Console provides a dashboard card showing how many testers are opted-in and how many days are left in your 14-day requirement. However, this high-level widget doesn't tell you if the testers are actually using the app.

To ensure you don't fail the engagement check, you must manually read your analytics.

Metric 1: Active Devices

Navigate to Statistics > Users > Active Devices. This chart shows how many physical devices currently have your application installed.

• What to look for: This line should remain flat or grow above 12. If the line drops sharply, it means testers are uninstalling your app, putting your streak at risk.

Metric 2: Daily Active Users (DAU)

Navigate to Engagement > Active Users. This is the most critical chart for passing the review. It shows how many unique testers opened the app on any given day.

• What to look for: You want a healthy, fluctuating line showing 6 to 10 testers engaging daily. A flatline at 0 means your app is installed but ignored—a primary cause for rejection.

Metric 3: Android Vitals (Crashes and ANRs)

Navigate to Quality > Android Vitals > Crashes and ANRs.

While you obviously want a stable app, seeing 1 or 2 minor crash logs here during closed testing is actually a positive signal to Google's algorithm. It proves that real devices are interacting with your app and generating authentic system logs.

The 48-Hour Delay

Always remember that the Play Console is an aggregate reporting tool. The data you see today reflects tester activity from 24 to 48 hours ago. Do not panic if Day 1 statistics look empty; check back on Day 3 to verify the initial install surge.