What is a Ruleset?

Vrio Analytics is extremely customizable through filtering and pivot table style reporting. But when there is a need to drill in, include certain components & exclude others, this is where rulesets come in.

Rulesets allow a user to create a very specific cohort of customer, orders, transactions to analyze.

Rulesets use defined field operator relationship to determine what is included in the cohort. These can be created from:

• Configuration settings such as Campaign, Offer, Item, etc
• Marketing Sources: Network, Source, UTM Parameters, etc
• Customer Data - AOV, CLV, Revenue, etc
• Transactional Data - Cycle, attempt, Add On, Upsell, etc
• Payment Data - Discounts Used, Payment Methods used, Processor, etc

Within every report, you can use Rulesets. Save Rulesets for reuse.

Business Use Case

Use Case 1: I want to see only Initial Offers. I name my offers "Brand A Initial" and "Brand A Upsell". I am going to create a ruleset where Offer Name 'contains' Initial.

Use Case 2: I have an issue and need to isolate anyone from Campaign A who are on billing cycle 2+ and used any discount code that starts with "JULY". I am going to create a ruleset where Campaign = A ; Transaction Cycle greater than 2 ; Discount Code starts with JULY. I also want all these definitions to be true.

Common Rulesets

• Traffic Source views
• Campaign grouping views

Create a Ruleset

To create a ruleset, select the report that you wish to use.

1. Navigate to the + next to the Ruleset dropdown.
2. Choose Field - this will be the dimension that you want to create a ruleset around. Note - Multiple dimensions can be used to create your ruleset.
3. Choose the Operator - defined below
4. Set the values that you want used in this ruleset. Depending on the Field, either a drop down list will populate or a text field. For text fields use a "," comma when you have finished defining your value.
5. Click Add Rule
6. Repeat this process with any combination of Fields operator values until Ruleset / cohort is defined

Operators will determine what the ruleset should be limited to:

Lastly, define how restrictive the ruleset logic should be:

Any Definition Can Be True

• Any of the defined definitions can be true.
• Any definitions not defined will be removed from the dataset.
• NOT ALL definitions have to be present for a customer to be in this ruleset.

All Definitions Must Be True

• All defined definitions must be present to be in this ruleset.
• Any definitions not defined will be removed from the dataset.

Pay Attention

If you have Campaign Name contains Main, and it says All Definitions Must Be True the data will only show you any customer that is in ALL campaigns that contain Main in the name.

Use Cases

Example 1: A ruleset has discount code ABC and Transaction Cycle = 2.

When Any Definitions Can be True is set, customers with cycle 1 using discount code ABC can be in this ruleset. Similarly, customers on transaction cycle 2 without discount code ABC can be in this ruleset.

When All Definitions Must be True is set, customers with cycle 1 using discount code ABC will not be in this ruleset. Only customers on cycle 2 with a discount code of ABC will be in this Ruleset.

Save a Ruleset

To Save a Ruleset, simply navigate to the right corner and select "Options".

Once the ruleset has a name, it will appear in the dropdown "Load Ruleset" with all other saved Rulesets:

Validation Tips

Create your ruleset, then use the Dimensions included/excluded in your ruleset across a large date range. If you expect something to be excluded that you see in your report, double check the definitions are configured correctly.

Applying a Ruleset to an Alert or Schedule

When creating an alert, there is the option to select Ruleset. Choose the ruleset as the alert filter and create the alert as normal.

See more on alerts here.

See it in Action