Quick answer
FTUE (first-time user experience) is everything a new user sees and does in their first session with a product or game. It is good when the user reaches the step where the product delivers its core value in that session, which you can only measure once that step is defined as an event.
Formula: FTUE completion = new users who reach the core-value event in their first session ÷ new users
What is FTUE?
FTUE stands for first-time user experience: everything a new user sees and does in their first session with a product, from the first screen to the moment they either get what they came for or leave. The term started in game development and is now used for apps and SaaS products as well.
Whatever the product, a first-time experience is good or bad for one reason: did the new user reach the step where the product delivers its core value, in that first session? In a puzzle game that is finishing the first real level; in a photo editor, exporting an edited photo; in an analytics tool, seeing your own data in a report. Screens, tooltips and welcome videos only matter to the extent that they get people to that step.
That makes FTUE measurable, but only after you do one thing: define the core-value step as an event. Without it, teams judge the first-time experience by how the screens look or by survey comments. With it, FTUE becomes a number you can track per release: the share of new users who reach the event in their first session.
In games, "the FTUE" often also names a concrete part of the build: the scripted opening levels or tutorial that teaches the controls, which designers tune separately from the rest of the game. In SaaS and app teams the word is broader and closer to "first session". Both meanings share the same test: does the first session end with the user having done the thing the product is for?
FTUE vs onboarding vs activation
The three terms overlap and are often used interchangeably. They differ in scope and in what you measure.
| FTUE | Onboarding | Activation | |
|---|---|---|---|
| What it is | The whole first session as the user experiences it | The guidance you design: welcome screens, setup steps, tours, checklists | The milestone a user reaches when they first get the core value |
| Time span | First session | First session up to the first few weeks | A single moment (event) |
| Owner | Product and design | Product, design, growth | Product and growth, defined with data |
| Measured by | Share of new users who reach the core-value event in the first session | Step completion of the onboarding flow | Activation rate: activated users ÷ new users in a period |
| Example | A new user signs up, imports data and sees a report in 12 minutes | A three-step setup wizard plus a checklist for week one | The event first_report_viewed |
The useful way to hold them together: activation is the destination, onboarding is the route you build, and FTUE is how the first trip along that route actually went. The moment a user feels that value is often called the aha moment; activation is the measurable event you choose to stand for it. How to design the onboarding itself is a separate topic, covered in app onboarding.
How to define the core-value event
Pick one event per product (or per main use case) and write down why. These rules keep the choice honest:
- It is something the user does, not something you show. "Viewed the welcome tour" is not value; "created the first invoice" is.
- It can happen in the first session. If the core value needs a week (a habit tracker's first streak), pick the first step that predicts it, such as the first logged entry.
- It predicts coming back. Users who reach it should return noticeably more often than those who do not. Check this with data, as in the example below; if there is no difference, you picked the wrong event.
- It is specific enough to instrument. One event name, with properties that let you filter (platform, plan, acquisition source).
- It is shared. Product, design, marketing and support use the same definition, written into the tracking plan.
Measuring FTUE: a worked example
Sample data: a task-management app has 2,000 new users in one month. The team defines the core-value event as "shared a project with a teammate" and builds a funnel in which every step must happen in the user's first session.
| Step (first session) | Users | Conversion from previous step |
|---|---|---|
| 1. Signed up | 2,000 | |
| 2. Created a project | 1,460 | 1,460 ÷ 2,000 = 73.0% |
| 3. Added at least three tasks | 1,020 | 1,020 ÷ 1,460 = 69.9% |
| 4. Shared the project (core value) | 610 | 610 ÷ 1,020 = 59.8% |
FTUE completion = new users who reached the core-value event in their first session ÷ new users = 610 ÷ 2,000 = 30.5%.
Now check rule 3, that the event predicts coming back. Of the 610 who shared a project, 336 returned in the next period: 336 ÷ 610 = 55.1%. Of the 1,390 who did not (2,000 − 610), 222 returned: 222 ÷ 1,390 = 16.0%. Overall, 558 of 2,000 returned (27.9%). Reaching the event goes together with a return rate more than three times higher (55.1 ÷ 16.0 ≈ 3.4), so it is a reasonable definition of value. This does not prove that sharing causes retention (people who share may simply have a team waiting), but it shows the event separates engaged users from the rest.
The funnel also tells the team where to work. The largest absolute loss is between steps 1 and 2: 540 people (2,000 − 1,460) signed up and never created a project. The weakest step-to-step rate is the last one, 59.8%. Improving step 2 from 73.0% to 80.0% would put 1,600 users into step 3; if the later rates held, about 1,600 × 69.9% × 59.8% ≈ 669 users would reach the core value, roughly 59 more per month. That is the kind of estimate a design change can be judged against, and it only exists because value was defined as an event.
FTUE in games and in SaaS
| Games | SaaS / productivity apps | |
|---|---|---|
| Typical core value | Finishing the first real level or match; the first reward | First real output: a report, an invoice, a shared document |
| Usual FTUE format | Scripted tutorial levels teaching controls one at a time | Setup steps, templates, sample data, contextual tips |
| Main risk | Too long or too slow before the fun starts | Empty product: nothing to see until the user imports data |
| Early signals to watch | Tutorial step completion, first-session length, day-1 return | Setup completion, time to first output, time to value |
Both columns follow the same pattern: name the moment of value, then remove everything between the first screen and that moment that is not strictly needed.
What a strong first-time experience does
Platform guidance and usability research agree on a few principles that can be checked against your own funnel:
- Let people start doing, not reading. Apple's Human Interface Guidelines recommend teaching through interactivity, letting people perform the task instead of viewing instructional material.
- Keep any up-front flow short and optional. Apple advises making a separate tutorial optional and not showing it again on later launches once skipped.
- Prefer contextual tips over a deck of slides. Nielsen Norman Group's research found that swipe-through tutorial cards did not improve task performance, and recommends testing the app without them first.
- Do not make people wait. Large downloads, long sign-up forms and permission prompts before the first useful screen all add steps to the funnel. Fewer fields in a signup flow usually means more people reach step 2.
Common mistakes
- No core-value event. Measuring "completed onboarding tour" tells you people clicked Next, not that they got value.
- Counting completion over weeks instead of the first session. A user who comes back on day 9 to finish setup had a poor first-time experience, even if they activated eventually.
- Averaging across very different users. Invited teammates and self-serve signups start from different places. Split the funnel by acquisition source or invite status.
- Reading screens instead of behaviour. Opinions about the welcome screen matter less than where the 540 people who never created a project stopped. Watch those sessions.
- Calling a correlation a cause. An event that predicts retention is a good target, but test changes before claiming they moved retention.
- Measuring once. FTUE changes with every release. Track it per release and per platform.
Measuring FTUE in TapCub
The worked example above can be rebuilt in TapCub with the same four steps and the same retention check.
- Build the first-session funnel. In All-platform analytics › Behavior › Behavior analysis, create a funnel with sign-up, project created, tasks added and project shared, and require the steps to share one session. The funnel shows how many people reached each step and where the 540 who never created a project dropped out. See build a funnel.
- Watch new users as a group. The lifecycle view in the same place counts New users per week or month (people seen for the first time in that period), so you can see whether FTUE changes coincide with a change in incoming users. Retention in the same section shows whether people come back in period 1. See read the lifecycle report.
- Compare reached vs not reached. Create a rule segment in All-platform analytics › Users › Segments & tags for people who did the core-value event, and use it as a group in retention to repeat the 55.1% vs 16.0% comparison on your own data.
- Watch the sessions where people stop. All-platform analytics › Behavior › Session replay is off by default; once you turn it on, you can watch first sessions that ended before step 2 instead of guessing why they ended. See session replay.
TapCub measures the first-time experience; it does not build product tours, checklists or in-app guides. Those stay in your product code, and the funnel tells you whether they help.
See also: What is a walkthrough? Meanings, how to run one and how to measure it.
Sources
- Apple Human Interface Guidelines, Onboarding.
- Nielsen Norman Group, Mobile-App Onboarding: An Analysis of Components and Techniques.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Product Adoption Consultant
Explores customer onboarding, live conversations, and self-service, turning common usage questions into practical guidance and improvements.