Braze Marketing Automation Use Cases: What to Build First

Wooden tray holding stacks of green and terracotta ceramic bowls while a hand places a green bowl on top of one stack, showing each automation build adding one mechanic.

Braze marketing automation use cases differ in the Canvas mechanics they need, so the order you build them in matters. Start with a welcome flow, then an abandoned checkout with matching exit criteria, then a win-back that relies on delays, then renewal or booking reminders. Each build adds one new mechanic and exposes one new failure mode while the stakes are still low.

Key Takeaways

  • Build the four use cases in order of new Canvas mechanics: welcome flow, abandoned checkout, win-back, then renewal or booking reminders.
  • Exit criteria can be matched to the entry event, so a shopper who buys a different item keeps receiving reminders about the original one.
  • A user marked to exit during a Delay step stays in that step until the delay ends.
  • Delay steps can run up to 730 days, and a calendar date that has already passed exits the user.
  • Message steps advance users whether or not the message was received, so add a Decision Split where receipt matters.
  • Check that the trigger appears on a live user profile before launch.

Which Braze marketing automation use cases should you build first?

Pick by mechanics, not by revenue promise. The Braze documentation describes how Canvas works and how to test it, and it does not rank use cases by value. Any ranking is therefore a judgement call.

As a Braze implementation partner, we recommend building in order of new mechanics introduced. A welcome flow needs an entry event and a few delays, and an abandoned checkout adds exit criteria that match the entry event.

A win-back adds long delays and splits. Renewal and booking reminders reuse all of it and add date logic.

This order means every new Canvas teaches the team one thing. If a flow misbehaves, you know which mechanic to suspect.

What does each use case need from a Canvas?

The table maps each use case to the mechanic that decides whether it works. Entry type is the first decision, and Braze documents three: scheduled, action-based and API-triggered.

OrderUse caseEntryMechanic that decides successFailure mode to plan for
1Welcome flowAction-basedDelay steps between messagesMessage steps advance users whether or not the message was received
2Abandoned checkoutAction-basedExit criteria matched to the entry eventUser exits on any purchase, or never exits at all
3Win-backScheduled or action-basedLong delays and a decision splitA calendar date that has already passed exits the user
4Renewal or booking reminderAction-basedAction Paths on the entry propertyProperty names differ between entry and exit events

The order and the entry column are our view. The mechanics and failure modes draw on the Braze Canvas documentation covered in the sections below, and the failure mode in the abandoned checkout row is our own reading of the exit settings.

How should you set exit criteria for an abandoned checkout?

Braze lets you add exception events to the Canvas entry rules, which removes users from the journey when they perform a specific action. Those exception events apply while a user waits in a step, including a Delay step.

The documentation goes further for an abandoned checkout. You can configure a user to exit only when they purchase the exact item they abandoned. If they buy something else, they keep receiving reminders about the original item.

That matching compares a property on the exit event with the stored entry data. In workspaces without Canvas Context, the personalisation menu labels that entry data Canvas Entry Properties instead, so check which label your workspace shows.

Our suggestion is to set the exit event to the matching purchase rather than any purchase. A shopper who buys a different item would otherwise stop getting reminders about the one they left behind, and reporting can still look healthy.

Why does a delay change what exit criteria do?

Braze records the exit as soon as the event happens. If the user is in a Delay step, they remain in that step until the delay period ends, and they then don't proceed into any following steps.

This matters when you read analytics. Exit activity can appear when the event happens and again when the Delay step completes, so we suggest planning reporting around the second moment, when the user has fully left.

Delays also have a definition worth knowing. A day in a Delay step is 24 hours, calculated from the time the user enters the step, while a calendar day waits until the next specified time, which can be shorter.

What goes wrong with action-based entry?

Each of the following is documented in the Braze Canvas QA checklist. The first two are named there as causes of an empty audience or of users who never enter.

  • Race conditions. For action-based entry, confirm the trigger action can't fire before audience criteria are met.
  • Duplicated triggers. Don't use the same trigger in both Entry Schedule and Target Audience.
  • Triggers that never arrive. Verify the triggering datapoint appears on a live user profile in Messaging History before launch.

Our suggestion is to check the third one first on any new build. Looking at a real profile takes minutes, and it settles whether the event is reaching Braze at all. If it is not, the work is integration rather than Canvas design, and CustomerIK's Braze services cover onboarding and technical integration.

How do you design a win-back flow that behaves?

Win-back relies on time. Delay steps can run up to two years (730 days), so a long wait is a design choice.

Pair it with a Decision Split, which checks segments and filters right after the previous step unless you add a delay.

Two documented behaviours catch people out. A calendar date that has already passed exits the user from the Delay step, and a Decision Split path with no step after it exits the user from the Canvas.

Set the re-eligibility window with care. The checklist says a wrong window causes over-messaging or retargeting issues. A win-back that over-messages works against its own purpose.

We recommend writing down what a lapsed user should have done before the first win-back message, and putting that check in the Decision Split. The split makes the rule visible on the Canvas where the next person will look for it.

What does a first build look like for a hypothetical ticketing business?

Take a hypothetical ticketing business that has never run an automated journey. This example is illustrative, uses no client data and describes no real result.

The team starts with the welcome flow. They confirm the sign-up event reaches a live profile, set a primary conversion event and add two delays. Nothing else is introduced, so any fault is easy to place.

Next comes an abandoned ticket purchase. A user enters when they select a ticket, and the entry event carries an event identifier. The exit event is a completed purchase compared against the stored identifier, so buying a different ticket does not end the flow.

The Braze documentation uses this same ticketing pattern, so the property names are the first thing the team verifies. Third comes the win-back, with a long delay and a split on recent activity. Last come booking reminders that reuse the matching logic from the second build.

By then the team has met each failure mode once, on a flow where the cost was small. We would expect the second build to take the longest to review, since matching an exit to an entry property is hard to see in a preview. That is our view, not a documented fact.

What should you check before any of these go live?

Work through the Braze checklist in order. These checks apply to every one of the four use cases.

  1. Confirm the entry type: scheduled, action-based or API-triggered.
  2. Set a primary conversion event, because conversion events power Canvas optimisation and reporting.
  3. Align exit events with that conversion, or add segment-based exits so users leave when they convert or no longer qualify.
  4. Review re-eligibility and check for overlap with other Canvases, so users don't receive competing messages from multiple journeys.
  5. For local-time scheduled entry, launch the Canvas at least 24 hours before the intended entry time so no time zone misses the window.
  6. Remember that users advance through all Message steps regardless of whether they received the message, and add a Decision Split if advancement should depend on receipt.
  7. Use control groups to measure the impact of the Canvas messaging.

Subscription settings apply to every Email and Push step in the Canvas, so set them once and deliberately. This post does not settle any question of consent law. The documented facts above are the limit of what it states.

How does this connect to the rest of the programme?

Entry choices are covered in depth in our guide to action-based and API-triggered automation. Once the four builds are live, complex Canvas workflows shows how to combine them without tangling the logic.

These flows often start in email, and six email automation failure modes is a useful companion to the win-back and abandoned checkout builds. For the retention side, see retention campaign mistakes to avoid in Braze Canvas.

When you add channels, cross-channel customer journeys in Braze covers sequencing. For a wider set of standards, read marketing automation best practices for Braze users.

For related work, the case study on interactive rewards for re-engaging lapsing users covers one approach to the win-back problem. The case study on a multi-brand rewards programme migration covers how existing lifecycle use cases were mapped before anything was built.

What does CustomerIK recommend?

As a Braze implementation partner, CustomerIK recommends treating the first four Canvases as a teaching sequence: one new mechanic per build and one written exit rule per flow before launch.

Frequently Asked Questions

1. Which use case should a team new to Braze build first?

Build the welcome flow. It needs an entry event and a few delays, so it introduces the fewest new mechanics. The order is CustomerIK's judgement, not a Braze ranking.

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

Canvas steps can move users only forward in the flow. Use delays and the re-eligibility window to control how often someone is contacted.

3. How long can a delay run in a Canvas?

Delay steps can be extended up to two years (730 days). Limits can change, so check the Braze documentation for the current figure.

4. What happens to a user who meets exit criteria during a delay?

They are marked to exit straight away but remain in the Delay step until it ends. They don't proceed into any following steps afterwards.

5. Why does an abandoned checkout Canvas keep messaging someone who bought?

Check whether the exit event compares the purchased item with the item stored at entry. Also verify that property names and data types in the entry event match those used in the exit criteria.

Sources

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

If you are planning your first four Canvases and want a second pair of eyes on the build order, 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.