Exclusions
Definition
The same way you set rules in your properties, you can define exclusion rules.
If a condition's criteria are met in an event, then the event is excluded from further processing.
Condition blocks are read from top to bottom. The program stops on the first block of conditions validated by the event.
The excluded event will be identified with the following naming exclusion.eventname, and will be visible in the excluded events analysis. An event excluded by your configuration (Data Manager v2 / Exclusion / Not declared in the Data Model/ Privacy) is added to your bill, on the contrary Piano Analytics' default exclusions (Robots / Closed sites / Technical exclusions/ Business exclusion (duplicated order id etc.)) are not taken into account in your bills.
We will use the the label of the condition block to specify the exclusion cause.
Creation
We advise you to check our section dedicated to rule creation in properties before setting up an exclusion rule.
Creating an exclusion rule is similar to an exclusion rule but it holds 2 major differences:
The property being worked is the organisation or the site
The only action you can rely on is the exclusion
To set up an exclusion rule, please go to Data Management > Configurations > Exclusions and select your rule's perimeter to define its criteria. Once your rule is set you will only have to click on Save and Deploy to let it be taken into account by 20 minutes following the click.
Application perimeter
Your exclusion rule can be set on 3 different scopes:
By default exclusion
The rule is applied to the whole organisation.
Site exclusion
The rule is applied to a specific site.
Importing the default rule is not yet available.
Group of site exclusion
As soon as you create a rule on several sites, you must create a Data Management group of site.
Importing the default rule is not yet available.
Tests
You can rely on the right panel to try out if your set of parameters results in an event exclusion.
Deletion
You can delete an exclusion rule from your organisation Data Model.
The ones coming from Data Manager v2 are placed before Delta processing and therefore cannot be deleted directly from the Data Model.