Canvas exception events
As of February 28, 2023, you can no longer create or duplicate Canvases using the original editor. This article is available for reference when setting up exception events for the original Canvas workflow.
Braze recommends that customers who use the original Canvas experience move to Canvas Flow. It’s an improved editing experience to better build and manage Canvases. Learn more about cloning your Canvases to Canvas Flow.
When scheduling a component for a Canvas using the original Canvas editor, you have the option to set up an exception event. You can add an exception event to a component as long as the audience is not immediately advanced. Users who perform the exception event will not be advanced through the step and will drop out of your Canvas audience.
Exception events will only trigger while a user is waiting to receive the associated Canvas component. If a user performs the same action on a previous Canvas step, the exception event will not trigger.
For Canvas Flow, exception events are only configured using Action Paths. For example, you can define an Action Path and use the Everyone Else path as the exception.
Exception events for an action-based step will work during the step delay or window. Scheduled steps don’t have a window, and as a result, the exception event will only work if it happens during the delay.
For example, if you have an exception event for “Abandoned Cart” on the third step of your Canvas, but a user abandons their cart while they are on the second step, the exception event will not trigger. In this example, the exception event will only trigger if the user abandons their cart while on the third step of your Canvas.
Edit this page on GitHub