Cookie Consent Manager FAQs

This article contains answers to several frequently asked questions about the Web Governance Cookie Consent Manager.

Why does the scan miss some of the cookies?

The scheduled scan picks up cookies, but it may miss some. The most common reasons are:

• The scan might miss a cookie that was set by JavaScript on the page. This situation occurs, for example, if your website has Accessibility enabled or if Javascript is enabled in the domain features.
• Some cookies are only set when the website visitor clicks a button or interacts with another aspect of the page.

Some remedies:

For cookies that are present but sometimes missed by the scan, Web Governance provides a manual setup and exemption feature.

For more information, read How to manage cookies.

If the problem persists, select Contact support in the Help menu to start a chat, or email Acquia Support.

When a user sets cookie preferences, are the preferences saved to the website or Web Governance's servers?

1. The cookie preference is stored in the cookie that is saved to the browser of the website visitor.

   For more information, visit:

   • Consent Manager setup introduction

2. The cookie consent log is saved on Acquia servers for two years.

   Web Governance tracks and stores the following information:

   • IP address: The IP Address of the device that received the cookie (anonymized)

   • UUID: The unique ID for the user device that received the cookie.

     Note

     The UUID is removed from the user's device when the user deletes the cookies from their device. Without the UUID, the user cannot request the record of the cookie consent.   

   • Location: Location (country) of the device that received the cookies.
   • Data Regulation: This is the data regulation category of the website (GDPR/CCPA).
   • Accepted Cookies: The cookie categories that the website user accepted.
   • Date: The date that the cookies were received by the device.

   View the log in the platform with these steps:

   1. Log in to your Web Governance account.
   2. Click Privacy on the left menu bar.

For more information, read the Data Privacy collection.

Why do non-essential cookies load when a user selects only essential cookies? How can I fix this?   

Ensure that all of the cookies on your site are categorized correctly.

• Cookies that are uncategorized are not blocked by the Essential setting.
• Cookies that are categorized as Essential are always included. Ensure that the non-essential cookies are categorized correctly.

For more information, read:

• Consent Manager setup introduction
•  How to manage cookies

What happens to newly added, uncategorized cookies on my site? What should I do to ensure that uncategorized cookies are blocked with the cookie banner? 

Cookies are not blocked until they are categorized. There are two ways to configure them so that they are categorized correctly, manually or with the scan.

For more information, read:

• Consent Manager setup
• How to manage cookies

How do I set up the Consent Manager SDK?

For information on how to set up the Consent Manager SDK, read the Acquia Web Governance for developers collection.

How do I customize the font and colors on the cookie banner?   

The cookie banner font automatically adapts to the font type that is set on the website in the <body> tag. If a website uses font type Arial as the font set in <body>, the cookie banner inherits the font type Arial.

How do I configure cookies to load only after visitor consent?   

HTML attributes must be added to content elements on your website if you only want them to load after a consent choice is provided by the visitor. For example, if you use Google Analytics on your website and only want the script to load after a visitor has accepted Statistics cookies, you must mark up the Google Analytics script with an HTML attribute.

For more information and instructions, read Web Governance for developers.