Article Navigation
Introduction
This document answers frequently asked questions about the Monsido Consent Manager, cookie banner, and cookie settings.
For more assistance on the Monsido Consent Manager functionality, see the
Monsido Consent Manager chapter of the User Guide.
Q: Why does the scan miss some of the cookies?
A: The scheduled Monsido scan picks up cookies, but some may be missed. The most common reasons are:
This might happen if a cookie is set by Javascript and Monsido is 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, Monsido offers a manual setup and exemption feature for specific cookies.
See the following Monsido User Guide articles:
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?
The cookie preference is stored in the cookie that is saved to the browser of the website visitor.
The log of the cookie consent is saved on Monsido servers for two years. The information that Monsido tracks and stores 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 Monsido platform under Data Privacy - Consent Log.
Q. What are the implementation steps?
See the User Guide sections:
Q. Not all of the cookies are being blocked for users that have chosen just the Essential cookies, how can I fix this?
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.
Q. What happens to newly added, uncategorized cookies on my site?
Cookies are not blocked until they are categorized.
Q. How do I set up Monsido Consent Manager SDK?
For more information and a full explanation, see Consent Manager for Developers for instructions.
Q. What determines the font used in 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?
HTML attributes must be added to content elements on your website if you only want them to load once a consent choice has been provided by the visitor. For example, if you are using Google Analytics on your website and only want the script to load once a visitor has accepted Statistics cookies, you will need to mark up the Google Analytics script with an HTML attribute.
For more information and instructions, see the Monsido for Developers article: