Using Braze for Cross-Channel Customer Journeys

Hand holding a paper ticket toward a green-lit sign on a second tram platform while a tram arrives on the first, showing a fallback route in a cross-channel journey.

A cross-channel customer journey in Braze is a Canvas that moves one customer through a sequence of steps. Each step chooses a channel, a wait, a branch or an exit rule. This guide explains how those steps behave, where journeys tend to go wrong, and how to sequence channels so each message earns its place.

Key Takeaways

  • A Canvas moves customers through steps in sequence, and each step is best given one decision to own.
  • A customer who can't be reached on a channel advances with nothing sent, so plan an explicit fallback.
  • Delay steps can run up to two years (730 days), and a calendar date that has already passed makes customers exit.
  • The Action Paths evaluation window defaults to one day and has a maximum of 31 days.
  • Evaluating engagement straight after a send catches customers before they can respond, so add a delay first.
  • An exit event marks a customer to exit straight away, but a customer waiting in a Delay leaves only when the delay ends.

How do Braze cross-channel customer journeys work in Canvas?

Braze describes Canvas as a unified interface where marketers craft campaigns with multiple messages. Steps occur in sequence, so the first step happens before the second can.

Within a step you can set triggers or schedule delivery, refine targeting with filters or exception events, and pick a channel such as push or a webhook.

Customers enter a Canvas by schedule or by an action-based trigger. Action-based entry responds to customer behaviour as it happens. That choice matters later, because event properties can't be used in the lead Message step.

Which channels can one Canvas use?

The Message step page offers nine channel options. They include email, push notifications, in-app messages, Content Cards, banners, webhooks, WhatsApp, and SMS, MMS and RCS. One journey can use several of them in turn.

The Message step also defines when a customer moves on. A customer advances if the message is sent, frequency capped, aborted, or can't be reached on that channel, or if they fail the delivery validations.

An unreachable customer doesn't stall the journey. They simply move to the next step with nothing sent.

Delivery validations check profile criteria at send time, and Braze recommends them when Quiet Hours, Intelligent Timing or rate limiting are enabled. For in-app messages they are checked on entry to the Message step, before the message displays.

We recommend treating that behaviour as the reason a cross-channel journey needs an explicit fallback. If the next step assumes the first message landed, a customer who was unreachable on that channel gets a follow-up to something they never saw.

For a worked example of fallback in practice, see our case study on unifying guest profiles for a global hotel brand, which covers Canvas journeys built around an automated fallback from WhatsApp to SMS and then email.

What does each Canvas step decide?

Before building, it helps to name the one decision each component owns. A journey that asks one step to make two decisions is usually the one that's hard to debug later.

ComponentThe decision it owns
MessageWhich channel carries the message, and whether delivery is validated at send
DelayWhen the customer moves on: a duration, a calendar date or a day of the week
Decision SplitA true or false query on segments and filters
Action PathsWhich route a customer takes based on what they do within an evaluation window
Audience PathsWhich route a customer takes based on the first group whose criteria they meet

How should you sequence channels and delays?

Delays do the sequencing work in a journey. A Delay step can hold customers for a duration, until a calendar date, or until a day of the week. You can extend it up to two years (730 days), and you can delay at company time or at a customer's local time.

Profile changes made during a delay are reflected when the customer advances. A customer who gains a new contact detail while waiting can therefore become reachable on a channel they didn't have at entry.

Two cautions apply. If a calendar date has already passed when customers reach the step, they exit the Canvas. And a Delay with nothing after it advances customers straight out.

We recommend planning the journey as a ladder. Put the first message on the channel the customer is likeliest to see, then wait long enough for it to land before any second channel is used. A second channel that arrives within minutes of the first reads as repetition rather than a second chance.

When should you branch on what a customer did, and when on who they are?

Action Paths sorts customers by what they do. The evaluation window defaults to one day, can be adjusted, and has a maximum of 31 days.

With ranking off, the first qualifying action sets the route, and customers who do nothing take the Everyone Else group at the end of the window. With ranking on, everyone is held until the window closes and then takes the highest priority group they qualify for.

Audience Paths sorts customers by who they are right now. Customers take the first branch whose criteria they meet, and a single step can hold up to eight audience groups.

Evaluation uses current attributes, filters and segment membership at that moment, and ignores the event that triggered entry. Once placed in a group, a customer stays there even if their profile changes afterwards.

A Decision Split asks one true or false question. By default its filters are checked right after the previous step unless you add a delay.

The failure mode to name first is evaluating engagement too early. Braze documents that evaluation is immediate and that customers are checked for an interaction almost immediately after a message sends. So an Audience Paths step or a Decision Split placed straight after a Message step will send nearly everyone down the "did not engage" branch.

Our suggestion is to put a delay between them that matches how long a customer realistically needs to respond.

One documented trap sits in the in-app channel. When an action group's trigger is starting a session and the next step is an in-app message, the customer must perform two session starts to receive it. Allow for that when you choose the trigger.

How do you stop a journey once the customer has converted?

Exit criteria add exception events to the entry rules. When a customer performs the exit event, Braze marks them to exit straight away. Exception events apply even while a customer is waiting in a step such as a Delay.

Examples include placing an order, starting a session, performing a custom event or adding an email address.

There's a timing detail to plan around. A customer in a Delay remains in that step until the delay ends, and only then leaves the Canvas.

Conversions are tracked after the Canvas ends, but exits are not tracked once a customer has exited. Braze recommends setting the conversion window to at least match the longest path in the Canvas.

We recommend treating exit analytics as lagging behind customer behaviour. A customer who buys on the first day of a long wait has stopped receiving messages, yet the exit may not appear in your reporting until the wait finishes. Don't read a low exit count as a sign the exit rule failed.

Exit rules can also be matched to the entry event. In an abandoned checkout Canvas, Braze shows how to exit a customer only when they buy the exact item they abandoned, while still sending reminders if they buy something else. Check that property names and data types in the entry event match those used in the exit criteria.

What does a cross-channel journey look like in practice?

Take a hypothetical homeware retailer that wants to win back customers who start checkout and stop. This is an illustration of the advice above, not client work and not a Braze template. The numbered steps show one reasonable ordering.

  1. Entry: Use an action-based entry on a custom event for checkout started, carrying an item identifier as an entry property.
  2. Exit rule: Set the purchase event as an exception event, with a filter that matches its item identifier to the entry property. Only a purchase of the abandoned item ends the journey.
  3. First message: Send an email after a short delay, with delivery validation switched on and a segment that excludes customers who have since bought.
  4. Wait: Add a delay long enough for the email to be opened, because evaluation steps check engagement immediately.
  5. Branch on action: Use an Action Paths step with a one week window. Customers who bought a different item get a reminder about the original. Everyone Else moves on.
  6. Branch on channel eligibility: Use a Decision Split on whether the customer can receive push. Those who can get a push reminder. The rest get a final email.
  7. Measure: Pick a conversion event, and hold back a control group so you can see what the journey added.

The retailer ends up with one goal, one exit rule and a named fallback for the customers a channel can't reach. Test every component in a development environment before launch.

What goes wrong when you change a live journey, or run several at once?

Editing a live Canvas has documented edges. Schedule changes apply only to customers who aren't already waiting for the step.

Stopping a Canvas doesn't remove waiting customers from a Delay at once, and if the delay window passes while the Canvas is stopped, those customers exit instead of receiving the next step.

When in doubt, Braze advises stopping the Canvas, duplicating it and relaunching for a clean re-evaluation. Don't change the ranking setting on an Action Paths step after launch if customers are already in it.

Overlap is the other risk. Braze's release notes list Message Prioritization as generally available from 15 Oct 2026, described as an optional layer on top of frequency capping. Release status can change, so check the current documentation before relying on it.

Before launching a new journey, we recommend listing every other journey and campaign that can reach the same customer in the same week. Decide which one wins when they collide. That decision is cheaper to make on paper than after customers have received two messages on two channels in one afternoon.

How does this connect to the rest of the programme?

A journey is only as good as the audiences and data behind it. Our guide to building multichannel engagement campaigns in Braze covers the campaign side, and the post on automating complex workflows in Braze Canvas goes deeper on branching.

Audience quality decides who enters at all, so read segmenting your audience for better engagement in Braze alongside this one. For the wider plan, see building a customer engagement strategy with Braze. Two further reads cover retention campaign mistakes to avoid in Braze Canvas and optimising the customer journey with Braze data.

As a Braze implementation partner, CustomerIK recommends mapping the journey on paper before opening the builder. Write down one goal, one exit rule and a named fallback for every channel, then build only what that map needs.

Frequently Asked Questions

1. How many channels can one Canvas use?

The Message step page offers nine channel options, and one Canvas can use several of them across its steps. Check the page for the current list.

2. Can a Canvas send a customer back to an earlier step?

Canvas steps move customers forward only, so a step can't link back to a previous one.

3. How long can a customer wait in a Delay step?

Delay steps can be extended up to two years (730 days), as documented on 04 Nov 2026.

4. What is the longest Action Paths evaluation window?

The documented maximum is 31 days. The default is one day.

5. What happens to a customer who can't be reached on a channel?

They advance to the next step without a send. Add a Decision Split or an Audience Paths step if you want a different channel to cover them.

Sources

CustomerIK is a Braze implementation partner working across onboarding, technical integration, marketing operations and customer data management.

If you're planning a Canvas that crosses email, push and in-app and want a second pair of eyes on the exit rules and fallbacks, let's talk.

Preferences

Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website.

Accept all cookies
Accept all cookies

These items are required to enable basic website functionality.

Always active

These items are used to deliver advertising that is more relevant to you and your interests.

These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features.

These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.