Growth & updates
Roblox first-session diagnosis: from loss shape to repair
Repair the exit mechanism rather than the nearest red number. The curve shows when players leave, the funnel shows at which decision, observation shows what they encounter, and D1 shows whether they later return.
Focused deep dive
Four evidence types
Run an unguided playtest on a target device and record pauses, mistaken expectations, and errors. First-session retention locates early exit timing. Funnel completion locates the transition. Errors and performance explain technical mechanisms. No source replaces the others.
D1 and D7 need mature cohorts. Compare matching weekdays, sources, and supported segments; a blended average can move because mix changed. Before a causal experiment, before/after remains observational.
| Loss | Possible cause | Check |
|---|---|---|
| Immediately after join | Loading, spawn, controls | Device test, errors, JoinReady |
| Before first action | Unclear goal or UI | Playtest and ActionStart |
| Action before reward | Difficulty, bug, delay | ActionComplete and server logs |
| After reward | No next goal | RewardUsed, repeat loop, feedback |
One repair cycle
Suppose mobile players receive a pickaxe but do not swing. Observation finds a starter offer covering controls, while the ad promises a cave that spawn does not reveal. The team removes the obstruction and moves spawn. Both respond to observed blockers but remain separate log entries.
First verify completion and errors, then wait for the matching D1 cohort. If Paid remains weak after the first loop, the next question concerns the ad promise rather than a generic reward.
- Define the job of the first session.
- Observe without coaching.
- Align curve, funnel, and errors.
- Repair one demonstrated mechanism.
- Validate the early step, then mature return.
- Record alternative explanations.
Primary sources
Put this into practice in MARPLA
Separate organic Home from other sources, inspect countries and supported joint breakdowns, then relate audience changes to Home set history and record a hypothesis in a note.
- Compare your game with benchmarksBenchmark scales show how your game performs alongside other projects.Step-by-step guide →
- Investigate Home and new audiencesCheck source, countries and cohort maturity to separate audience-mix changes from a worse game experience.Step-by-step guide →
- Compare audience composition and qualityCompare a complete period with its predecessor and separate audience mix change from within-segment metric change.Step-by-step guide →

Discussion0
Loading comments…