Handling conflicts in enforcement conditions

Privacy principles

To ensure your business’s data activation complies with relevant policies and regulations and guards against data leaks caused by user error or misconfiguration, we built Consent Integrations with strict adherence to privacy by design and privacy by default principles. These principles require that data processing and activation are allowed only when explicit consent or clear conditions are met.

How Consent Integrations handles conflicts in enforcement conditions

• When at least one Consent Integration or exemption is active: No data processing is allowed without a specific signal from your consent management platform (CMP).

• When two or more enforcement rules overlap for integrations: Tealium iQ will not load, and no tags will fire.

• Exemptions are allowed to overlap: If a single Integration overlaps with any number of Exemptions, the Integration is enforced and the Exemptions disregarded.

In ambiguous scenarios, such as when two integrations present and both of their enforcement rules evaluate to true, Consent Integrations withhold data processing and activation to protect against potential data leaks. This may result in the loss of data from blocked tags, but it is a precautionary measure to mitigate the risk of data leaks.

The following table shows how Consent Integrations handles conflicts depending on the number of active exemptions and integrations: