Rules engine

Define the rules yourself and set them in the flexible Rules Engine. Utilize the standard set of rules or, together with Proud Nerds, create new rules that suit your business case. The rules engine is used to set the trigger for personalization actions to be executed.

Section	Description
Rule stacking	Description of how to use single rules or rule condition stacking
Operators	Overview of various operators to be used
Always apply	Description of the “always apply” toggle
Priority	Each personalization rule can have a priority

Rule stacking

Rules can be stacked in the engine with AND | OR | NOT operators

This means a personalization rule can consist of multiple conditional rules which should all be valid or any of them. On top of that rules can be grouped to a group set of rules can be validated against in conjunction of another group of rules.

The set of instructions above is valid if the current date is between 4th and 8th March, or it is between the 11th and 14th but for those dates the shipping country should be specifically The Netherlands.

Operators

The rules engine has various operators that can be used, which depend on the type of data field used. Operator overview

• Numbers

  • == (equals)

  • != (is not equal)

  • < (smaller then)

  • <= (smaller than or equals)

  • > (greater then)

  • >= (greater then or equals)

  • Between

  • Not between

  • Is empty

  • Is not empty

• Texts

  • == (equals)

  • != (is not equal)

  • Is empty

  • Is not empty

  • Any in (array of values)

  • Not in (array of values)

• Active period

  • Toggle (yes / no)

• Tags

  • Some (any of selected tags)

  • All (all of selected tags)

  • None (no tag connected)

  • Count (with all mathmetical operators as numbers, used as counter on amount of tags).

Always apply

The always apply feature always makes the personalization valid and automatically applied upon loading the website.

When toggled, the rules engine is hidden.

Priority

In case multiple active and valid rules have the same action, one should get priority over the other. The priority number can be used for this.

The number input sets the sequence in which the particular rule is executed. The higher the sequencer number, the more priority the rule gets. So for example: Personalization record 1 has priority: 1000 Personalization record 2 has priority: 250 Then record 2 is executed first.