About load rules

A load rule determines when a tag loads on your site or app. A load rule is one or more conditions that are based on the values in the data layer. For example, a load rule condition that identifies your search page might be:

page_type equals search

The default load rule is All Pages, which contains no conditions and is always true.

The following components use load rules:

• Tags
• Consent manager
• Currency converter extension
• Data validation extension
• Channel extension

Boolean logic

Multiple conditions can be combined using boolean logic to form more complex load rules. For example, to load a tag on the search page, but only when the user is not logged in, the load rule conditions might be:

page_type equals search
AND
is_logged_in equals 1

This complex logic can be combined into a single rule or created as two rules and then enforced using the Match All Rules setting. See how to assign load rules to a tag.

AND logic

Use AND logic to create a rule that is true only when all of the conditions evaluate to true. For example, a rule that combines 3 conditions using AND logic evaluates to true only if each individual condition also evaluates to true. If any of the conditions evaluate to false, then the entire rule also evaluates to false.

OR logic

Use OR logic to create a rule that is true when any of the conditions evaluate to true. For example, a rule that combines 3 conditions using OR logic evaluates to true if any of the individual conditions also evaluate to true. A rule that uses OR logic only evaluates to false if all of the individual conditions also evaluate to false.

List of comparison operators

Each rule condition uses a comparison operator and a variable from the data layer. The following table lists the available comparison operators that can be used in load rule conditions. For operators that include (ignore case) in the name, the text value of the variable is converted to lowercase before the comparison.

Load rules and consent enforcement

While it is possible to add consent conditions into existing load rules, your use case may require you to use Consent Integrations for more reliable consent enforcement.

Consent Integrations is a Tealium iQ Management feature that allows organizations to easily incorporate consent enforcement into their client-side data activation processes. Unlike load rules, which control when tags fire based on conditions such as page views or user interactions, Consent Integrations focus exclusively on ensuring user consent is respected during data collection and processing activities. For more information, see Consent Integrations.

Using load rules for consent enforcement may result in the following issues:

• Missed initial events
• Data leaks
• Difficulty completely triggering server-side tools

Additionally, you can fire tags without respecting load rules using an optional array of tag IDs (uid_array) in track calls. When using load rules for consent enforcement together with the uid_array parameter, consent conditions are ignored along with the rest of the rule.

For more information about load rules and Consent Integrations, see Beyond Load Rules: Leveraging Consent Integrations for Compliance.