Getting Started in the UI
Reporting

Using Consent & Reject Actions

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 now available for use on TCFv2 vendor lists. For more on using consent and reject actions in TCFv2, click here.

How do I access consent and reject actions?

Step 1 - Access Vendor Lists

Each piece of consent-related legislation has its own vendor list. For example, CCPA will have its own vendor list(s) and GDPR (TCFv1) will have its own vendor list(s). To apply a custom consent and/or reject action to a vendor or purpose/category, click on the appropriate vendor list section.

In this example, we'll use GDPR (TCFv1).

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 Personalisation (purpose).

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

Consent Actions

There are three options for configuring consent actions:

  1. Custom JavaScript

  2. Google Tag Manager

  3. Inline URL

Custom JavaScript

The "Custom JavaScript" option will 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. For example, a variable of myVar that has global scope should be referenced as window.myVar in the "Custom JavaScript" section. The consent action can be used to set a cookie for local storage of the consent action to be leveraged on future page views.

Google Tag Manager

The Google Tag Manager option enables 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

The last option is using the "Inline URL" option 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.

Reject Actions

There is only one option for configuring a reject action on GDPR (TCFv1) and CCPA vendor lists:

  1. Custom Javascript

Custom Javascript

The "Custom JavaScript" option will 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. For example, a variable of myVar that has global scope should be referenced as window.myVar in the "Custom JavaScript" section. The consent action can be used to set a cookie for local storage of the consent action to be leveraged on future page views.