Condition nodes explained
This type of nodes allows users to define the circumstances that need to exist so the workflow could continue. The conditions can be divided into two groups: customer-related and general.
- Conditions cannot be used as the starting point of the workflow.
- Conditions are not tracked in workflows by default. If you want to have statistics or include information about the movement of a customer to a specific condition on a profile, you need to turn this option on in the settings of a condition.
- All condition nodes allow for more than one path to let users define separate paths for the scenarios when the conditions are met or not.
This category of nodes is recommended to be used in the customer-oriented workflow. Users can define the type of audience that proceeds between the steps in the workflow or check whether they performed a specific activity.
- Profile Filter
- Event Filter
This category of nodes allows to prepare alternative paths a workflow can go when conditions are not met or if you want to test some solutions such as effectiveness of templates.
- ABx Test
- Metric Filter
- Event Filter
"ABx Test" node
This node branches paths according to the allocation assumptions set in the condition
"Profile Filter" node
It lets through customers in the workflow who met conditions defined in the filter
"Metric Filter" node
It branches scenario into paths that match and not match results of the metrics
"Event Filter" node
It lets customers through in the workflow if they perform a defined activity
"Business Filter" node
It lets a journey continue if a certain set of business events co-occur