Skip to main content
All CollectionsAudits
Applying Rules to Audits and Journeys
Applying Rules to Audits and Journeys
Luiza Gircoveanu avatar
Written by Luiza Gircoveanu
Updated over a week ago


A Rule applied to an Audit or Journey helps you validate that your data is collecting as expected. While your account may show dozens or hundreds of rules defined, they must be applied to specific Audits or Journeys for them to be useful.

The edit screen for an Audit or Journey has a tab for assigning rules. In Journeys, the tab is called Journey Rules, for Audits, it is called "Rules".

Applying Rules to Audits

To assign Rules to a new web Audit that you are creating, you must click the Standards button at the bottom of the edit screen. Then click on the Tag &Variables Rules tab. If you are editing an already existing Audit, the Rules tab is already present at the top of the screen.

Assign or remove rules from the Audit in the Rules tab.

Apply rules that you want to run on this Audit by clicking "assign"

If you have labeled your rules, you can add multiple rules at the same time by using labels.

Create a Rule on the fly without leaving your Audit setup. When you save the new Rule, it will be added to the Audit and saved in the Rule Library.

ObservePoint makes it easy to create Rules based on data that is found during a previous Audit. In your Audit, drill down to the page-level details (you can do this by selecting any of the URLs found on almost all Audit reports). Once there, select the Tags tab, find the tag you would like to build a rule out of, and select Create Rule. This will bring up a modal, which allows you to select the variables and values that you would like to include in your Rule. Rules created using this In-Audit rule creator will not have any 'If conditions' and will be applied to every page after the Audit is re-run or the rules are reprocessed.

The rules will execute only on the pages or under the conditions defined in the rule setup, if any. Rules without conditions defined execute on every page. Any changes made to a rule which existed on the Audit before its last run can be re-applied to the existing data without re-running the Audit. After an Audit runs, you can also apply new rules to the Audit and select Reprocess Rules to test the Audit's results against the rules' conditions. Reprocessing Rules is much faster than re-running the Audit entirely, so this can save you a lot of time.

The option to reprocess rules is found on the Gear Icon inside the Audit report on the upper right corner of the screen. It only applies to rules that were applied on an Audit but have changed since it was run.

Applying Rules to Journeys

Rules can be applied to Journeys unless the rule has a URL or status code condition defined. Therefore, when applying rules to Journeys, only rules without URL or status code conditions will show in the list.

There are two places that a rule can be applied in Journeys: on a step and at the global level (Journey rule). A rule that executes on a step will succeed if the result criteria are met at any time during the step. A rule that is applied globally will succeed if the rule criteria is met at least once during the entire Journey. This is useful, especially for apps that batch tags to fire at intervals rather than on specific screens.

In most cases, you want to apply the rules at a step level. You do so by going to the Journey steps while editing the Journey or you can go to the Journey report and create a rule ad-hoc based on the results of a run by clicking the Add Rule button.

This will give you a pop-up where you can determine the rule name and select variables you want to validate. (Note: If you checkmark the variables and click "Add Rules" the rule will test for that exact variable value. So if the value is something that changes frequently you'll want to go in to customize the rule.)

Later if you have a rule that fails because it didn't have the expected value and you want to update that rule to actual value you can also do that from the Journey report. In the case below if set as expected, my rule would now check to see that on this step event6 fires not event7.

See Journey Rules Reporting for information on reading and interpreting rules in Journeys

Did this answer your question?