Mobile Game Soft-Launch Checklist: Preparation, Metrics, and Launch Decisions

Key takeaways

• A disciplined soft-launch advances through three sequential gates: technical and telemetry verification first, core-loop retention second, and Net LTV versus Cost Per Install (CPI) scalability third.
• If a soft-launch is accessible to players in Vietnam, the build must fulfill G1–G4 licensing rules, Vietnamese mobile phone verification, under-18 playtime limits, and virtual item restrictions under Decree 147/2024/ND-CP (effective December 25, 2024, amended by Decree 116/2026/ND-CP effective April 8, 2026) and Decree 174/2026/ND-CP (effective July 1, 2026).
• When evaluating payback viability, studios must compare CPI against Net LTV (calculated from revenue after deductions appropriate to the payment channel, business model, and revenue recognition principles) rather than Gross LTV.
• Four mistakes routinely corrupt soft-launch data: blending organic community fans with paid UA cohorts, changing multiple variables simultaneously, fragmenting iOS spend below SKAdNetwork privacy thresholds, and letting individual whales skew small-cohort ARPDAU.

What is a mobile game soft-launch designed to validate?

In mobile game publishing, following a structured mobile game soft-launch checklist turns early testing into a controlled field experiment rather than a miniature marketing campaign. Running on live servers, real payment rails, and unscripted player behavior, a soft-launch exposes bottlenecks in technical stability, onboarding pacing, and economy balance before a studio commits full-scale User Acquisition (UA) capital.

Cohort discipline is especially critical in maturing markets, as highlighted in our Vietnam mobile game market overview and Gamota's Vietnam Mobile Gaming Year-in-Review 2025 (published February 2026): total market revenue reached USD 825 million in 2025 (+9.16% YoY) across 54 million players, yet only 7%–10% of players are payers and only 12 of the Top 50 most-downloaded titles also ranked in the Top 50 by IAP revenue. To keep test data clean and actionable, an effective soft-launch moves sequentially through three validation gates:

1. Stage 1 — Technical & Telemetry Validation: Conducted during the opening days of live operation with a small install cohort. Engineering verifies crash-free session rates across common device tiers and matchmaking stability under mobile latency. Key client analytics events must be inspected and reconciled against server database logs to ensure accuracy.
2. Stage 2 — Retention & Core Loop Validation: Once crash rates and telemetry are clean, the product team measures Day-1 (D1), Day-7 (D7), and Day-30 (D30) retention cohorts. These curves pinpoint drop-offs during the first-time user experience (FTUE) and test whether core progression sustains daily play.
3. Stage 3 — Monetization & UA Validation: Triggered only after early retention stabilizes. Publishing and UA leads evaluate starter-pack payer conversion, build projected Net Lifetime Value (Net LTV) curves, and verify whether Net LTV can recover Cost Per Install (CPI) within the target payback window.

When should you skip a full multi-phase soft-launch?

Running a multi-week soft-launch is not always the right tool. You should hold off on a full soft-launch in two specific situations:

• When basic client stability or the first 30 minutes of gameplay have not passed internal QA: If crash rates remain high or the tutorial contains known progression blockers, buying paid traffic simply burns budget confirming bugs that internal playtesting should have caught.
• Early hyper-casual marketability smoke tests: If your team is only testing ad creative click-through rates and D1 mechanic appeal for a lightweight prototype, a 3-to-5-day CPI test on an open testing track is far leaner than operating a full live-ops economy.

How should you select soft-launch markets and cohort sizes?

Choosing where to open servers and how many installs to buy depends on your current validation gate. Official Google Play and Apple developer platforms provide two primary distribution mechanisms:

• Storefront beta tracks: On Android, Google Play Console offers Internal, Closed, and Open testing tracks. These let studios cap tester headcount and keep early beta feedback separate from public store ratings. On iOS, Apple's TestFlight supports up to 10,000 external testers invited via public links or email prior to commercial release.
• Territory-restricted commercial availability: When measuring true storefront conversion rates, live In-App Purchase (IAP) spending, and ad-network campaign optimization, publishers configure country availability in Google Play Console and App Store Connect to release the title in selected test territories.

Four criteria for choosing test territories and cohort volume

Product Managers and UA Leads should size their test markets and daily cohorts around four operational criteria:

• Behavioral and device-tier similarity: The test market must mirror your primary commercial market in genre affinity, Android versus iOS device mix (in Vietnam, 57% Android and 43% iOS in 2025 per Gamota / Statcounter), and 4G/5G network conditions.
• Manageable CPI for server liquidity: Multiplayer, matchmaking, or guild-driven games need enough concurrent players so queues do not stall. Picking a territory with moderate CPI lets the team sustain healthy server liquidity within a controlled testing budget.
• Statistically meaningful daily cohorts: Reading retention or payer conversion from daily cohorts of 30 to 50 installs invites false conclusions. A single high-spending player or a brief server outage can swing percentages sharply. Daily cohorts must be large enough that active players remaining at D7 and unique payers support reliable build-over-build comparisons.
• Android granularity versus iOS privacy thresholds (SKAdNetwork / AdAttributionKit): On Android, Google Play Install Referrer and Mobile Measurement Partner (MMP) SDKs deliver granular event funnels quickly even at modest volume. On iOS, Apple's SKAdNetwork and AdAttributionKit enforce crowd-anonymity privacy thresholds: when a campaign falls short of Apple's daily install volume bar, postback conversion values are withheld or coarsened. Studios therefore run Stage 1 and Stage 2 primarily on Android, then consolidate Stage 3 iOS spend into fewer high-volume campaigns as a reference operational practice.

Mobile game soft-launch checklist before opening servers

A misnamed funnel event or broken payment webhook can invalidate weeks of paid test traffic. Before opening servers to external players, the producer should sign off on five operational workstreams with each responsible lead:

Workstream	Pre-Open Checklist Items	Owner	Acceptance Criteria (Pass Gate)
1. Engineering & Infrastructure	Verify crash-free rates on low/mid-tier phones; run concurrency load tests; test resumable asset-bundle downloads on 4G; enable CPU/memory alerts	Client & Server Engineering, QA	Zero progression-blocking bugs; initial load time within target; server auto-scaling verified under peak load
2. Telemetry & Attribution	Integrate MMP SDK and product analytics; instrument step-by-step FTUE funnel events, level progression, virtual currency sinks/sources, and verified purchases	Client Engineering, Data Analyst, UA	Key events are inspected and reconciled against server data for accuracy; MMP excludes sandbox test orders
3. Payments & Economy	Configure IAP SKUs in App Store Connect and Google Play Console; localize price tiers; run end-to-end purchase, item delivery, and refund tests	Economy Designer, Engineering, Payments	Test purchases grant exact items within seconds; duplicate IPN webhook retries never trigger double grants
4. Legal & Store Compliance	Secure G1–G4 credentials if open in Vietnam; enable full name, birth date, Vietnamese phone verification, and under-16 guardian flow; display age badges, health warnings, and under-18 playtime caps; block item trading	Legal, Product, Publishing Operations	Full compliance with Vietnamese game regulations (Decree 147/2024/ND-CP, Decree 116/2026/ND-CP); builds approved by Apple and Google
5. Live Operations & Support	Launch in-game support ticketing, community channels, 24/7 server incident escalation (on-call), and player compensation templates for emergency maintenance	LiveOps, Customer Support	Support tickets route directly to helpdesk; on-call engineers meet a 15–30 minute response SLA for outages

Under Workstream 3, if your title also connects local payment channels through an authorized web billing portal, engineering should verify webhook signatures and idempotency locks against our payment gateway integration checklist for websites and apps.

Regulatory obligations when testing directly in Vietnam

Studios often assume labeling a build "Open Beta" or "Soft-launch" waives local licensing rules. In reality, Vietnamese law does not exempt limited or beta releases from statutory compliance once the service is opened to players in Vietnam.

Under Decree 147/2024/ND-CP (effective December 25, 2024, as amended regarding administrative procedures by Decree 116/2026/ND-CP effective April 8, 2026), any online game service provided to players in Vietnam must have a Vietnamese enterprise applying for the license and bearing responsibility for service provision, holding the required G1 license or G2–G4 registration certificate. Account registration must collect full name and birth date and verify players via a Vietnamese mobile phone number, while users under 16 require parent or legal guardian registration.

The client must display age rating badges (18+, 16+, 12+, 00+) and health warnings. Under Articles 39 and 48 of Decree 147/2024/ND-CP, technical systems must enforce under-18 playtime limits of no more than 60 minutes per game per day and total playtime of no more than 180 minutes per day across all games for players under 18 provided by the same enterprise (applying across both G1 and G2–G4 categories), while prohibiting virtual item trading or cash-out mechanisms.

Furthermore, under Decree 174/2026/ND-CP (signed May 15, 2026, effective July 1, 2026), failing to verify player accounts with a Vietnamese mobile phone number or permitting unauthorized virtual item trading carries administrative penalties. (Editorial note: Legal counsel must verify final compliance requirements directly against the official Gazette text before opening Vietnam servers.) For a step-by-step breakdown of G1–G4 licensing, see our guide on publishing a mobile game in Vietnam from contract signing to launch.

Which soft-launch metrics should you track and how should you read them?

Rather than chasing generic "industry benchmark" percentages from blog posts that omit genre and traffic mix, teams should standardize exact cohort formulas. The table below defines six core indicators alongside common analytical traps:

Metric	Standard Definition & Calculation	Business Question Answered	Common Analytical Pitfall
D1 / D7 / D30 Retention	Percentage of users who installed and first opened the game on day D0 who return to open it on exactly day 1, day 7, and day 30 post-install	Do the onboarding flow, core loop, and progression depth keep players returning through month one?	Confusing Rolling Retention (returned on day N or any later day) with strict Classic N-day Retention, inflating retention figures
Session Length & Sessions/DAU	Average duration per play session and average daily sessions per Daily Active User (DAU)	Do energy timers, daily quests, and match lengths fit daily mobile usage habits?	Relying only on the arithmetic mean (skewed upward by AFK emulator sessions) instead of inspecting median session length
Payer Conversion Rate	Percentage of users in an install cohort who complete at least one verified real-money purchase	Do starter bundles and early purchase touchpoints persuade players to make their first payment?	Judging conversion after 48 hours on strategy or RPG titles whose deeper monetization systems unlock around D5–D7
ARPDAU	Average Revenue Per Daily Active User (Total daily revenue divided by that day's DAU)	How effectively does the active player base monetize each day, and how do LiveOps events lift spend?	Extrapolating early soft-launch ARPDAU—when nearly 100% of DAU consists of fresh D0–D3 installs—linearly into long-term forecasts
CPI (Cost Per Install)	Average paid advertising spend required to generate one completed app install	How strongly do the game's theme, art style, and ad creatives resonate on paid networks?	Running micro-budgets that only capture the cheapest, highest-intent users and assuming CPI stays flat at 10x spend
Projected Net LTV	Calculated from cumulative revenue per user from day D0 through day N after deductions appropriate to the payment channel, business model, and revenue recognition principles	How much net revenue does each install generate to pay back upfront CPI?	Comparing Gross LTV (before payment channel deductions) directly against CPI, or fitting LTV curves from 3 days of data without a D14/D30 anchor

When should you launch commercially, iterate, or sunset the project?

The purpose of a soft-launch is enabling leadership to make an objective capital-allocation decision. To prevent sunk-cost bias from dragging testing out indefinitely, the studio and publisher must lock a three-way decision matrix before opening the server:

1. Greenlight Commercial Launch (Go / Scale): Client stability holds firm, D1/D7/D30 retention meets or beats genre targets, and cohort modeling proves Net LTV recovers CPI within the target payback window. Leadership then locks the commercial launch date and scales UA budgets.
2. Targeted Iteration (Iterate / Pivot): Top-of-funnel metrics pass, but a downstream metric misses target with a clear root cause. For example, CPI is low and D1 is healthy, yet D7 drops at Stage 15 due to an uncalibrated boss wall; or D7 holds steady while starter-pack conversion lags. The team isolates one hypothesis, ships a focused patch, and buys a fresh cohort to verify the fix.
3. Sunset or Major Rework (Kill / Re-architect): Both CPI remains prohibitively high and D1 retention stays far below target after two to three iterations on onboarding and early gameplay. That pattern signals a fundamental market-fit gap; stopping early preserves marketing capital for higher-potential titles.

Illustrative cohort evaluation across two test waves (hypothetical figures)

The table below shows how a publishing committee compares cohort metrics across two builds. This is an illustrative example using hypothetical figures for a tactical RPG targeting a Day-30 UA payback window with an assumed 30% payment channel deduction:

Tracked Metric (2,000 Paid Installs per Cohort)	Pre-Agreed Target	Wave 1: Build A (Hypothetical)	Wave 2: Build B (Hypothetical)	Committee Diagnosis & Decision
Crash-Free Session Rate	≥ 99.0%	99.2%	99.4%	Technical stability gate passed in both builds
Classic D1 / D7 / D30 Retention	38% / 14% / 6%	39% / 9% / 3.5%	40% / 15% / 6.5%	Build A hit a D7 wall at Stage 15; Build B smoothed progression pacing
Cumulative D30 Payer Conversion	≥ 3.5%	2.4%	4.1%	Build B repriced starter bundles, lifting first-purchase conversion
Average Paid CPI	≤ 25,000 VND	24,000 VND	24,500 VND	Acquisition cost held steady below target ceiling
Gross LTV30 (Pre-Deduction)	≥ 36,000 VND	27,000 VND	38,000 VND	In Build A, comparing Gross LTV30 (27,000 VND) to CPI falsely implies UA payback
Net LTV30 (After Assumed 30% Deduction)	≥ 25,000 VND	18,900 VND	26,600 VND	Build A: Net LTV30 falls short of CPI by 5,100 VND/install → Iterate. Build B: Build B's Net LTV30 exceeds CPI by 2,100 VND/install, meeting the assumed UA payback target → Go / Scale

Four common mistakes that corrupt soft-launch data

Across soft-launch reviews conducted with partner studios, Appota's game publishing and UA teams consistently encounter four operational errors that distort cohort decisions:

• Mixing organic community fans with paid UA cohorts: Studios frequently post test-server download links on existing fanpages or Discord channels. Pre-existing fans retain and spend at much higher rates than cold ad installs. Failing to segment paid UA cohorts away from organic traffic severely overstates commercial LTV projections.
• Changing multiple product and ad variables in the same week: Overhauling the tutorial, cutting starter-pack prices by 30%, and switching ad networks in a single release makes it impossible to tell which change moved D7 retention or ARPDAU.
• Letting individual high spenders skew small-cohort ARPDAU (Whale bias): In a 1,000-install cohort, one or two heavy spenders can triple cumulative revenue overnight. Publishers always evaluate Payer Conversion Rate, median spend per payer, and capped ARPDAU (winsorizing extreme outliers) alongside raw ARPDAU.
• Scaling UA budgets while technical or D1 leaks remain open: Buying tens of thousands of installs before fixing asset-download drop-offs or D1 tutorial churn depletes testing budgets before engineering can deploy a patch.

(Editorial note: These internal operational takeaways will receive final confirmation from Appota's Gaming specialist prior to publication approval.)

You can download the Vietnam Mobile Gaming Year-in-Review 2025 report by Gamota for 2025 Vietnam market benchmarks, or explore more publishing analyses on the Gaming topic hub on Appota Insights. If your studio is preparing a mobile title for soft-launch or needs an independent publishing review of your D1/D7/D30 cohort curves, monetization tiers, and Vietnam compliance readiness, compile your install-cohort data and connect with Appota's game publishing team to review your pre-launch checklist and commercial rollout plan.

Sources

1. Google Play Console Help — Set up an open, closed, or internal test, Google, accessed 2026-10-31
2. Apple Developer — TestFlight Overview, Apple, accessed 2026-10-31
3. Apple Developer — Receiving Ad Attributions and Postbacks (SKAdNetwork Crowd Anonymity), Apple, accessed 2026-10-31
4. Google Play Console Help — Changes to Google Play's service fee, Google, accessed 2026-10-31
5. Apple Developer — App Store Small Business Program, Apple, accessed 2026-10-31
6. Nghị định 147/2024/NĐ-CP về quản lý, cung cấp, sử dụng dịch vụ Internet và thông tin trên mạng, Chính phủ Việt Nam (dẫn qua Cổng TTĐT Bộ Khoa học và Công nghệ), 2024-11-09, accessed 2026-10-31
7. Nghị định 116/2026/NĐ-CP sửa đổi, bổ sung một số điều của các Nghị định có quy định thủ tục hành chính liên quan đến hoạt động sản xuất, kinh doanh thuộc phạm vi quản lý của Bộ Văn hóa, Thể thao và Du lịch, Chính phủ Việt Nam, 2026-04-02, accessed 2026-11-04
8. Quy định xử phạt vi phạm hành chính về xác thực tài khoản game bằng số điện thoại theo Nghị định 174/2026/NĐ-CP, LuatVietnam (dẫn Nghị định 174/2026/NĐ-CP của Chính phủ), 2026-05-15, accessed 2026-10-31
9. Báo cáo Ngành Game Mobile Việt Nam 2025 (Vietnam Mobile Gaming Year-in-Review 2025), Gamota (Appota Group), 2026-02-04, accessed 2026-11-04