Branch components
Branch components route users through different paths in a Journey based on specific criteria. Use them to create different experiences for users based on their profile data, previous message interactions, test variants, or how often they have passed through a Journey step.
The following Branch components are available:
User Branch: Routes users based on user data and conditions
Check Interaction: Routes users based on their interaction with a previous message or campaign
Variants: Splits users into different test groups
Capping: Controls how often users can pass through a specific point in a Journey
User Branch
User Branch allows users to follow different paths in a Journey based on conditions. Use it when the Journey should take different actions depending on information about the user.
For example, users with a Premium subscription can follow one path, while users with a Standard subscription follow another path.
Add a User Branch
Add a User Branch to the Journey where users should be evaluated against specific conditions.
Each path in the User Branch has its own conditions. When a user reaches the branch, Netmera evaluates the conditions and routes the user to the corresponding path.
Choose a condition type
Select the type of information that should be used to evaluate the user.
Available condition types include:
Profile Attribute: Evaluate information stored in the user's profile
Segment: Route users based on segment membership
Tag: Evaluate tags assigned to the user
Event: Evaluate events performed by the user
Select the condition type that matches the information that should determine the user's path.
Define the condition
After selecting a condition type, define the criteria that the user must meet.
Select an operator and specify the value for the condition.
For example:
Subscription Level → equals → Premium
This condition routes users whose Subscription Level is Premium to the corresponding path.
Select Add to save the condition.
Multiple conditions can be added to a path when more specific criteria are required.
Add groups
Use groups to combine multiple conditions and create more detailed branching logic.
Select Add Group, then add the conditions that should be evaluated together.
Each group uses one of the following logical operators:
Match all conditions: The user must meet all conditions in the group
Match any condition: The user must meet at least one condition in the group
For example, a group using Match all conditions can route users who are both in a specific segment and have a specific profile attribute.
Check Interaction
Check Interaction allows a Journey to evaluate how users interacted with a message or campaign that was created before the Journey started.
Use this component when the next Journey step should depend on whether a user received, opened, or clicked a previous message.
For example, users who opened a previous push notification can follow one path, while users who did not open it can follow another path.
Configure the interaction check
Select the Check Interaction step to open its configuration options.
Step name
Enter a meaningful name that describes the interaction being checked.
A descriptive name makes the step easier to identify when reviewing or managing the Journey.
For example:
Opened Welcome Push
Search message by name
Search for and select the message or campaign that should be checked.
The selected message determines which user interaction Netmera evaluates.
For example, select a campaign named Welcome Push to check whether users interacted with that campaign.
Interaction type
Select the interaction that should determine the user's path.
Available options include:
Received
Not Received
Opened
Not Opened
Clicked
Not Clicked
The available interaction types depend on the channel of the selected message.
Choose the interaction type based on the channel
Use the interaction type that corresponds to the selected message channel.
Received / Not Received
Available based on the selected message
Clicked / Not Clicked
Push Notifications
Opened / Not Opened
Mobile Widget, Web Widget, SMS, E-mail
For example, use Clicked to check whether a user clicked a Push Notification. Use Opened to check whether a user opened an E-mail.
Look back (days)
Specify how many days Netmera should check for the selected interaction.
For example, enter 7 to check whether the user performed the selected interaction within the specified 7-day period.
This allows the Journey to evaluate recent user behavior rather than checking interactions without a defined time frame.
Variants
Variants allows you to test different versions of a message or action within the same Journey.
Use Variants when you want to divide users into different groups and provide each group with a different experience. This can be used to compare different messages, content, designs, or actions.
For example, create two variants of a Push Notification:
Variant A: Message with a discount offer
Variant B: Message with a different offer
Users are distributed between the variants according to the percentages configured for each variant.
Configure variants
Select the Variants step to configure the test groups and the actions users receive in each group.
Step name
Enter a meaningful name that describes the test.
For example:
Push Notification A/B Test
A descriptive name makes the test easier to identify when reviewing the Journey and its results.
Add variants
Select + to create the variants that should be tested.
Each variant represents a different version of the experience.
For example:
Variant A - Discount Offer
Variant B - Free Shipping
Add as many variants as required for the test.
Set distribution percentages
Define the percentage of users who should enter each variant.
Select the percentage value next to a variant and enter the required distribution.
For an equal split between two variants:
Variant A
50%
Variant B
50%
You can also use different percentages when one variant should be shown to a smaller or larger portion of users.
For example:
Variant A
70%
Variant B
30%
The configured percentages determine how users are distributed across the variants.
Define actions for each variant
Configure the message or action that users should receive after entering each variant.
Each variant can contain a different set of Journey steps.
For example:
Variant A - Discount Offer
Add a Push Notification with a discount-focused message.
Variant B - Free Shipping
Add a Push Notification with a different offer.
Different variants can also use different content, designs, or actions depending on the purpose of the test.
Save the configuration
After configuring the variants, distribution percentages, and actions, select Save.
The Variants step is then added to the Journey and can be connected to the subsequent Journey steps.
Capping
Capping controls how often users can pass through a specific point in a Journey.
Use Capping when users should not repeatedly receive the same communication or pass through the same Journey step without a limit.
For example, a Journey can allow a user to pass through a specific message step once, or allow multiple passes with a defined waiting period and maximum number of passes.
The Capping step has two paths:
ON_PASSED: The user is allowed to continue through the capped path
ON_CAPPED: The user has reached the configured limit and is routed through the alternative path
Capping and Entry Rules
Capping works independently from the frequency settings configured in Entry Rules.
Entry Rules > Capping Options determine how often a user can enter the Journey
Capping > User Eligibility Type determines how often a user can pass through that specific Capping step
A user can therefore be eligible to enter a Journey while still being capped at a specific point within the Journey.
Add the Capping step
In Journey Builder:
Select Add Step where the capping rule should apply.
Under Branch, select Capping.
Select Add.
The Capping step is added with the ON_PASSED and ON_CAPPED paths.
Configure the User Eligibility Type
Select the Capping step to open the Capping Details panel.
Under User Eligibility Type, select one of the following options:
One Time
Multiple Times
One Time
Select One Time when each user should be allowed to pass through the Capping step only once.
The first time the user reaches the step, the user follows ON_PASSED.
If the same user reaches the Capping step again, the user follows ON_CAPPED instead.
When One Time is selected, the following fields are not displayed:
Lock Duration
Entry Capping
Multiple Times
Select Multiple Times when users should be allowed to pass through ON_PASSED more than once.
The number and frequency of eligible passes are controlled by the configuration below.
Configure the capping limits
When Multiple Times is selected, configure the following options:
Lock Duration
Defines how long a user must wait after an eligible pass before they can pass through ON_PASSED again.
If the user reaches the Capping step during the lock duration, the user follows ON_CAPPED.
For example, if the Lock Duration is set to 24 hours, a user who passes through ON_PASSED cannot pass through the same path again for 24 hours.
Entry Capping
Defines the maximum number of times a user can pass through ON_PASSED.
For example, an Entry Capping value of 3 allows a user to pass through ON_PASSED up to three times within the applicable period.
After reaching the configured limit, subsequent attempts follow ON_CAPPED.
Specify a capping time period
Enable this option to apply the Entry Capping limit within a recurring period.
When the configured period resets, the user's Entry Capping count is reset and the user can become eligible to pass through ON_PASSED again.
Capping Time Period
Define how often the Entry Capping limit should reset.
The configured period determines the timeframe in which the Entry Capping limit applies.
Configure the capping paths
After configuring the Capping step, connect the subsequent Journey steps to the appropriate paths.
ON_PASSED
Use this path for users who are eligible to continue through the capped point.
For example, connect it to a message or another Journey action.
ON_CAPPED
Use this path for users who have reached the configured capping limit.
For example, connect it to an alternative message, another Journey action, or the end of the Journey.
View capping step statistics
Capping performance can be reviewed from Journey Analytics.
From the Journey list, select the View icon in the Action column to open the Journey Analytics page.
For a Capping step, the following metrics are available:
Entry Count
Number of users who entered the Capping step
Pass
Number of users who passed the capping rule and continued through ON_PASSED
Block
Number of users who reached the capping limit and continued through ON_CAPPED
Last updated
Was this helpful?