What 1,500+ Google Play Closed Testing Campaigns Taught Us
Aggregated, anonymized behavioral data from real Closed Testing campaigns. Every guide tells you to get 12 testers. None of them tell you what testers actually do during those 14 days. This page does.
The average tester: what 14 days actually looks like
Every Closed Testing guide tells you to get 12 testers. But nobody publishes what happens next. We analyzed anonymized, aggregated data from 1,500+ campaigns on TesterBee to understand what real testers actually do — how often they open apps, how long they stay, when they drop off, and which device models they use.
The single most important finding: only 22% of testers open the app every single day. Google does not publish exact engagement thresholds, but our data shows that testers who open the app on at least 10 of the 14 days correlate with first-attempt production access approval. Testers who open it on 5-7 days typically do not.
This means your tester instructions matter enormously. Do not just say "please test my app." Give testers specific tasks on specific days. "Try the search feature on day 3. Create a new account on day 5. Use the sharing feature on day 8." Structured engagement produces the signals Google's review systems look for.
The drop-off curve: when testers leave and why
Tester drop-off follows a predictable pattern across all 1,500+ campaigns. Understanding this curve helps you schedule updates and re-engagement at the moments that matter most.
Days 1-3: The Honeymoon
92% retentionAlmost every tester opens the app in the first 72 hours. Curiosity drives exploration. This is when you get your highest session counts. Crashes on day 1 lose testers permanently — 14% of campaigns had at least one tester report a launch crash.
Days 4-7: The Cliff
68% retentionThe highest churn window. Novelty wears off. Friends and family are the worst offenders — they meant well but they forget. 26% of testers who installed on day 1 have stopped opening the app by day 7.
Days 8-10: The Plateau
68-71% retentionTesters who survived the cliff tend to stick. These are your reliable testers. They open the app every 2-3 days, explore new features when you push updates, and provide the most useful feedback.
Days 11-14: The Finish
65% retentionThe final stretch. Drop-off is minimal. Testers who are still engaged at day 11 are committed to completing the 14 days. 87% of testers active on day 11 remain active through day 14.
Device diversity: what testers actually use
Google checks whether your testers use a variety of real devices. Twelve testers all on Samsung Galaxy S24s running Android 14 is a red flag. Here is the actual device distribution across our tester pool.
| Device Brand | Share | Common Models |
|---|---|---|
| Samsung | 34% | Galaxy A and S series dominate |
| Xiaomi / Redmi / POCO | 22% | Budget to mid-range devices |
| Google Pixel | 8% | Pixel 6 through Pixel 8 |
| OnePlus | 7% | Nord and flagship models |
| OPPO / Realme | 6% | Budget to mid-range |
| Motorola | 5% | Moto G series |
| Other | 18% | Huawei, Vivo, and other brands |
Red flag for Google: All 12 testers on the same device brand or model. Aim for at least 4 distinct device brands and 3 distinct Android major versions across your tester pool.
What Google actually measures: the engagement signals that matter
Google does not publish its exact evaluation criteria, but our data from 1,500+ campaigns reveals clear correlation patterns between specific engagement metrics and first-attempt approval rates.
Session Frequency
Most importantTesters need multiple sessions across multiple days. Campaigns where the average tester opened the app on 10+ distinct days had a 97% first-attempt approval rate. Campaigns averaging 5-7 days had a 41% approval rate.
10+ distinct days with sessions
5 or fewer distinct days
Session Duration
HighShort sessions (under 30 seconds) suggest crashes or immediate exits. Google interprets this as low engagement. Sessions of 1-5 minutes with multiple screen transitions suggest genuine exploration.
1-5 minutes per session, multiple screens
Under 30 seconds, single screen
Feature Interaction Depth
HighGoogle tracks whether testers actually use your features — not just whether they open the app. A tester who launches and stares at the home screen generates no useful signal. They need to tap buttons, navigate screens, trigger functionality.
4+ distinct screens per session
Home screen only, no navigation
Developer Responsiveness
MediumGoogle monitors whether you push updates during the 14 days. An app that receives zero updates signals that the developer is not using testing for its intended purpose. Campaigns with 2+ updates during the 14 days had an 89% approval rate vs 53% for campaigns with zero updates.
2-3 updates during 14 days
Zero updates pushed
Device Diversity
MediumGoogle checks device model and brand variety. All 12 testers on the same device model suggests emulators or one person with multiple accounts. Aim for at least 4 distinct device brands and 3 distinct Android major versions.
4+ brands, 3+ Android versions
All same brand/model
What this means for your Closed Testing strategy
Recruit 14-15 testers, not 12
With a 35% expected drop-off by day 7, exactly 12 testers leaves no margin. Two extra testers cost nothing and save weeks of delay if someone drops out.
Space out feature instructions
Do not tell testers to explore everything on day 1. Give them a reason to return on days 3, 5, 8, and 11 with specific feature requests. This creates the multi-day engagement Google looks for.
Push updates at strategic moments
Day 3 (fix early bugs), day 6 (respond to feedback), day 9 (add polish). This creates a visible feedback loop. Zero updates during 14 days signals to Google that testing was not taken seriously.
Monitor daily, not weekly
Do not wait until day 14 to check your tester count. If someone drops off on day 5 and you do not notice until day 13, you have lost 8 days of potential replacement time.
Document everything for the questionnaire
Every update you push, every bug report you receive, every change you make — write it down. This documentation becomes your production access questionnaire answers and separates approved applications from rejected ones.
Get 12 real testers who stay engaged
TesterBee provides 12 verified testers on real Android devices across 4+ brands and 3+ Android versions. Daily engagement monitoring. Same-day replacement if anyone drops. 98.4% success rate. From $14.99.
Get 12 testers now