Where new players actually quit in the first session

Most studios know their D1 retention number. Far fewer know the specific moment in the first session that produced it. A D1 number is a result. It doesn't tell you which step in the new-player experience pushed players over the edge from "trying this" to "closing this."

Without that information, every D1 improvement effort is a guess. You change the tutorial because the tutorial is the obvious suspect. The number moves a little, or doesn't, and you can't tell whether the tutorial was actually the problem or whether your change happened to coincide with a shift in traffic mix. The right level of resolution to fix first-session drop-off is per-step, not per-day.

The session funnel most studios don't build

The metric studios usually track is "started the game and reached a defined point." That definition is usually too coarse — something like "completed the tutorial" or "reached level 3." Players who quit before that point all collapse into one bucket called "didn't finish."

A useful first-session funnel has many more steps than that. Game launched. First screen shown. Permissions prompt accepted or declined. First gameplay action attempted. First gameplay action completed. First win or first loss. First time the game introduced its core mechanic. First time the player did the core mechanic on their own. First social or progression event. First mention of monetisation.

Each of these steps is a place where a player can quit, and the rate at which players quit at each step has a meaningful interpretation. A high drop at the permissions prompt means your permissions ask is happening before the player has a reason to grant it. A high drop at the first gameplay action attempt means the controls or the goal aren't clear. A high drop at first loss means the loss state isn't recoverable in a way that encourages a retry.

The four common quit points

In most mobile games, first-session drop-off concentrates at one of four places.

Before gameplay starts. Players who launch the game and quit before the first interactive moment are responding to load times, permission prompts, account creation requests, or a long unskippable opening sequence. The fix here is friction reduction, not gameplay improvement. Whatever you're asking the player to do before they get to play is being asked too early.

During the tutorial. Players who start gameplay but quit during the guided tutorial are usually responding to one of three things: the tutorial is too long, the tutorial doesn't let them do the thing the game advertised, or the tutorial gates the interesting parts of the game behind too many forced steps. Players want to play the game they downloaded, not be told about it.

At the first real challenge. Players who clear the tutorial and quit at the first non-trivial gameplay moment are bouncing off difficulty or unclear goals. The first real challenge after the tutorial is supposed to feel like a graduation. If it feels like an unexpected wall, players read that as the game not being for them.

At the first content or progression gate. Players who play normally for a while and then quit at the moment the game asks them to wait, watch an ad, or make a decision about progression are responding to a break in flow. The session was going well, then the game introduced a constraint, and the player chose to leave rather than engage with it.

Where your game's drop concentrates determines what you fix. Treating "first session drop-off" as one problem and applying a generic onboarding rework misses the specificity required to move the number.

How to find your actual quit points

The data needed to identify the real quit point isn't exotic. It requires event logging that's granular enough to separate the steps above, and a way to compute the percentage of new players who reach each step.

Three checks worth running on your existing event data:

Look at the ratio of "session_start" events to first gameplay events. The gap between these two — players who launched but never played — is your before-gameplay drop. If this is more than 5–10% of starts, your pre-game flow is asking too much.

Look at the distribution of session length for D0 players who didn't return. Most studios have this data and don't slice it. A bimodal distribution — a cluster around 30 seconds and another around 5 minutes — tells you that two different things are causing drop, and they need different fixes. A long tail past 10 minutes with a hard quit at the end suggests players who engaged genuinely and hit a specific wall.

Look at the last event recorded for D0 churners. What were they doing in the seconds before they closed the game? The mode of this distribution — the single most common last action — is the moment your game lost them. Once you know what that moment is, you can decide whether to remove it, ease it, or move it.

The fix is rarely "make it easier"

The instinct when first-session drop-off is high is to make the early game easier — shorter tutorial, more hand-holding, lower difficulty, more free rewards. Sometimes that's right. Often it isn't.

Easier doesn't mean more engaging. A tutorial that's shortened by removing meaningful interactions feels emptier, not better. A first level that's softened to remove all challenge feels less like a game and more like a demo. Players don't quit because games are hard — they quit because games are hard in a way that feels unfair, unclear, or unrewarding.

The more useful framing is: what was the player trying to do at the moment they quit, and what stopped them? If they were trying to understand the core loop and the tutorial wasn't letting them, the fix is to let them try things in the tutorial, not to remove the tutorial. If they were trying to retry a failed attempt and the game made them wait, the fix is to remove the wait, not to make the attempt easier.

What to measure after a change

When you redesign a section of the first session, the right metric isn't D1 retention — it's drop-off at the specific step you changed.

D1 takes a day to measure and bundles together everyone who quit, including players who quit for reasons completely unrelated to your change. Step-level drop-off updates faster and tells you specifically whether the change moved the needle at the point you intended.

If step-level drop-off improved and D1 didn't, you may have shifted the quit point elsewhere — players are getting past your fixed step but failing at the next one. That's still useful information, and it tells you where to look next.

See how we track per-step engagement and identify drop-off →

D1 retention is the headline number. The first-session funnel is the explanation. Studios that can read the funnel as easily as they read the headline spend their onboarding budget on the specific moments where it matters, rather than on broad tutorial rewrites that may not address the actual cause.

Talk to us about diagnosing your first-session experience →