Using Consent & Reject Actions

Sourcepoint provides the ability to trigger additional JavaScript code based upon what the user elects to provide consent for personal information or instead elects to reject the use of personal information. Sourcepoint refers to these actions as consent and reject action, and they can be configured within the Sourcepoint UI. The actions can be triggered on a vendor-by-vendor basis or on a purpose-by-purpose basis.

To configure a consent action, navigate to the vendor list you want to use in the user interface. The vendor list can be accessed from the Consent tab in the Sourcepoint UI.

Click on the vendor list you want. Then select the vendor or purpose that you want to fire the JavaScript for. This will open up the window where you can configure consent actions.

Once the window is open click on the "Consent Actions" link and you will see a screen similar to the screenshot below.

There are three options for configuring consent actions.

  1. Custom JavaScript

  2. Google Tag Manager

  3. Inline URL

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.

The Google Tag Manager option enables you to trigger an 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.

To configure a reject action, navigate to the vendor list you want to use in the user interface. The vendor list can be accessed from the Consent tab in the Sourcepoint UI.

Click on the vendor list you want. Then select the vendor or purpose that you want to fire the JavaScript for. This will open up the window where you can configure consent actions.

Once the window is open click on the "Reject Actions" link and you will see a screen similar to the screenshot below.

Unlike the consent actions there is currently only the option of firing custom javascript for a reject action. 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.