Documentation

Each Data Governance Rule in Improvado consists of several fields that must be filled in. Below you can see a description of each field:

Rule Name

A short name for the rule. This will be displayed on the dashboard.

‍Example: Campaign is at or above 10% CTR.

Rule Description

A brief explanation of what the rule does and how it should be interpreted.‍

Example: Campaign is at or above 10% CTR.

Platform

The source of the data. Choose from the available sources or specify your own if not listed.

Table Name

The name of the table from which the data will be pulled. Leave blank if unsure, AI will automatically select an appropriate table.

Violation If

The condition under which the rule is considered violated. The main logic and formulas should be located here. In most cases, you should think of it as the opposite of the description.‍

Example: Click-through rate in an ad set is less than 10%.

Action Required

The action to be taken if the rule is violated.‍

Example: Disable the campaign if CTR is less than 10%.

Filters

Additional logic to limit the data to which the rule applies. Note that filters should not contain the logic of the rule itself. All rule logic must be defined in the Description and Violation If fields.‍

Example: ```spend > 0 AND campaign_status = ‘Active’.```

Group By

The granularity of the data. Define the level at which the rule should be applied. The following sequence must be followed:

• account_id and account_name are always required.
• If you want to deep granularity of the rule:
  • For account-level: "account_id, account_name"
  • For campaign-level: "account_id, account_name, campaign_id, campaign_name"
  • For ad set-level: "account_id, account_name, campaign_id, campaign_name, adset_id, adset_name"
  • For ad-level: "account_id, account_name, campaign_id, campaign_name, adset_id, adset_name, ad_id, ad_name"

Compliance Categories

Choose the relevant compliance category for the rule.

Available categories:

• Taxonomy Compliance: Ensures adherence to data classification standards. It verifies that the data is categorized correctly according to predefined taxonomies, ensuring consistency and clarity across datasets.
• Metric Compliance: Validates the accuracy and consistency of metrics. This ensures that all metrics are measured and reported correctly, aligning with the standards set by the organization.
• Guidelines Compliance: Aligns with predefined guidelines and policies. This ensures that all data practices comply with internal guidelines and external regulations, maintaining integrity and trustworthiness.

Business Category

Select the relevant business category.

Available categories:

• Efficiency: Focuses on operational performance. Rules in this category aim to optimize processes and resource utilization, enhancing overall efficiency.
• Brand: Pertains to brand-related metrics and standards. Rules here ensure that all activities align with brand guidelines and contribute positively to brand value.
• Productivity: Targets productivity metrics and improvements. This category focuses on enhancing the productivity of teams and processes, ensuring better output and performance.

Severity

The importance level of the rule.‍

Options: High, Medium, Low.

Run Frequency

This parameter specifies how often a rule will be executed to check for any violations that trigger notifications. It can be set to run at various intervals, including hourly, daily, or weekly.

Example: If the Run Frequency is set to hourly, the rule will run every hour. If any changes in the data meet the specified conditions during these hourly checks, the user will receive a notification. Similarly, if set to daily, the rule will run once every day, and if set to weekly, it will run once every week, sending notifications if the conditions are met during these intervals.

Important to consider: The data extraction parameters must be set accordingly to match the Run Frequency field. If the frequency is set to hourly, data extraction should also be performed hourly. If set to daily, data extraction should be daily, and similarly, if set to weekly, data extraction should be weekly. This alignment ensures that the rule checks are based on the most current data available for the specified interval. (link to documentation about it).

Rule Owner

The individual responsible for enforcing the rule. They will receive notifications related to the rule.

‍Example: test.account@improvado.io

Rule Status

By default, it is set to Enabled to ensure visibility on the dashboard and active notifications. Switch to Disabled to remove this rule from your dashboard and stop receiving notifications about the specific rule.