The first 72 hours decide who activates

The 72-hour pattern appears in almost every B2C product where activation data has been looked at carefully. A signup cohort does not activate at a uniform rate across the first week. The curve is steep at the front: hour 0 to hour 72 usually captures 60–80% of the users who will ever activate, and everything after is a long tail.

The reason is behavioural, not statistical. A user who just signed up has the product in their head. They have the reason they signed up still fresh. They're within the same context — same device, same intent, same mental state — that got them to sign up in the first place. Every hour that passes increases the probability that something else (work, life, a competitor's email) will take that context away. Once the context is gone, bringing it back is a different, harder campaign.

The lifecycle implication: treat the first 72 hours as a different phase of onboarding than the rest of week one. Higher message density, more channels, tighter triggers, and stricter stop conditions. A flat onboarding sequence spread evenly across seven days is under-delivered at the start and over-delivered at the end. The onboarding flows guide covers the full week-one structure this guide sits inside.

Three signals separate users who are going to activate from users who aren't, often within the first six hours. Watch these and you can intervene while intervention is still cheap.

Signal 1 — First meaningful action.Did the user take any action beyond signup confirmation within the first session? Opening a page doesn't count; taking a step toward the activation event does. Users who take nothing in session one activate at roughly a third of the rate of users who take something — and the gap widens by hour.

Signal 2 — Return visit.Did the user come back for a second session within 24 hours? This is usually the single most predictive signal of eventual activation, more predictive than the depth of the first session. A user who signed up, did a lot in session one, and then didn't return for three days is a much weaker bet than one who did a little in session one and came back the next morning.

Signal 3 — Personalisation investment. Did the user give the product anything — a profile field, a preference, a first piece of content, a connection to a tool? Users who invest something in the setup activate at meaningfully higher rates than users who accept all defaults. The investment is cheap psychologically but expensive to walk away from later.

The Orbit Lifecycle Reporting Framework skill covers how to instrument these three signals specifically so they show up in your dashboards, not buried in a raw event table nobody queries.

Different signal states call for different interventions. A flat "day 1, day 2, day 3" sequence ignores the difference. A better shape:

User took the first action, came back, invested something.On track. Light-touch messaging only. Avoid the common failure of keeping the onboarding push going for users who are clearly finding their way — they'll read it as the product not noticing them.

Took first action, hasn't returned.The most rescuable state. A well-timed push notification or email around hour 18–24 recovering the context ("you started X — here's how to finish") often lifts return rate significantly. The window is narrow; leave it past 36 hours and you're in cold-reactivation territory instead of warm-onboarding.

No first action, hasn't returned.Weakest state. The honest path here is a short, high-impact message at hour 24–48 that re-sells the product — not "finish setup" but "here's what this will do for you". Low conversion, but the alternative is zero.

Activated. Move them out of onboarding immediately. This is where most programs silently damage their brand — continuing to send onboarding messages to an activated user trains them to ignore your emails.

Email is the slowest channel in the onboarding stack, and the 72-hour window punishes slow channels. A message scheduled for 9am local delivery the day after signup is already halfway through the critical window. Push notifications, in-product tooltips, and SMS all move faster and should do the bulk of the work in the first 24 hours.

The practical split: in-product guidance for hour 0 to hour 2. Push notifications for hour 2 to hour 24. Email from hour 24 onwards. SMS as an optional channel for specific high-conversion moments (transactional confirmations, reminders at natural usage points, sometimes a single cart-style nudge).

The push-preview tool exists because push copy for onboarding needs the same discipline as email but gets a fraction of the attention. A push with truncated body text in the Android expanded view is worse than no push at all.

The hardest discipline in the 72-hour window is stopping. Every channel in the stack wants to fire. Product wants the in-app checklist up. Lifecycle wants the email sequence. Push wants a reminder. Done without coordination, the user gets four messages about the same thing in the first day, and three of them will train them to ignore you.

A simple rule that works: any channel firing a reminder about X suppresses all other reminders about X for the next 12–24 hours. This means one canonical state — usually the in-product completion state — that every channel reads before deciding whether to fire. Without that shared state, coordination is theatre.

The Orbit Multi-Channel Orchestration skill covers the full coordination layer — channel selection, frequency governance, and the shared-state pattern that lets this actually work across a real program.