Avoiding Common Marketing Automation Mistakes in Braze

A hand seating a cream connector into the first of three sockets on an oak board, with the last socket lit green, showing a Canvas journey checked in order from entry to exit.

This guide covers the marketing automation mistakes in Braze that sit in journey design: entry rules, exit rules, delivery controls and testing. Each one has documented Canvas behaviour behind it. The order below is the order a Braze implementation partner would check them in, starting with whether users enter at all.

Key Takeaways

  • Braze checks the Target Audience before it evaluates the entry trigger, and the checklist advises against using the same trigger in both Entry Schedule and Target Audience.
  • Re-eligibility and re-entry are separate settings, and a user can pass one and still be blocked by the other.
  • Exit criteria work best when property names and data types match the entry event, and a user in a Delay step leaves only when the delay ends.
  • Intelligent Timing conflicts with quiet hours and with rate limiting, so choose one control from each pair.
  • Stopping a Canvas doesn't remove users waiting on a Delay or Action Paths step.
  • Isolate Connected Content and webhook side effects before you preview or send test messages.

Which marketing automation mistakes in Braze should you check first?

The Braze Canvas documentation describes entry, exit, delivery and testing behaviour in detail. Its standard investigation path confirms the Canvas is active and the entry schedule matches expectations, then checks the user's messaging record. If no record exists for the expected send time, the issue is with entry, not the message.

We recommend the same order when you review a journey you've already built. Check entry, then exit, then delivery controls, then content. A fault upstream makes every later check misleading.

MistakeWhat the documentation saysCheck this first
Trigger repeated in the audienceDon't use the same trigger in both Entry Schedule and Target AudienceRemove it from Target Audience
Re-eligibility mixed up with re-entryA user can be re-eligible but blocked because they're still in the CanvasReview both settings together
Exit event that never matchesProperty names and data types in entry events must match exit criteria or Action Paths stepsCompare names and types
Exit expected mid-delayAn exited user stays in a Delay step until the delay endsPlan reporting around delay length
Competing delivery controlsIntelligent Timing conflicts with quiet hours and with rate limitingChoose one from each pair
Stop treated as a resetUsers waiting on a Delay or Action Paths step stay in the journeyReview waiting users first
Preview run with live side effectsConnected Content executes during preview user pathsIsolate profile-changing calls

Why do eligible users fail to enter a Canvas?

Braze checks the Target Audience before it evaluates the entry trigger, except for change in attribute triggers. A trigger on its own doesn't guarantee entry if the user wasn't in the audience when Braze evaluated it.

That makes a repeated trigger an easy mistake to build. If the same event sits in both Entry Schedule and Target Audience, users may not match the audience when the event arrives. The checklist advises against it and asks you to confirm the trigger action can't fire before the audience criteria are met.

Re-eligibility and re-entry are separate controls. Re-eligibility decides whether a user may enter again after exiting. Re-entry decides whether a user already inside can start a concurrent path.

A user can be re-eligible but blocked because they're still in the Canvas. Check both settings before you conclude the trigger failed.

If a user performs the same trigger several times within one second, Braze processes only one entry. When you test repeat entry, space your trigger events out.

What goes wrong when entry and exit events don't match?

The Braze example uses a ticket. A user who buys the ticket they selected exits and stops receiving reminders. A user who buys a different ticket stays in and keeps receiving follow-ups about the original one.

Either behaviour can be right, and the mistake is not deciding which you want. Braze asks you to verify that property names and data types in your entry events match those used in exit criteria or Action Paths steps.

The checklist also recommends aligning exit events with your primary conversion. Segment-based exits do the same job for users who no longer qualify. For conversion tracking, the exit criteria page recommends a conversion window that at least matches the longest path in the Canvas.

Why does an exited user still sit inside the journey?

When a user performs the exit event, Braze marks them to exit immediately. If they're in a Delay step, they remain in that step until the delay period ends.

Braze gives an example of a Delay step lasting 30 days. A user who performs the exit event on the first day is marked to exit right away. They don't fully leave until 29 days later.

We recommend judging a new Canvas on a reporting window that covers its longest delay. Exit counts can lag behind real behaviour when a long delay sits early in the journey.

How do delivery controls and send settings work against each other?

The QA checklist flags two documented conflicts. Intelligent Timing conflicts with quiet hours, and Intelligent Timing also conflicts with rate limiting. We recommend choosing one control from each conflicting pair and recording the choice in your build notes.

Advancement is a separate trap. By default, users advance through all Message steps regardless of whether they received the message. When a Message step aborts a send, the user still moves to the next step.

If you only want recipients to continue, add a Decision Split directly after the Message component. Braze also notes that users who can't receive a specific channel may still enter a variant. It recommends per-step Send Settings over narrowing Target Audience with channel filters.

What should you know before stopping or restarting a Canvas?

Stopping a Canvas blocks new entries and further messages from the Canvas flow. Email sends already handed to your email service provider can't be recalled. Users waiting on a Delay or Action Paths step aren't removed automatically.

If you re-enable the Canvas before their scheduled send time passes, they may still receive pending steps. We recommend treating a stop as a pause with a queue behind it. Review who is still waiting before you re-enable.

How should schedules handle daylight saving and time zones?

On daylight saving transition days, daily scheduled Canvases can run up to one hour earlier or later than usual. If your entry criteria depend on an attribute or event logged close to the entry time, users may not qualify yet. Braze advises making sure those updates land more than one hour before the scheduled entry time.

For local-time scheduled entry, launch the Canvas at least 24 hours before the intended entry time so no time zone misses the window. Action-based journeys have one more timing detail. Braze evaluates delays from the timestamp sent with the event, so use the current time and not a backdated one.

How do you test a Canvas without side effects?

Work through testing in an order that keeps live data safe:

  1. Preview user paths to confirm Delays, Decision Splits, Audience Paths and Action Paths behave as expected.
  2. Before previewing, remove or isolate any Connected Content or webhook that alters user profiles or data other Canvases reference. Connected Content executes during preview, and webhooks execute when test messages are sent.
  3. Send test messages to an internal group.
  4. For complex journeys, duplicate the Canvas, restrict entry to test users and reduce delays to about one second. We recommend keeping the audience limited to named test users until every branch has been exercised.
  5. Confirm control group size before launch, because you can't add a control group retrospectively.

What does a worked example look like?

Take a hypothetical retailer with an action-based Canvas that sends a basket reminder after a delay. The team sees shoppers who've already bought still getting the reminder. This is an illustration, not client work, and it carries no figures.

Entry comes first, and the Canvas is active with users entering, so that isn't the fault. Next the team checks the exit criteria. The purchase event carries its product identifier under a different property name from the basket event, so the comparison never matches.

Aligning the property names lets the comparison work for users who enter afterwards. Shoppers who bought during the delay still show as inside the journey until the delay ends. That's the documented behaviour, because they were marked to exit and won't advance.

The team reads exit counts over a window long enough to include the delay. The numbers then make sense.

How does this connect to the rest of the programme?

These mistakes sit alongside decisions covered elsewhere. Our guide to action-based and API-triggered entry covers the entry choice. Our piece on six failure modes in email automation covers sends that go wrong after entry.

For wider planning, see marketing automation best practices and using templates for faster automation. Onboarding journeys apply the same entry and exit logic, covered in Braze onboarding best practices. Our guide to automated campaign QA covers review habits.

As a Braze implementation partner, CustomerIK recommends reviewing every live Canvas in this order: entry, exit, delivery controls, then content. A short written check at each stage catches journey faults before customers see them. Confirm limits and behaviour against the Braze Canvas documentation before you rely on them, because features change.

Frequently Asked Questions

1. Why didn't a user enter my Canvas when they performed the trigger?

Braze checks the Target Audience before it evaluates the entry trigger, so a user outside the audience at that moment doesn't enter. Check audience membership, re-eligibility and re-entry settings, and whether the same trigger sits in both Entry Schedule and Target Audience.

2. What is the difference between re-eligibility and re-entry?

Re-eligibility decides whether a user can enter a Canvas again after exiting. Re-entry decides whether a user who is currently inside the Canvas can enter a concurrent path.

3. Does a user leave a Canvas immediately after the exit event?

Braze marks them to exit immediately, but a user in a Delay step stays in that step until the delay ends. They don't advance to later steps after that.

4. What happens to waiting users when I stop a Canvas?

Users can't enter and no further messages are sent from the Canvas flow. Users waiting on a Delay or Action Paths step aren't removed automatically, so re-enabling before their send time may deliver pending steps.

5. How long are Messaging History and Messaging Observability logs available?

Braze states they're available for up to 30 days from the event. Check the current documentation, because retention periods can change.

Sources

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

If your live Canvases need a second look at entry, exit and delivery settings, 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.