A welcome push series for new app users
By Abdalla Kamesh · Published November 20, 2026 · 4 min read

Someone just installed your app. They tapped Allow on the notification prompt, which is the most valuable thing they will give you all year. The next week decides whether they keep it on.
A good welcome series does two jobs. It shows the shopper what the app is for, so they open it again. And it earns the right to send the next message, so they do not turn notifications off. This post builds a short series in a StoreToNative app, using Journeys (Pro and Agency).
Before the first push: the intro slides
The welcome starts before any notification. The app’s intro slides, which you set in the Design studio, are where the shopper first meets the app, and the last slide (or the first launch) is where the app asks for notification permission. Tell the shopper what they will get: order updates, a heads-up when something they watch is back in stock or cheaper, the occasional offer. A shopper who knows what is coming is far less likely to say no. App onboarding screens that don’t annoy covers the slides themselves.
The ready-made Welcome journey
Open Journeys in the console. One of the four ready-made journeys is Welcome: it starts when a shopper installs your app and, after a day, sends a welcome push. Switch it on with the Live switch and you have a one-step welcome.
That is a fine start. The series below adds two careful follow-ups.
A three-push series
Build it with Start from blank and the trigger “a shopper installs your app”, or edit the ready-made one.
Push 1, after one day: say what the app is for. Not a sale. A short line on the useful things: “Your orders, tracked in one place. Watch any product to hear when it’s back or cheaper.” Let it open the app home.
Wait two days, then a Check: “Have they ever ordered?” A check splits the flow into Yes and No. Leave the Yes side ending in Stop: a shopper who has already bought does not need a nudge. The blocks you add after the check go on the No side, for shoppers who have not bought.
Push 2, day three: one good reason to look. Your bestsellers, a new arrival, the category most people buy first. Open it on that category, not the home screen.
Wait four days.
Push 3, day seven: the personal touch. Something that sounds like the store, not a robot: what you are working on, a product you love, how to reach you. Then Stop.
That is three pushes in a week at most, and fewer for anyone who buys: a journey ends by itself the moment a shopper places a paid order in the app.
The rules that protect you
Journeys follow safety rules you cannot turn off:
- A journey stops as soon as the shopper places a paid order in the app, or turns notifications off.
- No journey push goes out between 9 pm and 9 am in the shopper’s time zone; a due push waits until the morning.
- A shopper gets at most one journey push a day, across all journeys.
The editor also checks the journey before you turn it on: one to four pushes on any path, at least 24 hours between two pushes, and no path longer than 21 days. The series above fits all of them.
What a welcome journey cannot do yet
A Discount push (a push that names one of your app-only codes) works in other journeys, but a welcome journey cannot send a discount yet. If you want to reward the first order, use the Thank a first-time buyer automation on the Push page instead: it sends once, after a shopper’s first order through the app. That is a better moment for a thank-you anyway, because the shopper already said yes to you.
Read the numbers after two weeks
Each block in the journey shows its own numbers: how many shoppers reached it, pushes sent and opened, and paid orders after it. Each check shows how many went Yes and No. The row at the top shows the last 30 days: shoppers who entered, paid orders, revenue, pushes sent.
Look at the drop between push 1 and push 2. If almost nobody opens push 2, change its words or what it opens on. If shoppers turn notifications off during the series, cut a push.
Write like a person
Every push in a welcome series is read by someone who just met you. Use short words, one idea per message, and the store’s own voice. Push notification copy that converts has examples, and how often to send push notifications explains why less is usually more. The push notifications guide is the place to start if your app is new.