Skip to main content

Set up Conditional Firing Using LaunchPad

IAB TCF, IAB USP, and Google Consent Mode may not cover all of the third-party and first-party tags that collect personal data on your site (For example: Pinterest share buttons, Embedded Twitter feeds, or Custom Trackers). In order to allow vendors to only collect personal data based on the user's consent state, you can set up Conditional Firing Logic.

Defining where your non-IAB vendors/tags are being fired from is a good place to start. Depending on your set up we cover multiple scenarios.

Hard-coded tags

In case the tags that you need to control are hard coded on your site, you can use Content Tags in combination with tag loading rules.

Tags fired Through a Tag management solution

In case the tags that you need to control are loaded from a Tag Manager then you can use the Tag Manager Trigger integration options. Currently the following Tag Managers are supported:

Tag Loading Rules

The tag loading rules enable you to control the loading of any tag on your website based on trigger conditions. Using the tag loading rules any tag can be configured to fire on user consent or stop firing in case the user opt-out.

With tag loading rules, you can make use of the tags that you've previously configured in the Tags section. This way the setup for tag loading rules only has to be done once and can be used across multiple Privacy Manager configurations.

Procedure. Set up a Tag Loading Rule

  1. First configure the tag(s) you want to conditionally fire using a Tag Loading Rule in the Tags section.

  2. Head over to the integrations section of your LaunchPad, click New and select Tag Loading Rule.

  3. Name your Loading Rule.

    Note

    This can later be used to reference the loading rule.

  4. Click Choose a tag to begin setup to select one or multiple tags that you want to trigger using the loading rule.

  5. Click Choose a trigger to begin setup to define one or multiple trigger conditions.

Trigger Conditions

Trigger conditions when a tag should be fired. A Tag Loading Rule can have one or multiple Trigger Conditions.

There are three Trigger Types:

  • Consent: When the consent state is changed for a given vendor from the Universal Vendor List. Consent data are obtained from the Universal CMP API.

  • Event: When a certain event is emitted from the LaunchPad API.

  • URL: When there is a match on a URL regex.

Multiple trigger types can be used for a single Tag Loading Rule. A new Trigger Condition block can be added by pressing the ‘plus' button. The relation between two trigger types is always “AND” so case of multiple trigger types then all conditions will have to be true for the tag to fire. The relation between two conditions of the same type is always “OR”, so either of the conditions have to be true.

Example:

Consent: “Vendor X”

AND

URL: CONTAINS “example” OR URL: CONTAINS “demo”

In this scenario for the tag to fire between the user will need to give consent for “Vendor X” AND the sire URL should contain “example” OR “demo”.

Consent Trigger Condition

Use the Consent Trigger Condition to ensure that the tag is only fired when there is adequate consent. Select third-party vendors and/or publisher purposes.

Tag Manager Triggers

Conditional firing is crucial to ensure privacy compliance even within the IAB TCF.

Data collection is not allowed until the end-user gives explicit consent to have their data collected and for TCF the consent has to be given specifically to the vendor in question.

In order to help you, we’ve automated the technical part for Google Tag Manager, Adobe Launch, and Tealium IQ so that no development resources are needed to set everything up.

By following our Google Tag Manager guide, you’ll be able to take care of the less technical part that is needed for conditional firing.

In this section: