Using Consent & Reject Actions in TCFv2

Overview

Consent & Reject actions allow you to set up custom actions at the vendor or purpose/category level within a vendor list. The custom actions can be configured to fire based on a user's action to either accept (consent action) or reject (reject action) giving consent for personal information.

New and improved consent and reject actions are only available for use on TCFv2 vendor lists. For more on using consent and reject actions in TCFv1 or CCPA, click here.

How do I access consent and reject actions?

Step 1 - Access GDPR (TCFv2) Vendor Lists

Each piece of consent-related legislation has its own sets of vendor lists. For example, CCPA will have its own vendor list(s) and GDPR (TCFv2) will have its own vendor list(s). To apply our new and improved custom consent and/or reject actions, click on GDPR (TCFv2).

Step 2 - Access Vendor List

Click Edit on the vendor list.

Step 3 - Select Vendor or Purpose

Click on the vendor or purpose for which you'd like to set up a consent or reject action. In this example, we'd select Google Ad Manager (vendor) or Select Personalised Content (purpose).

In the pop up window, select either Consent Actions or Reject Actions.

Consent Actions

There are several new options available for use on consent and reject actions.

  1. Geolocation - consent actions can now be targeted to or away from specific geographic regions. For example, if you'd only like a consent action to fire in the EEA, you could set the action to fire IN EEA. If you'd like a consent action to fire everywhere but the EEA, you could set the action to fire NOT IN EEA.

  2. Execute Custom Accept Action

    1. On status change only - consent actions can now be set to only fire on status changes. When unchecked, this custom consent action will fire immediately after a user clicks consent and every pageview thereafter. When checked, this custom consent action will only fire immediately after a user clicks consent but not every pageview thereafter.

  3. Implementation Type - there are 4 implementation types that can be used when creating a custom consent action. Those implementation types are detailed below.

    1. Custom JS

    2. Google Tag Manager

    3. Inline URL

    4. Cookies (NEW)

Implementation Types

There are 4 implementation types that can be used when creating a custom consent action:

Custom JS

This option allows you to fire any code that is placed in the text field. It can also reference any globally scoped function or variable that exists on the site page. These functions and variables will likely need to be referenced from the window object.

Google Tag Manager

This option allows you to trigger a custom event that has been configured within Google Tag Manager upon the user providing consent. This event fires when a user provides consent.

Inline URL

This option allows you to fire a pixel. In cases where a SSP or DSP pixel should only be fired based upon a user's consent, the pixel can be trafficked here and fired when a users provides consent for that vendor or purpose.

Cookies (NEW)

This option allows you to set custom cookies. You can set the name, value, domain, and expiration all within the editor.

Reject Actions

There are several new options available for use on consent and reject actions.

  1. Geolocation - reject actions can now be targeted to or away from specific geographic regions. For example, if you'd only like a reject action to fire in the EEA, you could set the action to fire IN EEA. If you'd like a reject action to fire everywhere but the EEA, you could set the action to fire NOT IN EEA.

  2. Execute Custom Reject Action

    1. On Status Change Only - reject actions can now be set to only fire on status changes. When unchecked, this custom reject action will fire immediately after a user clicks consent and every pageview thereafter. When checked, this custom reject action will only fire immediately after a user clicks reject but not every pageview thereafter.

    2. When New User - reject actions can now be set to fire only when the user is new. When unchecked, this reject action will fire when the user rejects. When checked, this reject action will only fire if the user is new.

  3. Implementation Type - there are 4 implementation types that can be used when creating a custom reject action. Those implementation types are detailed below.

    1. Custom JS

    2. Google Tag Manager (NEW)

    3. Inline URL (NEW)

    4. Cookies (NEW)

Custom JS

This option allows you to fire any code that is placed in the text field. It can also reference any globally scoped function or variable that exists on the site page. These functions and variables will likely need to be referenced from the window object.

Google Tag Manager (NEW)

This option allows you to trigger a custom event that has been configured within Google Tag Manager upon the user providing consent. This event fires when a user provides consent.

Inline URL (NEW)

This option allows you to fire a pixel. In cases where a SSP or DSP pixel should only be fired based upon a user's rejection, the pixel can be trafficked here and fired when a users provides consent for that vendor or purpose.

Cookies (NEW)

This option allows you to set custom cookies. You can set the name, value, domain, and expiration all within the editor.