You can filter participants in your customer journeys based on whether they match or don't match specific criteria.
What is the criteria filter node?
The criteria filter node lets you split recipients into two groups, ones that meet the criteria you specify (following the success path), and ones that don’t (following the fail path).
The criteria builder supports multiple types of values that you can build criteria with.
Make sure that the value you enter matches the value type selected. Some systems store data differently than others, so make sure to check the field types in the system the data is coming from.
Currently formulas can only be entered (as free text) on the left or right hand side of an equality operator when the ‘formula’ type is selected. A handy formula picker will appear when you click into a formula field, to help you write formula expressions.
The following formulas and arguments are currently supported:
DateAdd("interval", number, instant)
- Returns the result of adding the number of intervals to the given instant (e.g. add 5 days from now)
interval— SECONDS, MINUTES, HOURS, DAYS
number— The number of intervals to add (e.g. 5)
instant— The instant to add to (a moment in time)
- Returns the current datetime
In our above example, to use a formula that specifies ‘add 5 days from now’ you would enter:
DateAdd("DAYS", 5, NOW())
- Returns the
instantthe experience started (when the flow triggers for an individual recipient)
field option allows you to reference data in fields (like a merge field). You can start typing to search available fields to select.
For example, if
City was a field in your system of record, you could use the field type and add a value (for instance,
Sydney) to filter recipients based on whether their city is Sydney or not.
Boolean value type can be either true or false.
A string type is just a normal text string - using the field type example above, in the LHS you may have the field
City defined as above, in the RHS of the builder you might put
Sydney as a string value.
A simple integer, e.g. 1234.
Offer expiry example
As an example, we can use the criteria filter to create an offer expiry period in the flow.
When a recipient replies to the original outbound SMS, the reply will come back into Pendula, and the split will check whether it was received before the expiry - i.e. was it received 2 days before or 2 days after the original messages sent?
In the criteria builder:
LHS Select type =
Enter the formula =
DateAdd ("DAYS", 2, ExperienceStart())
(2 days from when the experience started)
Select operator =
RHS Select type =
Enter the formula
Essentially this criteria checks that the flow was triggered less than 2 days ago and the recipient has replied, they can continue through the the ‘success’ path of the split.