|184.108.40.206.5 Multiple conditions, parenthesis and condition evaluation order << 220.127.116.11 >> 18.104.22.168.1 Item code|
22.214.171.124 Product targeting with condition treeSome campaign types use product targeting based on conditions (or "rules"). Some of such campaign types can have multiple condition trees, some may only have one. These campaign types are not supported if the webshop-platform is not in use.
If a campaign has a condition tree which can be matched by multiple different products, and not just one product or its option choices, the product list of the campaign can not be shown automatically in the shop. In order to be able to show product lists automatically, every condition tree of the campaign must be either single "product code"-condition or single "product list"-condition, and that condition must not have negation enabled. For example, if product pack campaign's all product slots are with single "product code"-condition, the shop can show automatically a view in which the user can, when necessary, choose a product option, and then add the whole campaign pack at once to the shopping cart.
Condition / rule - A single condition which has to be true for the currently handled product or products to belong to the campaign.
Condition/targeting/rule tree - A tree-like structure of nested or parallel conditions, whose coming true in whole defines what or which products can belong to the campaign.
Negation / inverted - Switching the logic to work in the opposite way, so yes/is true/applies will become no/false/doesn't apply and vice versa.
Generic properties of rules
Negation Almost any condition can be switched to work in the opposite way; if a negation is enabled, the condition that would otherwise have been true will be false, and correspondingly condition that would otherwise have been false will be true. This is usually presented so that along the condition, there is a separate choice which has, for example, "is" and "is not", or "any of the products" and "none of the products".
Price rule Every condition can have its own price rule. If a condition tree branch that is true has multiple price rules in effect, the innermost/deepest price rule will be used. If the condition tree evaluation does not provide any applicable price rules, either a generic price rule in the campaign or some default functionality of the campaign type will be used, or the price is not changed at all. For example, in "buy X get Y" campaigns the built-in rule is "0" (i.e. for free). The price rule can be set by clicking on an icon like this
|Picture 8.18 : Set pricerule|
Multiple conditions apply simultaneously If multiple conditions are true under the same "product iterator", and thus it is possible that multiple price rules are in effect simultaneously, some price rule will be chosen, usually the first/topmost.
In many cases the same functionality can be achieved with multiple different condition trees (or even using different campaign types). The examples below do not consider this, and the shown examples are possibly to just one understandable way to make the intended product targeting. The examples can be used as a base for creating product targetings intended to work in the explained way.
Certain product or any of its option choices, or the specific option choice of the specific product is valid for the campaign:
|Picture 8.19 : Example product or its option choices|
A list of product item codes. Any of the listed products, or any option choice of any of the listed products is valid for the campaign:
|Picture 8.20 : Example procuct list|
Alternative products (e.g. for a buy 2 get 3 -campaign): product 0001, product 0002, or a product from group /golf/bags (or any of its subgroups):
|Picture 8.21 : Example alternatives and a product group|
Alternative products (e.g. for a buy 2 get 3 -campaign): product 0001, product 0002, or a product from group /golf/bags (or any of its subgroups). In addition the product must have price less than 25€.
|Picture 8.22 : Example alternatives and a product group, and price|
Alternative products and one alternative being a pair of products: product "pants", product "shirt", or products "socks" and "T-shirt" together.
|Picture 8.23 : Example pair of products|
Couple product groups, excluding certain products: product from group "/clothing/shirts" or from group "/clothing/pants", but not from group "/clothing/pants/suit pants".
|Picture 8.24 : Example alternatives excluding certain choices|
Descriptions of the conditions/rules
126.96.36.199.1 Item code
188.8.131.52.2 Product list
184.108.40.206.3 Product group
220.127.116.11.4 Product field
18.104.22.168.5 Product type
22.214.171.124.6 Product iterator
126.96.36.199.7 Logic operator