Action Paths in Canvas allow you to sort your users based on their actions.
Using Action Paths, you can:
- Customize user paths based on a specific action, including user engagement events and custom events
- Hold users for a given duration to prioritize their next path based on their actions during this evaluation period
Create an action path
To create an action path, add a component to your Canvas. Drag and drop the component from the sidebar, or click the plus button at the bottom of a step and select Action Paths.
In the Action Settings module, you can choose how long you’d like to hold users in the action step by setting the Evaluation Window. By default, users are evaluated within one day, but you can adjust this window by seconds, minutes, hours, days, and weeks depending on your Canvas. Note the maximum evaluation window for an action path is 31 days.
Within the Action Settings, you can also turn on the ranked order for your components by switching on the Advance users based on ranked order toggle.
By default, Ranking is off. When a user enters the action path and performs the trigger event attached to any action group, they will immediately advance through the relevant action group. If a user doesn’t perform a trigger event, then they will advance through the default Everyone Else group at the end of the evaluation period.
When Advanced users based on ranked order is enabled, this means that Ranking is on. So, all users will be held until the end of the evaluation window. At the end of the evaluation period, users will advance through the highest priority action group that they are eligible for at the end of the evaluation window. Users who do not perform any of the actions during the evaluation window will advance through the default Everyone Else group.
Note that when the action group trigger is starting a session and the next step is an in-app message, the user will need to perform two session starts to receive the in-app message. The first session assigns the user to the action group within the action path, and the second session triggers the in-app message.
Ranking status example
Let’s say you have an action path with an evaluation period of one day with two action groups: Group 1 and Group 2. Group 1 has a trigger event “Start Session”, and Group 2 has “Make Purchase”. If Ranking is turned on, then all users in the action path are “held” for one day. At the end of the day, if a user has started a session and made a purchase, then they advance to the highest rank path. In this case, the user would advance to Group 1.
In the preceding example, if Ranking is off and when a user performs one of the trigger events (“Start Session” or “Make Purchase”), that user is advanced in the relevant action group based on the trigger action.
Note that Canvas entry properties differ from event properties. Canvas entry properties are properties from the event that triggered the Canvas. These properties can only be used in the first full step of a Canvas when using the original Canvas workflow. When using Canvas Flow, Persistent Entry Properties are enabled and allow the entry properties to be re-used throughout the whole Canvas. Conversely, event properties originate from an event or action that occurs as the user goes through their workflow.
Add a trigger or multiple triggers to define your action groups. Here, you can select a range of trigger events such as custom events, engagement events like interactions with your app, and more.
Within each action group settings, you also have the option to select the checkbox I want this group to exit the Canvas, meaning that the users within this group will exit the Canvas at the end of the evaluation period.
Canvases with re-eligibility
If users enter into an action path multiple times and have multiple entries in the action path at the same time, the expected behavior varies depending on the Ranking status.
|Ranking Status||Action Path Behavior|
|Off||When a relevant action is performed, Braze will deduplicate entries and immediately advance the earliest entry through the relevant action group.
When a relevant action is not performed, all entries will advance at the end of the relevant evaluation window. No deduplication will occur.
|On||All entries will advance at the end of the relevant evaluation window. No deduplication will occur.|
Note that the rankings aren’t editable after launch.