- AdBOOST Rules
Rule system is an inseparable and core part of AdBOOST, which you will encouter many times during his usage. From the moment, when your items enter the AdBOOST for a first time (as a part of the data feed during its first processing) until they leave it towards target advertising network, they are filtered and modified multiple times. To ensure that you can segment your items and modify them to fit your needs, we use rules. In later parts of this guide, you will find out, where you can find the rules and most important, how to use them and get the most out of them.
Where to find the rules
Here is the comprehensive list of all rules locations:
- Feed filter rules
- Feed editor rules
- Product Group assign rules
- Keyword Pattern filter rules
- Ad Pattern filter rules
- Export filter rules
- Export CPC edit rules
- Notifications setup
There are two types of rules:
- Filter rules - can be found as a single container and consist of predicates and conditions
- Modifier rules - can be found as a set of orderable containers that consist of filter predicates and modifier actions
Example 1: Filter rule with two predicates, first with two conditions, second with one condition
Example 2: Two modifier rules. First with one predicate, two conditions and one actions, second with no predicates and two actions.
- If you leave predicate part of any rule empty, it will match all items
- Modifier rules, same as rule actions are orderable - Drag&Drop by handle
- Rules are applied sequentially and order matters. If you modify some of item properties in one rule, all following rules will show only informative number of covered items but correct result of all previous rule actions applied in sequential order. See the screen below
This section describes individual parts of every rule, starting at top-level and increasing granularity.
Every rule predicate is a collection of conditions with following structure:
OPERAND - OPERATOR - VALUE
Predicates, same as conditions can be combined by logical operators AND (all conditions are met) and OR (at least one condition is met).
- OPERAND - feed property, that can either exist in feed or have been created as a virtual property in Feed Schema Settings. These properties can be numeric - properties in numeric1, numeric2 or other_numeric categories, or generic - every other feed property
- OPERATOR - set of operations that differ for numeric and generic feed properties
VALUE - case-insensitive text value that differs with operator because there are three types of them:
Operator without value - Not empty
Basic operators - =, !=, >, <, >=, <=, Starts with, Ends with, Contains, Does not contain, Regex
- Batch operators - Contains any, Does not contain any
Actions can be found only in modifier rules because they change values of properties for items that fit the conditions of one specific modifier rule.
Structure of actions is very simmilar to the one of predicates:
OPERAND - OPERATOR - VALUE/PARAMETERS
OPERAND - feed property, that can either exist in feed or have been created as a virtual property in Feed Schema Settings.
OPERATOR - set of operations summorted by AdBOOST
- VALUE/PARAMS - this property differs for every operator:
Find one string and replace it with another
Replace property value with static content or with value of other property
Find string in value and remove everything on its left/right including/without itself
Same as replace but instead of string to find, you can choose from most frequently used ready-made regular expressions or provide your own
You can choose from most frequently used ready-made regular expressions that remove some kind of value-unit pairs from your product properties or provide your own
Set capitalization policy
Make all letters in property value uppercase
If the selected property is numeric, round it’s value to fixed decimal places (usefull after math operations)
Take one property, apply math operation to it and save it as a value of another property
Remove all listed strings from value
Remove color names in selected language
Remove any HTML tags (ussualy enclosed in <> tags)
Create unique hash from one property value and save it as a value of another property