Every app install starts a countdown. Most users who go quiet do it in the first few days — not because the app failed them, but because nothing pulled them back before your app slid off their mental home screen. The first week decides whether an install becomes a customer or a dormant icon, and app onboarding push notifications are the highest-leverage tool you have inside that window.
This guide builds the series step by step: the milestones to map, the message-by-message sequence from install to first purchase, the exit rules that keep it from becoming spam, and the numbers that tell you it’s working.
The dormancy cliff, and why onboarding owns it
Re-engagement campaigns get the attention, but they fight uphill: by the time a win-back fires, the user has already decided your app isn’t part of their routine. Onboarding pushes work with gravity instead. The user just installed, intent is at its lifetime peak, and each message lands while the decision “is this app worth keeping?” is still open. A percentage point of improvement here is worth several points of win-back effort later.
Map milestones before you write a single message
A calendar-based drip (“day 1, day 3, day 7”) treats every user identically regardless of what they’ve done. A milestone-based series is smarter: each message targets the next incomplete step in the user’s journey, and skips users who already took it. For a commerce app the ladder usually looks like:
- Install → granted push permission
- Permission → account created
- Account → first product browsed or saved
- Browse → first item carted
- Cart → first purchase — the milestone that predicts everything after it
Instrument each milestone as a custom event with the iOS SDK’s trackEvent call — one line per milestone. Those events become both the triggers and the exit conditions for every message below.
PushEngage.trackEvent(name: "onboarding_first_save",
properties: ["category": "outerwear"],
profileId: currentUserId,
provider: nil, eventType: nil) { _, _ in }The series: install to first purchase
Before message one: earn the permission
None of this fires without notification permission, and iOS gives you one native shot at it. Ask at a value moment with a soft-ask screen first — the full pattern is in our iOS permission priming guide. Done right, the permission grant is itself the first onboarding milestone.
Message 1 — a few hours after install: the welcome
Not “welcome to our app” — a door back in. Deliver one concrete piece of value: the promised welcome offer, the feature that motivated the install, or the item they browsed in their first session. The welcome notification principles from web push apply directly: specific, warm, and useful beats ceremonial.
Message 2 — day 1–2: the next-step nudge
Fires only for users stuck below a milestone: account not created, nothing browsed. Point at the single next action, deep-linked to the exact screen where it happens. Users who already took the step never see this message — that’s the milestone branching doing its job.
Message 3 — day 3–4: discovery
The user has poked around but hasn’t committed. Show them the thing they haven’t found yet: a category they’d like based on their browsing event properties, a feature that makes the app stickier (saved sizes, price alerts), or honest social proof. This is the message that most benefits from the event properties you attached in trackEvent — “new arrivals in outerwear” beats “check out what’s new.”
Message 4 — day 6–7: the first-purchase close
For users who carted but didn’t buy, the cart abandonment sequence already has them — don’t double-send. This message is for the browsers: a time-boxed first-order incentive if your margin supports one, or your strongest value framing if it doesn’t. Either way, day 7 ends the onboarding series. Whatever happens next belongs to your regular lifecycle campaigns.
The rules that keep it welcome
- Exit on milestone, not on schedule. A user who purchases on day 2 exits the entire series that instant.
- One message per day, maximum. If the cart sequence is active, the onboarding series yields.
- Respect quiet hours and time zones. A 3 AM welcome is an uninstall generator.
- Every message deep-links to the action it asks for. Never the home screen.
Measure activation, not opens
The series has exactly one success metric: what percentage of new installs reach first purchase (or your app’s equivalent activation milestone) within 14 days, versus the pre-series baseline. Open rates diagnose copy; activation lift justifies the program. Attach goal tracking so each message’s contribution to completed first purchases is attributed automatically, and review the funnel monthly — the message with the weakest milestone-completion lift is the one to rewrite.
Build it once, benefit on every install
An onboarding series is the rare campaign you build once and every future user flows through. Instrument the milestones, configure the triggered sequence in the dashboard, and let the branching handle the rest. For the broader strategy this slots into, see the app push marketing guide — and when you’re ready to build, the setup guide plus an afternoon gets you live.
