Onboarding Runway

The Onboarding Runway covers everything that happens before a user enters the engagement loop: the first impression a prospect forms, the decision to install, the creation of an account, and the data foundation that everything downstream depends on. Get the runway wrong and there is no loop to optimise.

First Contact

The impression made before the app is even opened

Engagement starts before the install

It is tempting to draw the Blueprint’s boundary at the moment a user opens the app for the first time. Most of the data and analytics we work with sit inside the app itself, and the rest of this guide leans heavily on in-app behaviour. But the engagement loop is set in motion well before that, in the seconds a prospect spends with an ad, a partner endorsement, a friend’s recommendation, or a post on social media.

This is First Contact: the very first time a prospect encounters your product, and the impression they take away from it. Get it wrong, and there is no install, no registration, no loop to optimise.

A lesson from a different industry

Before working on digital engagement, I spent time as a data analyst inside the customer service department of a Fortune 500 company. The primary metric we optimised European service operations against was First Contact Resolution (FCR): the share of customer issues fully resolved on the first interaction, with no callbacks, transfers, or follow-up tickets.

FCR mattered far more to us than ticket volume or average handling time, and the reason was consistent across every region: FCR was the strongest predictor of overall customer satisfaction. A customer whose problem was solved on the first call rated the entire experience higher than a customer whose problem was eventually solved across three calls, even when the final outcome was identical.

The mechanism is human, not procedural. First contact is when the customer decides whether they feel heard. Everything afterwards is shaped by that initial read.

The same principle applies to digital First Contact

A prospect encountering an ad, a social post, or a partner email is doing the same thing the call-centre customer was doing: forming an opinion about whether this product seems to understand them.

If the first contact answers a real question the prospect already has, they download. If it feels generic, mistargeted, or salesy in a way that doesn’t fit their context, they scroll past, and a download you might have had is gone.

This is why First Contact belongs in the Blueprint even though it sits outside the app’s analytics surface. The mindset that matters in-app (put the user at the centre, design for the human behind the screen, use data to keep getting closer to what they actually want) starts here.

What drives First Contact conversion

From the LiveWell data set and partner campaigns, six factors consistently moved the needle on prospect conversion:

• Partner endorsement: brands the prospect already trusts (e.g. Polar, Endu, Philips) carrying the message
• Brand trust at the sponsor level: confidence in the parent brand (in our case, Zurich) lowering the perceived risk of trying something new
• Social proof: knowing colleagues or peers are using the product already
• Herd behaviour: in-app events and campaigns that create visible momentum (LiveWell calls these Boosts)
• Continuous reminders: a single enrolment email being opened does not mean it landed at the right moment. Repeated, well-spaced touches matter
• Targeted campaigns: broad campaigns that try to speak to everyone tend to speak to no one. Localised, intent-aware messaging consistently outperforms

The two principles that hold up

Two simple rules, both straight from what we’ve measured:

1. The user should already have intent before they encounter your download prompt. Building intent at the download screen is too late.
2. Comms should be aligned with the needs and environment of the prospect. A campaign written for a generic user will underperform a campaign written for a specific one, even when the specific one is a smaller audience.

Bottom line

First Contact is the digital equivalent of First Contact Resolution. It is the moment the prospect decides whether you seem to understand them as a person, not as a segment. The download, the registration, the activation, and everything that follows is built on top of that one impression.

Spend as much care on the message a prospect sees before they reach your app as you do on the first screen they see inside it.

Prospect Conversion

From impression to install

The narrowest part of the runway

Between First Contact and Registration sits the conversion decision itself: the prospect taps the ad, lands on the store page or landing page, and either installs or leaves. This step has the least surface area of the whole runway, often a single screen, yet it filters out the majority of prospects who showed initial interest.

Intent is built upstream, not here

The most important finding about this step is what doesn’t work. An A/B test that added a pre-registration carousel of app features did not improve conversion: both groups landed around the same 17 to 18% install-to-enrolled rate. If the prospect is at your download prompt, they have already decided whether the product is for them. Anything you add at this point is friction, not motivation.

That makes prospect conversion a measurement point more than an intervention point. The levers that move it live in First Contact: partner endorsement, social proof, targeting, and timing. When install rates dip, the fix is almost always upstream in the campaign, not on the store page.

What to do at this stage

• Keep the path short. Every extra screen between the tap and the install costs prospects.
• Match the message. The store page or landing page should pay off the specific promise the campaign made. A mismatch between ad and page reads as bait-and-switch and kills trust at the worst moment.
• Measure by source. Track install rate per channel and campaign, not just in aggregate. Targeted, affiliated channels convert at a different rate from broad paid acquisition, and blending them hides the signal.
• Hand off cleanly to registration. The prospect’s intent is at its peak right after install. The next thing they should see is the fastest possible route to an account, which is exactly what the Registration section covers.

Registration

The mandatory door to becoming a trackable user

Why registration matters

Without registration, a user is invisible across time. You may have analytics on what happened in a single anonymous session, but you cannot connect their behaviour across multiple sessions, devices, or installs. The moment a user reinstalls the app or switches phones, an anonymous session resets from zero and any behavioural history is gone.

Registration creates the persistent user identity that the rest of the engagement framework depends on. Without it:

• You can’t measure retention properly, only sessions
• You can’t run cohort analysis, because cohorts need stable identifiers
• You can’t personalise
• You can’t reach the user outside the app, because you have no channel to them

As the Data is Engagement Fuel section explains, engagement generates behavioural data and that data powers the next loop. Registration is the infrastructure that makes that fuel storable and useful beyond a single session.

Registration is not onboarding

These two are often spoken about interchangeably, and they shouldn’t be:

• Registration is the mandatory step that creates a user account. Email, social sign-on, password, a basic identifier. The user cannot meaningfully use the product without completing it.
• Onboarding is the optional set of steps that personalise or prepare the user for the product. Profile picture, content preferences, goal selection, connecting external services.

Treating them as the same flow is a common mistake. The cost is that registration friction goes up (every onboarding question feels mandatory) and onboarding completion goes down (the user just wants in). Keeping them visually and structurally distinct lets each be optimised on its own terms.

Simplicity wins at the registration step

Registration is friction. Every additional click, screen, or required field reduces the chance the user completes it.

In LiveWell data, registration via Apple or Google saw roughly 3x the conversion rate of traditional email registration (around 63% vs. 20%). The reason is straightforward: platform-native identity providers and OS-level password managers remove almost all of the typing, and the user doesn’t have to invent and remember yet another password.

Simplification is subtractive

A specific lesson worth highlighting: simplification is not about moving things around or making screens prettier. It’s about removing whole screens and questions, and rewriting any copy that remains so it’s concrete rather than abstract.

In one LiveWell cohort, simply rewriting the onboarding questions to be less abstract took the share of new users answering all of them from 42% to 84%. No new logic, no new screens, just less abstract language.

A separate A/B test showed that adding a pre-registration carousel of app features did not improve registration rates (both groups landed around the same 17 to 18% install-to-enrolled rate). At the registration step it is too late to build intent. If the user is on this screen, they have already decided to try the app; anything extra you put in front of them is friction, not motivation.

Practical implications

For teams designing or auditing registration:

• Integrate platform-native sign-on (Apple, Google, equivalent) as a first-class option, not an afterthought
• Treat each additional field on the registration screen as having a measurable cost in completion rate
• Move personalisation questions into a distinct, optional onboarding flow after the account is created
• Use concrete language. “What time do you usually exercise?” beats “Tell us about your wellness habits.”
• Resist the urge to “sell” the product on the registration screen. Sell pre-download. Register fast.