Permission: Vendor list - GDPR
Consent actions allow you to set up custom actions at the vendor or purpose/category level within a vendor list. A consent action is eligible to be fired if the vendor has been consented to by the end-user or utilizes legitimate interest as the legal basis. In this article, we will cover the following in regards to consent actions for GDPR TCF and GDPR Standard vendor lists:
Note: Please be aware that consent actions will not fire for AMP property types and you will receive an error. We recommend that you keep your AMP properties on a separate vendor list from other web properties and without any consent or reject actions in the vendor list.
From a GDPR TCF and GDPR Standard vendor list, click either a vendor or purpose/category.
Click Consent Actions in the subsequent modal.
Overview
In this section we will review the key aspects of the Consent Actions tab in the vendor and purpose modals.
| Field | Description |
| Geolocation |
Utilize the provided logic statement to target to or away from specific geographic regions. Examples • To only fire the consent action in the EEA + UK, you would set the action to fire IN EEA + UK. |
| On status change only |
Nested under the Execute Custom Consent Action, check this field to only fire your custom consent action immediately after an end-user clicks consent and not on any pageviews thereafter. If left unchecked, your custom consent action will immediately fire after an end-user clicks consent and on all subsequent pageviews. |
| Custom JS |
One of four implementation types that can be used when creating a custom consent action. Use the provided field to fire any input code.The code can reference any globally scoped function or variable that exists on the site's page. These functions and variables will likely need to be referenced from the window object. |
| Google Tag Manager |
One of four implementation types that can be used when creating a custom consent action. Allows you to trigger a custom event that has been configured in Google Tag Manager upon the end-user providing consent. Click here for more information. |
| Inline URL |
One of four implementation types that can be used when creating a custom consent action. Allows you to fire a pixel when an end-user provides consent. In cases where a SSP or DSP pixel should only be fired based upon an end-user's consent, the pixel can be trafficked here and fired. |
| Cookies |
One of four implementation types that can be used when creating a custom consent action. Allows you to set cookies (including the name, value, domain, and expiration) |
Add vendor tag based on consent action
A vendor tag (also referred to as a vendor pixel) is a snippet that your vendor may ask/require your organization to include in your configuration. However, it can be the case that a vendor tag should only be added to a property only after the end-user has rejected to the vendor.
Note: Before proceeding, you will need the URL for your particular vendor tag and/or opt-out pixel.
To add a vendor tag based on an end-user's consent, click Consent Actions in the modal and input the following script in the provided Custom JS field.
Note: In the provided script below, replace http://ad.somevendor.net/site/c=14674/pe=y/?param=true with the URL for your vendor tag.
function addVendor(url){
var s1 = document.createElement('script');
s1.type = 'text/javascript';
s1.src = url;
try {
document.body.appendChild(s1);
}
catch (e) {
console.error("SP: Couldn't append " + s1.src + "to page. Error: " + e)
}
}
addVendor("http://ad.somevendor.net/site/c=14674/pe=y/?param=true");
Click Apply changes when finished.
Comments
0 comments