What is FTUE and why does it matter on PC?

FTUE means first time user experience: everything from the first launch to the moment the player understands the game and wants more. On PC it often covers the main menu, settings, a tutorial and the first level or run.

It matters because most players never come back. In the GameAnalytics Benchmarks Hub for October 2026, the median PC game kept 6.54% of new players on day 1. The first session is the only session most players have. On Steam it also decides refunds: a player can ask for a refund within 14 days of purchase if they played less than two hours.

Sources: GameAnalytics Benchmarks Hub; Steam Refunds policy.

Which steps should a first session funnel have?

Pick three to five steps that every new player must pass, from the first launch to the first real success. A funnel in Manalens has two to five steps, so choose the steps that carry the most risk. Name them in snake_case and keep the names fixed across builds.

Start the funnel at the launch of the game, not after the first load. Dylan Jones gives this advice in Game Developer, so that you can see whether the first load makes players leave. He also suggests that you track the mandatory actions of the first five minutes or more.

First session funnel steps and what a drop at each step means.
StepEventWhat a drop here usually means
1. First launchgame_open (is_first_open true), sent by the SDKThe baseline. Every new player starts here.
2. Started playlevel_start with level 1, or a new_game eventThe menu, the settings or a long load lost them.
3. Tutorial donetutorial_complete (your own event)The tutorial is too long, too slow or unclear.
4. First goallevel_complete with level 1A difficulty spike or a confusing objective.
5. Second sessionsession_start in a later sessionThe game did not give a reason to return.

Sources: Manalens funnels and app events documentation; Game Developer, Indie Game Analytics 101, part 2 (Dylan Jones).

What does a first session funnel look like with numbers?

The table below is an example with invented numbers. It is not a benchmark and not data from a real game. It uses the five steps above for 1,000 new players, with a 7 day window so that the second session can count. The columns are the ones that the funnel table in Manalens shows.

Read it one row at a time. Step 2 loses 140 players before any play: look at the menu and the load time. Step 3 loses 240, the largest loss inside the first session. Only 620 of the 860 players who started level 1 finish the tutorial, which is 72%, and the median time for this step is 14 minutes. Step 4 loses 80: of the 620 players who finish the tutorial, 540 complete level 1, which is 87%. The first level is not the problem.

Step 5 is different. It asks whether the player comes back, and 190 of 540 do, which is 35%. This is a retention question, not a first session question. So in this example, the first fix is the tutorial, and the second is the reason to return.

Example first session funnel for 1,000 new players. All numbers are invented.
StepConvertedDropped offConv. rate (of entered)Median time from the step before
1. game_open (first launch)1,0000100%Start
2. level_start, level 186014086%1 minute 40 seconds
3. tutorial_complete62024062%14 minutes
4. level_complete, level 15408054%6 minutes
5. session_start (second session)19035019%1 day

Sources: Manalens funnels documentation.

Which events do I need for this funnel?

Three events from the SDK and three to five of your own. The Godot and Unity SDKs send game_open, session_start and session_end for you. The level events follow the Manalens app event conventions. The tutorial events are your own custom events: the conventions do not define them, so pick the names once and keep them.

Other tools use other names for the same steps. Google Analytics recommends tutorial_begin, tutorial_complete, level_start and level_end for games. GameAnalytics uses progression events with a status of start, complete or fail. If you move from one of them, map the names once in a tracking plan.

The event list for the example funnel. Properties follow the app event conventions where a convention exists.
EventPropertiesWho sends itIn the conventions
game_openis_first_open, first_open_atThe Godot and Unity SDKs, on each launchYes
session_startnoneThe SDKs, at launch or after 30 minutes idleYes
session_endduration_sThe SDKs, at quit or after 30 minutes idleYes
level_startlevel, attemptYour codeYes
level_completelevel, attempt, scoreYour codeYes
level_faillevel, attempt, scoreYour codeYes
tutorial_stepstepYour codeNo, your own event
tutorial_completeduration_sYour codeNo, your own event

Sources: Manalens app events documentation; Google Analytics Help, Recommended events; GameAnalytics Progression Events documentation.

How do I send FTUE events from my game?

Call track() at each step. You only add the steps that are unique to your game. Property values must be strings, numbers, booleans or null.

Add a step number to tutorial events if the tutorial has many screens. Then you can build a second, finer funnel inside the tutorial without new events.

GDScript (Godot)

Manalens.track("level_start", {"level": 1, "attempt": 1})
Manalens.track("tutorial_step", {"step": 3})
Manalens.track("tutorial_complete", {"duration_s": 412})
Manalens.track("level_complete", {"level": 1, "attempt": 1, "score": 1200})

Sources: Manalens Godot SDK and app events documentation.

How do I build the funnel in Manalens?

Add a Funnel chart to a dashboard, with your steps in order and a window that fits one first session. The default conversion window is 24 hours, and you can choose from 1 hour to 90 days. The table after the steps lists what a funnel does today and what it does not do.

  1. Open Dashboards, open or create a board, and click Add chart.
  2. Choose the Funnel metric.
  3. Add the steps: game_open, level_start, tutorial_complete, level_complete. Add a step filter for level 1 where needed.
  4. Keep Sequential order, so each step must come after the one before it.
  5. Set the conversion window to 24 hours for the first session, or 7 days to include players who finish the tutorial on a later day.
  6. Filter by build with the App filter group, so old builds do not hide a new problem.
  7. Save the chart and read the Dropped off and Median time columns.
First session funnels in Manalens, checked against the product documentation on 19 November 2026.
What you wantSupportedDetail
A funnel of two to five stepsYesEvents or pages as steps.
More than five steps in one funnelNoBuild a second funnel inside the weak step.
A conversion windowYes1 hour, 24 hours, 7, 14, 30 or 90 days.
Steps in order, or in any orderYesSequential is the default.
Drop-off and median time per stepYesIn the funnel table.
Filter by build, storefront or platformYesThe App group in the filter menu.
Breakdown by channel, device, country or an event propertyYesFirst touch or last touch.
Events that go with conversionYesConversion insights, when at least 10 people did the event.
What players did before they quitYesA User paths chart that ends at session_end.
Tutorial steps without codeNoAdd a track() call at each step.
Session replayNoNot in the product.

Sources: Manalens funnels, user paths and dashboards documentation.

How do I find the step that loses the most players?

Find the largest drop between two steps, then look at time and context. The funnel table shows, for each step, the people who converted, the people who dropped off, the conversion rate and the median time from the previous step. A step with a big drop and a long median time is often a step that players do not understand.

Then look closer with three tools. The Levels table in the Game KPIs board shows the fail rate per level, which finds difficulty spikes. A User paths chart with session_end as the end step shows the events that come before players quit. Conversion insights, under the funnel, lists events and property values that go with completing the funnel, such as a graphics setting or a platform, when at least 10 people did them. That is correlation, not cause, but it tells you where to test.

Sources: Manalens funnels, user paths and metrics documentation.

How long is a typical first session on PC?

Longer than on mobile. In the GameAnalytics Benchmarks Hub for October 2026, the median PC game had a session length of 20.82 minutes, and the top quarter had 33.83 minutes or more. The median mobile game had 3.14 minutes. So a PC tutorial that takes 15 minutes is not long by itself; a tutorial that takes 15 minutes before the first real choice may be.

Measure your own first session with the session_end event, which carries duration_s. Filter to new players with a segment, or compare the median time between funnel steps. If the time to tutorial_complete grows from one build to the next, the tutorial grew, even if nobody planned it.

Sources: GameAnalytics Benchmarks Hub; Manalens metrics and funnels documentation.

How does the first session connect to D1 retention?

Players who finish the first goal should return more often than players who do not. Check it with two retention charts. Use game_open as the entry event in the first chart, and tutorial_complete or the first level_complete in the second. If the second cohort has a much higher D1, then getting more players through the first session is likely to lift retention.

If both charts look the same, the first session is not your main problem. Look at the content after it, at stability, or at the players your marketing brings.

Sources: Manalens retention documentation.

What should I change when a step leaks?

Make one change per build and compare the build cohorts. Common fixes depend on the step.

Do not assume that more tutorial is the fix. A CHI 2012 study tested tutorials in three games with over 45,000 players. In Foldit, the most complex game, players with context-sensitive tutorials played 75% more levels and 29% longer than players with no tutorial. In the two simpler games, tutorials did not significantly improve engagement. A help button on demand even lowered play in one of them: players completed 12% fewer levels and played 15% less time. Test your own tutorial; do not copy a rule.

After each change, compare the funnel and D1 for the old and new build. Keep the event names the same, or the comparison breaks.

  • Menu to first play: start the game with one click, move settings later, shorten load times.
  • Tutorial: cut text, let players skip, teach by doing, and test the slowest screen first.
  • First level: lower the first difficulty spike, add a checkpoint, make the goal visible.
  • Crashes: check crash-free sessions for the new build in the Game health board before you change design.

Sources: Andersen and others, The Impact of Tutorials on Games of Varying Complexity (CHI 2012); Manalens funnels and error tracking documentation.

How do I see my first session funnel?

Manalens is the analytics and growth engine built for games. Add the SDK, send three or four first session events, and build the funnel, the Levels table and D1 retention for each build in one project.

Sources: Manalens product documentation.

Frequently asked questions

What does FTUE stand for?

First time user experience. In games it means the first launch, menus, tutorial and first level or run: everything a new player sees before they decide whether the game is for them. A first session funnel measures it step by step, so you can see where new players stop.

How many steps should a first session funnel have?

Three to five. Manalens funnels take two to five steps. More steps make each drop smaller and harder to read. Start with first launch, first play, tutorial done and first goal, then build a finer funnel inside the step that loses the most players.

Why does Steam make the first two hours so important?

Steam refunds a game bought in the last 14 days with less than two hours of playtime. A player who hits a crash, a wall or a confusing tutorial in that time can ask for the money back. A clean first session protects both retention and revenue.

Is there a benchmark for tutorial completion?

Not a public one for PC games that we could verify. The funnel table in this guide uses invented numbers to show the method. Compare your own builds with each other: the same steps, the same window, and a few hundred new players in each build before you trust a small gap.

Can I track a tutorial without changing the code?

Partly. The SDK sends game_open, session_start and session_end automatically, so you see launches and session length without new code. To see tutorial steps, levels or goals, you must add track() calls at those points. One line per step is enough in Godot or Unity.

Sources and implementation