FAQ consent manager

Introduction

This document answers frequently asked questions about the Consent Manager, cookie banner, and cookie settings.

For more assistance on the Consent Manager functionality, see the user guide article:

Consent Manager

Q: Why does the scan miss some of the cookies?

Why doesn't the scan catch all of the cookies?

Why are some cookies missing from the scan?

A: The scheduled scan picks up cookies, but some may be missed. The most common reasons are:

• A cookie that is set by Javascript might be missed if we are not running Javascript on the page. This situation could occur, for example, if your website has Accessibility enabled, or if javascript is enabled in the domain features.
• Some cookies are only set when the user clicks a button or interacts with some other aspect of the page.

Some remedies:

• For cookies that you know are present but sometimes are missed by the scan, we offer a manual setup and exemption feature for specific cookies.

  See the following user guide articles:

  Consent Manager

  • Cookie Setup - Manage Cookies Manually
  • Cookie Setup - Manage Cookies with the Scan

If the problem persists, contact our support team.

Q. When a user sets cookie preferences, are they saved directly to the website or do they save on Monsido’s servers?

Where are cookie preferences saved?

Are cookie preferences saved on my website?

Are cookie preferences saved on an Acquia server?

Where are cookie preferences saved?

What information about cookie preference is stored?

A: Cookie preferences are handled in this way:

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

  For more information, see the user guide articles: 

  Consent Manager

  • Cookie Setup - Manage Cookies Manually
  • Cookie Setup - Manage Cookies with the Scan
• The log of the cookie consent is saved on Acquia servers for two years. The information that we track and store contains the following:
  • 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

    This ID is gone from the user's device when the cookies on that device are deleted by the user. When the UUID is gone, the user can no longer 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 under Data Privacy - Consent Log.

  For more information, see the user guide article:

  Data Privacy ->

Q. Not all of the cookies are being blocked for users that choose just the Essential cookies, how can I fix this?

Why are some non-essential cookies placed on my visitors' browsers?

Why are cookies put on the customer's browser even though they declined?

• Check to make sure all of the cookies on your site have been categorized correctly.
  • Cookies that are uncategorized are not blocked by the Essential setting.
  • Cookies that are categorized as Essential are always included. Make sure that the non-essential cookies are categorized correctly.

For more information, see the user guide article:

• Consent Manager ->
  • Cookie Setup - Manage Cookies Manually
  • Cookie Setup - Manage Cookies with the Scan.

Q. What happens to newly added, uncategorized cookies on my site?

What if I get some new cookies on my website?

I have some uncategorized cookies, how do I fix it so that they are blocked with the cookie banner?

A: 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, see the user guide article:

• Consent Manager ->
  • Cookie Setup - Manage Cookies Manually
  • Cookie Setup - Manage Cookies with the Scan.

Q. How do I set up the Consent Manager SDK?

For more information and a full explanation, see Consent Manager for Developers.

Q. What determines the font used in the cookie banner?

Can I change the font and colors on the cookie banner?

Can I edit the typeset and color scheme of the cookie banner?

The cookie banner font automatically adapts to the font type that is set on the website in the <body> tag. So if a website uses font type Arial as the font set in <body> then the cookie banner also shows with font type Arial.

Q. How can I fix it so that cookies only load after the consent choice has been provided by the visitor?

How can I set it up so that cookies are applied after the visitor consents?

How can I change when cookies are sent to the visitor?

HTML attributes must be added to content elements on your website if you only want them to load after a consent choice has been provided by the visitor.

For example, if you use Google Analytics on your website and only want the script to load once a visitor has accepted Statistics cookies, you need to mark up the Google Analytics script with an HTML attribute.

For more information and instructions, see the Web Governance for Developers article:

Consent Manager Attributes.