Skip to main content

Why is the ordering of the Ruleset important?

The system checks the Criteria from top to bottom and if the ordering is not configured correctly, the wrong rule might take precedence.

Karan Saraf avatar
Written by Karan Saraf
Updated over a year ago

Ordering in Rulesets is vital for the automation to run according to the desired configuration. In Rulesets, you're provided with a toggle on the side of the Ruleset to move the rule up/down. By using the toggle, you can move the rule to the place you consider to be fit. To get a better understanding of how & why ordering is important, here is an example:

Consider a situation where the first rule in order says Clicks β‰₯ 100 and Orders = 0. This is the first rule in the order and will get triggered when the criteria becomes true as the system starts by checking the rules from top to bottom.

Suppose there's a second rule in order where the criteria is Clicks β‰₯ 150 and Orders = 0. Here, the attribute (Clicks & Orders) are the same and so the only way to determine which rule will take place is by the Values given to them. Orders is the same (Attribute & Value) between both rules and hence won't be the deciding factor. In Clicks, however, more than 100 clicks will trigger the Action in the rule.

Whatever number is greater than 150 will be greater than 100 and so no matter the number of clicks, the first rule's Action will get triggered because the ordering was not correct.

To rectify this, the rule with Clicks greater than 150 should be placed above Clicks greater than 100 for accurate results.

Did this answer your question?