Salesforce

Maintaining Your Cookie Consent Implementation

« Go Back
Information
Maintaining Your Cookie Consent Implementation
UUID-7088e090-c8ea-c34f-bccf-91377a9f33ec
English
Checked
Content

After you have gone live with OneTrust Cookie Consent on your site, it is essential to take steps to maintain your implementation.

If new content is being added to your site or you are making changes to your configurations within the Cookie Consent application, you will need to take action accordingly.

Rescanning and Evaluating Content for Blocking

If you are not aware of the content being added to the site, or not aware of the cookies that will be dropped by newly added content, make sure to rescan your site at a frequency that makes sense for your team.

For example, if there is a code release to your site or your tag manager updates once a month, you can set yourself up for success by rescanning the domain once a month after the release. For more information about scheduling scans, see Configuring a Website Scan.

After the rescan is complete, check to see if there are any additional cookies in the scan results. If there are, identify which scripts or tags these cookies are coming from and apply the proper blocking methods Client Side Cookie Management and Integrating with Google Tag Manager. You can utilize the scan export resource URLs to assist in this.

It is not necessary to republish your script for blocking new cookies unless you are planning to block the cookie under and category id that is not present in the preference center or utilizing OneTrust Cookie Auto-Blocking. If you are using the Auto-Blocking feature, it is necessary test the functionality of the auto-blocking with the Testing script on a staging or preproduction site prior to publishing the production script.

Example: I only have cookies categorized in the Strictly Necessary category and the Performance category. Only these two categories are shown in my preference center. I manually add a Functional cookie and associate it with my domain in the Cookie Consent Application. After I add my new Functional cookie, I must republish my script to ensure that the Functional category is displayed to the users in my preference center. That way, users can opt in or out of the Functional category and the script will fire or not fire based on my configured blocking method.

Configuration Changes to Categorization, Templates, Geolocation Rules and Republishing

Anytime you categorize a cookie in a category that cookies were not previously categorized in for your domain, you must republish your script. This pushes the category to the preference center so the user will be able to give consent to the category in the preference center.

If you would like all users to reconsent due to the new category, make sure to configure in the publish modal. You will also want to make sure to implement the proper blocking methods for the newly categorized cookie. For more information, see Client Side Cookie Management and Cookie Consent Integration with Google Tag Manager.

Example: I only have cookies categorized in the Strictly Necessary category and the Performance category. Only these two categories are shown in my preference center. I manually add a Functional cookie and associate it with my domain in the Cookie Consent Application. After I add my new Functional cookie, I must republish my script to ensure that the Functional category is displayed to the users in my preference center. If you make any configuration change to a template, you will need to republish your script.

Example: I updated the Notice Description text on my banner. I now need to republish my script.

If you make any configuration change to a geolocation rule, you will need to re-publish your script.

Example: I added an additional geolocation rule to my geolocation rule group that is associated with my domain. I now need to republish my script.

Add the Blocking Methods to New Site Content SOP

Another way to maintain your implementation for new site content is to add the blocking methods to your SOP for adding new site content.

Example: If your team is adding a tag to Google Tag Manager that is dropping cookies that fall under the Targeting category, you can apply the appropriate trigger to the new tag so that tag is only fired or only drops the cookies when the Targeting cookie category is active.

You can rescan your site to get the new cookie into the Cookie Consent application for tracking, or add the cookie manually. See these articles for further assistance on re-scanning and adding cookies: Scanning a Webiste and Adding Cookies.

 

Powered by