
Braze onboarding best practices rest on four decisions made before launch. They cover how a new user enters the Canvas, what makes them leave, how you confirm a message was received, and what you check after go-live. This post takes each decision from Braze documentation and applies it to a hypothetical subscription app.
Key Takeaways
- Settle purpose, entry, exit and conversion, advancement and channels in that order, before anyone writes a message.
- The Braze onboarding template keeps entry action-based on session start, so test the trigger with a fresh user.
- A user who performs the exit event during a Delay step stays in that step until the delay ends, then goes no further.
- Users advance past Message steps by default, so add a Decision Split on Received Message from Canvas Step where a later step depends on receipt.
- Set the conversion window to at least match the longest path, and decide the control group before go-live because it can't be added retrospectively.
- After launch, check bounce, error and rejection spikes and the first step's send breakdown in Canvas analytics.
What do Braze onboarding best practices start with?
The Braze Canvas guidance opens by asking what users should accomplish, who you are trying to reach and why you are building the Canvas. For onboarding the answers are short: the user is new, the goal is a first useful action, and the reason is the first impression.
The Braze onboarding template is intended for the consideration stage of the user lifecycle, and it targets users who first used an app less than one day ago. That narrow audience is a good default. It keeps the onboarding Canvas about new users and leaves lapsed users to journeys built for them.
Should onboarding entry be action-based?
The template keeps entry action-based, so a user enters when they start a session in any app. That suits onboarding because the first session is the moment worth responding to.
Action-based entry has one failure mode to design out. The Canvas QA checklist asks you to confirm that the trigger action can't fire before audience criteria are met, and says not to use the same trigger in both Entry Schedule and Target Audience. We recommend testing with a fresh user, created after the Canvas is built, because it tells you more than reading the filters ever will.
Re-eligibility belongs in the same conversation. The checklist asks you to set the re-eligibility window correctly to prevent over-messaging or retargeting issues. For onboarding, that means deciding up front whether a returning user can enter again.
When should a new user leave the onboarding Canvas?
Exit criteria remove users when they perform a specific action, and Braze records the exit as soon as the event happens. The QA checklist recommends aligning exit events with your primary conversion, or adding segment-based exits so users leave when they convert or no longer qualify.
The timing has a detail that matters for welcome series. If a user is waiting in a Delay step when they perform the exit event, they remain in that step until the delay ends. They don't proceed into any following steps when it finishes.
Reporting follows the same logic. Conversions are tracked even after the Canvas ends, but exits are not tracked once the user has left. Braze recommends setting the conversion window to at least match the longest path in the Canvas.
A window shorter than the longest path can make a slow welcome series look weaker than it is. We recommend setting the window before anyone reads the first report.
What order should these decisions be made in?
We recommend making the decisions in the order the Canvas will meet them. Purpose first, then entry, then exit and conversion, then advancement, then channels. Starting from the welcome email leaves the exit rule to be decided after the copy is approved, which is the wrong way round.
| Decision | What Braze documents | Sequencing advice |
|---|---|---|
| Entry | The template uses action-based entry on session start | Test with a fresh user before writing content |
| Exit | Align exit events with the primary conversion | Decide before the welcome series is drafted |
| Advancement | Users advance through Message steps by default | Add a Decision Split where a later step depends on receipt |
| Conversion window | Match the longest path in the Canvas | Set at build, not at first report |
| Control group | A control group can't be added retrospectively | Decide before go-live |
Does every user advance past a message they never received?
By default, users advance through all Message steps regardless of whether they received the message. For a light welcome series that can be fine. For an onboarding Canvas where step three assumes the user saw step two, we recommend making it an explicit decision.
Braze documents the pattern. Add a Decision Split directly after the Message component, with the filter Received Message from Canvas Step.
For in-app messaging, use an Action Paths component instead. For a multi-channel Message step, include a Delay step of at least five seconds between the message and the split.
How should onboarding messages be sequenced across channels?
The Braze onboarding template assumes three emails exist before you start: a welcome email, a tips email and a feedback email with a survey. It splits users by whether they clicked the welcome email, and Braze recommends a Delay step to avoid overwhelming users with repeated messaging.
The preferences survey template uses a three-day window to split users by whether they started a session or clicked the onboarding email. Users who finish onboarding exit the Canvas.
The in-app onboarding flow template collects user attributes, insights and preferences. Its messages need to be connected in sequential order so users move through the flow correctly.
Channel choice should follow reachability. The checklist suggests routing push-enabled users toward push steps and email-subscribed users toward email using Audience Paths, so reporting sizes stay accurate. Our suggestion is to start the sequence on the channel where you hold both a subscription and a device, and add the others as that user's data arrives.
Which QA checks fit an onboarding Canvas?
The Braze checklist runs in five phases, from setup and governance to post-launch monitoring. Not every item applies to every Canvas. These are the ones an action-based onboarding journey leans on.
- Confirm the entry type and use consistent naming so teammates can find the Canvas.
- Set the exit criteria to match the primary conversion.
- Review subscription settings. They decide who can receive email and push, and they apply to every Email and Push step in the Canvas.
- Verify that the triggering datapoint appears on a live user profile in Messaging History before launch.
- Duplicate the Canvas, restrict entry to test users only, and reduce delays to about one second to speed up QA.
- Decide the control group before go-live, because it can't be added later.
- For local-time scheduled entry, launch at least 24 hours before the intended entry time.
Subscription settings touch consent. What a market requires before you message a new user is a legal question, and this post doesn't settle it. The Braze setting you choose should follow the answer your own policy gives.
What should you watch after an onboarding Canvas goes live?
Start with deliverability. The checklist asks you to check for bounce, error or rejection spikes before volume ramps. Then compare entries with sends: check the entry audience and the first step's send breakdown in Canvas analytics.
An empty audience is usually a race condition or an over-restrictive filter. For edits made close to a scheduled entry or send window, Braze gives one rule. When in doubt, stop the Canvas, duplicate it, and relaunch for a clean re-evaluation.
We recommend rehearsing that relaunch on a duplicate with test users first, never directly on live traffic.
What does this look like for a hypothetical subscription app?
Imagine a subscription app that wants new users to start a trial in their first week. This is an illustration, not client work, and it uses no real data.
The Canvas enters users on their first session. Its primary conversion and its exit event are both the trial start, so a user who converts on day one stops receiving welcome messages. The conversion window is set to cover the longest path, which is the slowest route through the delays.
The first Message step is a welcome email. A Decision Split follows, filtered on Received Message from Canvas Step, so the tips email only goes to people who got the welcome.
A user who doesn't open the app sees an in-app onboarding flow on their next session, which asks for preferences. The team decides the control group before launch and tests on a duplicate restricted to test users.
How does this connect to the rest of the programme?
Onboarding Canvases sit inside a wider programme, and several CustomerIK posts go deeper on single parts of it. Start with building an onboarding workflow step by step if you are laying out the journey, and read measuring onboarding success before you choose a conversion event.
For mobile-first products, onboarding new mobile users from first open covers the first-session detail. Personalised onboarding with Canvas and feedback surveys for onboarding cover the branches. Push notifications for onboarding completion covers the nudge that finishes the job.
As a Braze implementation partner, CustomerIK recommends settling entry, exit and conversion window on one page before anyone drafts a message. Then run the QA steps above on a duplicate with test users.
Frequently Asked Questions
1. What is the first decision to make in a Braze onboarding Canvas?
Purpose: what users should accomplish, who they are and why you are building the Canvas. Entry and exit rules follow from those answers.
2. Should onboarding use action-based entry?
The Braze onboarding template does, entering users when they start a session. Test the trigger with a fresh user, and don't use the same trigger in both Entry Schedule and Target Audience.
3. What happens when a user performs the exit event during a Delay step?
Braze marks them to exit immediately, but they remain in the Delay step until it ends. They don't proceed into any following steps.
4. Do users advance if they never received a message?
By default, yes. Add a Decision Split with the filter Received Message from Canvas Step when a later step depends on receipt. For in-app messages, use an Action Paths component.
5. Can I add a control group after launch?
Braze documents that a control group can't be added retrospectively. Set variant and control percentages before go-live.
Sources
- Braze, Canvas best practices. Retrieved 09 Nov 2026.
- Braze, Onboarding (Canvas template). Retrieved 09 Nov 2026.
- Braze, Onboarding with preferences survey (Canvas template). Retrieved 09 Nov 2026.
- Braze, Onboarding flow (in-app message template). Retrieved 09 Nov 2026.
- Braze, Canvas QA checklist. Retrieved 09 Nov 2026.
- Braze, Exit criteria. Retrieved 09 Nov 2026.
- Braze, Matching exit criteria to entry events. Retrieved 09 Nov 2026.
- Written by CustomerIK, a Braze implementation partner.
CustomerIK is a Braze implementation partner working across onboarding, technical integration, marketing operations and customer data management.
If you are planning an onboarding Canvas and want a second pair of eyes on entry, exit and advancement before launch, let's talk.




