Learn how to configure conditions and create nested condition groups for validation rules.
Conditions let you define which requirements have to be fulfilled for the validation rule to run. In other words, it tells Accutics Val what specific cases should be included in the runs.
Use case: As an agency, you may have multiple accounts in your source. You can use conditions to limit the validation rule to validate specific accounts.
The settings for a condition vary slightly depending on the type of validation rule and source. You can define status conditions and/or set an advanced logic.
Status and date conditions
* status
It lets you define whether to run the validation rule based on the status of the campaign, ad group, etc.
For each of them, you are also able to define conditions based on their start and end dates.
The status options include:
- Enabled
- Paused
- Removed
The start and end date can be:
- In the past
- In the future
- In the past or future
* stands for anything like Campaign, Ad group, etc.
The default settings are: * status: Enabled * start date: In the past or future * end date: In the future
Effective status
For some of the sources, you’ll also see a ‘Use effective status’ check box. Whether this option is checked or not will affect how Accutics run the validation rule.
Simple status condition (Unchecked)
Deselecting the use of effective status, means that Accutics only take the status of the element into consideration.
That is, if you are creating a validation rule for a Google ads, it is the status of the Ad only that counts - regardless of the status of higher levels elements like Ad group and Campaign.
Example
Setting a simple status condition `Enabled´ for an Ad means that the validation will run for every Ad that has the status `Enabled´. Even if the Ad group or Campaign is paused or removed.
Effective status condition (Checked)
Using the effective status means that Accutics will calculate a status based on the status of elements at higher level.
This happens because ad platforms, like Google ads, have a hierarchical structure, where the status of the campaign affects the effective status of lower elements such as the Ad groups and Ads within in.
Example
Setting an effective status condition `Enabled´ for an Ad means that the rule only validates Ads that are enabled and where all the above elements are enabled too. This is the only scenario where an Ad has an effective `Enabled´ status. In Google ads, these Ads would also be shown as `Eligible´.
Indeed, if you pause or remove a Campaign, any Ad Group contained in it would inherit the same status, and so would any lower levels.
Dive deeper into how statuses at different levels affect each other in Google Ads here.
Exclude creatives synced from CM360
When configuring a validation rule for a DV360 source, you can apply a condition to exclude CM360-hosted creatives.
Synced creatives cannot be edited in DV360. Hence, we introduced this feature to exclude such creatives from the validation rule and avoid marking them as errors. Instead, set up a Campaign Manager 360 source and validate your placements on their platform.
To apply it, simply check the `Exclude CM360-hosted creatives´ box
Advanced conditions
This section lets you define advanced conditions using comparison/logical expressions.
To define an advanced condition:
- Choose the scope of the condition
Define whether ALL the conditions have to be present for the validation to be performed, or if just ANY condition is sufficient.
- Select the parameter to be evaluated
- Define the comparison operator
- Provide a value
You can edit and delete the expression by clicking on the expression.
You can add more expressions by clicking `Add expression´ to create multiple conditions.
Multiple conditions - Grouping
You can build conditions that contain multiple sub-conditions and combine them into groups.
To create a group:
- Create an expression
- Click on it > Click on the group icon
- `Add expression´ within the group
You can keep creating groups and nesting them within other groups.
Each group can be evaluated with its own ANY or ALL logic. This lets you define a condition that uses different scopes.
By clicking on the meatball menu, you can manage the group:
- move up
- move down
- duplicate
- ungroup
- delete