In the Settings section, you can select any of the following Languages you want the Consent Manager to display.
|
|
|
The Consent Manager banner includes a built-in language selector. You can select their preferred language directly from the banner, and content updates immediately without requiring a page refresh. The selected language is saved and automatically applied on future visits.
You may set the number of months a user’s consent will remain valid by clicking the Consent Duration dropdown list. This can be configured from 1 to 13 months duration.
You can also enable additional features for your Cookie Consent Manager.
-
Enable Auto-block
This auto-block feature provides an easier way to implement auto-block in CCM for trackers not consented to. This achieves compliance with GDPR and other laws, sets a tool to prepare for 3rd party cookies’ disappearance, and be able to solve “dark pattern” objections. Particularly, enabling this feature will let this CCM instance know that you are deploying CCM with the TrustArc Auto-block deployment method. If the feature is not enabled, the Auto-block method will not execute.
-
Enable Consent UID
The Consent User Identifier (UID) is an optional feature that can be enabled on the TrustArc backend. It is disabled by default. Enabling this feature will set a cookie and localstorage object with a randomly generated unique identifier (UID) value to each end-user’s browser the first time a consent preference is submitted. These objects will expire automatically after 13 months.
The Consent UID is passed to TrustArc and stored in our database and on the end-user's browser to tie the end-user's consent to this unique parameter. Consent Manager users who wish to pass a unique identifier for their own more comprehensive internal auditing purposes may find this feature useful.
For instance, website end-users that request a record of their consent history could be instructed to view their browser’s cookie details and provide you with this UID value, thereby making it easier for you to download a report specific to their consent history.
The Consent UID can be viewed using the GDPR Compliance Reporting Widget on the Consent Manager Admin Portal, or in the downloaded spreadsheet.
See more information on the TAconsentID cookie and truste.eu.cookie.TAconsentID localStorage object under the TrustArc Cookies and Local Storage Objects section.
Important: It is recommended that you consult with your legal counsel regarding incorporating disclosures about Consent UID practices into your Privacy Policy or Cookie Policy, as applicable.
-
Deploy multiple consent managers on the same root domain
When this feature is enabled, the Consent Manager will append its ID value in the form of a cookie on the users' browsers when consent is given. This allows you to deploy multiple consent managers on the same root domain in order to display differently branded versions or ensure users are consenting to the correct list of trackers. If you do not enable this setting, users will only be prompted to consent from one of the deployed consent managers.
NOTE: Do not deploy multiple consent managers on the same page, this is not supported.
-
Integrate Cookie Consent Manager with Tag Management System
The CM can be integrated with a Tag Management System such as Google Tag Manager, Tealium, or Adobe DTM to control the firing of tags based on the level of consent provided by the end-user. Note that if your website does not use a tag manager, the CM will default to using 3rd party vendor opt-out cookies (where such opt-out cookies are available for a vendor/service provider). Note that, in contrast to integrating the CM with a tag manager, because of the nature of the 3rd party vendor opt-out method, cookies and tracker scripts will not be suppressed upon site load, which could pose regulatory risk in the EU for consideration with your legal counsel.
Selecting the Apply zero tracker load to visitors from Europe only checkbox enables the notice_behavior cookie. This enables you to isolate the user to an EU location where non-essential tags are not immediately fired on first page load if the end-user is in the EU region and has not yet consented to some or all non-essential trackers.
Disclaimer: Plugins and browser extensions can block your tag managers and then, block CCM. Please check if your tag manager works with the popular Adblockers. If your tag manager is blocked, you may consider firing the TrustArc scripts outside of the tag manager in the HEAD tag.
Important: To ensure consent preferences are appropriately honored, once a tag script or code has been executed on a page (i.e., a tag has fired), you will need to configure an automatic page refresh in order for the new consent preference to be reflected. Failure to execute a refresh will result in the prior tracking behavior (e.g., tracking will continue as if an opt-out had not occurred) to persist until a manual refresh is done by a web visitor themselves.
Please refer to the sample code below for page refresh:
window.addEventListener("message", (event) => {
let eventDataJson = null;
// We only care about TrustArc Events at this point. And TrustArc's even it encoded in JSON
try {
eventDataJson = JSON.parse(event.data);
} catch {
// Some other event that is not JSON.
// TrustArc encodes the data as JSON
// console.log(event.data);
}
// Safeguard to make sure we are only getting events from TrustArc
if (eventDataJson && eventDataJson.source === "preference_manager") {
// Means that the user has submited their preferences
if (eventDataJson.message === "submit_preferences") {
// Reload the page
setTimeout(function(){window.location.reload();},500);
}
}
}, false);NOTE: This is a sample code only and must be evaluated before implementation. TrustArc is not liable for any data loss due to page refresh. Please consult your IT and Marketing teams before implementation.
-
Automatically request consent from visitors again in the future.
If your website’s tracking technology practices change and you wish to request consent again from previously consented users, open the date and time selector and select the date and time when you would like for this to occur. You will force the consent manager to re-appear for all users, including those who have previously submitted their consent. By default, the user's consent is stored for 13 months (or time specified in consent duration) and users will be asked to re-consent after their consent expires.
Your website visitors will encounter the message below when their consent is re-requested.