Understanding campaign evaluation
Understanding how Talon.One executes one or more campaigns is important to help you build advanced promotion use cases.
Evaluating promotion campaigns
The general evaluation order of promotion campaigns is:
- Information is fetched from Catalogs.
- Campaigns are evaluated one by one
according to their evaluation tree.
- Inside each campaign, cart item filters are evaluated in their order of appearance in the Campaign Manager.
- The rules are evaluated in their order of appearance in the Campaign Manager.
- Inside each rule, each condition and effect is also checked and applied in order of appearance.
- The effects are returned via the Integration API.
Evaluating strikethrough campaigns
The general evaluation order of strikethrough campaigns is:
- Talon.One monitors a specific set of events happening in cart item catalogs, or in campaigns containing strikethrough rules.
- When such an event is triggered, Talon.One evaluates all active campaigns with strikethrough rules according to their evaluation tree.
- Talon.One sends a request to the URLs set in your Strikethrough pricing notifications.
Evaluating cart item filters
To increase performance, the Rule Engine evaluates cart item filters only in the following cases:
A condition referencing a cart item filter is about to be evaluated or a valid effect referencing a cart item filter is going to be applied.
In this case, only the cart item filter referenced by the condition or effect is evaluated.
A discount effect or an update effect is about to be evaluated.
In this case, the Rule Engine evaluates from top to bottom all cart item filters that haven't yet been evaluated.
The campaign rules are evaluated by the Rule Engine from top to bottom as they appear in the Rule Builder section.
Before evaluating the campaign rules, the Rule Engine collects any customer profile data using the profile's integration ID, as that data may be required to evaluate the rules.
All conditions of a rule are evaluated and all its effects are applied before evaluating the next rule.
The conditions of each rule are evaluated by the Rule Engine from top to bottom as they appear in the rule.
All the conditions of the same rule are evaluated before evaluating the effects.
The Rule Engine evaluates whether the effects of each rule can be applied. It does it based on the order in which the effects appear in the rule, from top to bottom.
Each valid effect is added to the array of effects of the customer session response as the Rule Engines evaluates if it can be applied, so the Rule Engine takes the effect into account when evaluating if the following effects can be applied.
Any existing campaign budgets are checked when evaluating if the effects that impact them can be applied.
For this example, consider a campaign with 3 cart item filters and 2 rules. The first rule has 2 conditions and 1 effect, and the second rule has 1 condition and 2 effects.
|Cart item filters||Rule 1||Rule 2|
Also consider the following:
- Filter 2 is referenced by Condition 2 in Rule 1.
- Filter 3 is referenced by Effect 2 in Rule 2.
- Effect 1 in Rule 2 is a discount effect. The other effects are coupon effects.
The Rule Engine evaluates the cart item filters and rule conditions, and applies the effects, in the following order:
Filter 2 is evaluated when the condition that references it is about to be evaluated.
Filter 1 and Filter 3 are evaluated when the Rule engine is about to evaluate if the discount effect can be applied.