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. This article will discuss the configuring of reject actions.

Reject Actions

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.

Did this answer your question?