Developer-Settings
If you are not a developer, please do not change anything! The options are configured to work very well. These are highly specialized settings for developers; only change them if you truly know whatANDwhy you are doing so. Some of these settings can render your website unusable; always test everything - first.
Enable Widget-Cache
Enable this option to cache the response to Widget-requests. This significantly reduces response time, which in turn speeds up your website’s page load.
Minify JavaScript and CSS
Minify JavaScript- and CSS-code from CCM19 to speed up the loading of your web pages. Disable this feature only to simplify troubleshooting in case of problems. If disabled, Console.log messages will also be output!
My website is part of an ad--, and tracking-free network, e.g., ContentPass
Enable this setting if your website is part of a network that offers ad--, and tracking-free access to your content. If this network embeds a banner on your website that gives users the choice between a subscription and ad-supported access, it may also wish to take control of configuring the CMP-consent parameters on behalf of the user. In this case, the frontend-widget will not be displayed in favor of the network’s banner. It is then up to the network to perform the configuration via the JavaScript-API.
Execute inline-scripts using the eval-function
By default, CCM19 reloads inline-scripts by calling the eval-function. This behavior may be a concern, for example, if it does not comply with your website’s Content-Security-Policy (CSP). If this is relevant to you, you can configure it here.
Advanced Frontend-Behavior
Reload page when Consent-settings are saved
Enable this option to ensure that the webpage reloads after an update to the Consent-setting. This may be necessary if scripts that are initially blocked by CCM19 only become active after the page is reloaded.
Caution: An unexpected page reload does not provide a good user-experience and should be avoided whenever possible. In the vast majority of cases, you can achieve a solution that does not require a reload by adjusting settings in CCM19 or by re-triggering the necessary scripts.
Removing Unknown Cookies
CCM19 can be configured to remove cookies that are not stored in the tool as soon as they are detected.
Of course, this only works for first-party cookies. Third-party cookies—such as those embedded via iframes—cannot, unfortunately, be modified by your own site and therefore cannot be deleted. Your browser’s security settings prevent this.
Therefore, you must block these scripts or iframes before they are executed—that is, before they set the cookies.
Before you activate this feature, you should be absolutely certain that there are no cookies on your website that are not yet listed in CCM19 but are nonetheless essential for the site’s operation. This is because, with this setting active, all such cookies would be deleted every time a page is loaded.
Load Technically Necessary Embeddings Without Consent
If you maintain embeddings assigned to the “technically necessary” category, the source code, scripts, and iframes they target will not be blocked. This means that the site visitor’s consent is not required for these resources to be executed.
If you want to require the user’s consent before anything is loaded, you can disable this option—technically necessary embeds will then be loaded only after the visitor has given consent.
Force the “Reject” button when “Accept All” is selected
The German Data Protection Conference considers cookie-banners that make it more difficult to reject than to accept to be non---compliant with EU-regulations. This assessment is widely shared by many government data protection organizations EU-.
To protect you from legal consequences, we enforce the “Reject” button by default as soon as the “Accept All” button is active. You can disable this protection here if you are certain that you comply with all relevant regulations even without a “Reject”-button.
Override Persistent CSS-Declarations on the Website
Enable this option if there are unexpected layout issues in the frontend-widget, such as sharp corners when rounded corners are expected. Sometimes websites define their CSS-rules and mark them as !important;, which partially overrides the widget’s CSS-code. To counteract this, this option marks every custom CSS-rule as !important. Use with caution!
Optimize for Largest Contentful Paint (LCP)
If you notice in Google PageSpeed or other analytics tools that the CCM19-banner is listed as the decisive element for LCP, you can enable this setting to split up the banner text. This converts the large element into many small elements that are no longer relevant to the LCP.
Please note that this will not improve your page’s loading speed. The content being loaded remains the same. Splitting the banner would simply shift the focus to a different element as the LCP, which can then be optimized.
Enable Banner and Blocking Functionality Only on Configured Domains
If enabled, the banner will not be displayed and no scripts or iframes will be blocked if the domain-name does not match the name in the domain-settings or an entry in the domain list under "Consent-Storage."
Display the banner even if consent is not required
This option allows you to ensure that the banner is displayed even if it would not normally be shown due to other circumstances. In the opt---out-mode for countries outside the EU—where the banner is normally not displayed at all and all elements are preselected—the banner could still be displayed upon request, for example, to more prominently inform website visitors about the tools used and the opt---out-option.
Hide Banner for Specific Regions
Here you can enter countries where the banner should not be displayed. The banner must then be opened manually to view or change the cookie-settings.
Trigger Advanced GTM-Events for Each Active Embedding
If enabled and Google Tag Manager is in use, each activated integration triggers a CCM19.embeddingAccepted event in addition to the final CCM19.consentStateChanged event. You can disable this behavior here if you do not need these events.
Detect disguised scripts that use notations specific to other CMPs
This option enables the detection of scripts that use custom markup. Detected scripts follow the rules configured in this account. Behavior specific to another CMP is not emulated.
Currently, scripts that follow the following schemas are supported:
<script type="text/plain" data-cookieconsent="…">…</script>
<script type="text/plain" data-cookieconsent="…" src="…"></script>
Priority of the HTTP-headers Accept-Language over the HTML-attribute lang
By default, the language in the CCM19 banner is automatically determined based on the HTML-lang-attribute. If you enable this option, CCM19 will instead display the banner in the user’s browser language, provided that language has been enabled under “Texts & Languages.”
For the lang-specification, the system checks whether a matching translation is active in CCM19—once with the country code and once without it—during automatic detection. If no matching translation is found, the user-wide fallback language-is used, which can be set under "Available Settings." If this language is also not active in the domain, the system selects 'en_US', 'en_GB', 'en_DE', 'de_DE', 'de_AT', 'de_CH', and then the first available active language.
Using the example of en-GB, the prioritization would look like this:\ 1. en_GB\ 2. en or en_*\ 3. Fallback-language\ 4. Any language, but preferably English, then German
Delay in Displaying the Frontend-Widget
Here you can specify a time interval in milliseconds to wait before the widget is displayed when the website loads.
Block Scripts
General Blocklist: Always block -, without exception!
If you enter something here, all scripts containing this string will be blocked everywhere, without giving users the option to unblock the script in question.
Enter one expression per line. Scripts containing any of these strings will always be blocked, without exception. This can be used to block dynamic or other scripts.
However
This only applies to scripts contained on the page; scripts added via embeddings, for example, are not affected.
Block Scripts
Here you can configure the behavior of the Script-Blocker. This feature blocks the loading of scripts that are not under CCM19’s control. This automatically prevents the setting of unwanted cookies as well as the execution of unknown scripts.
Automatically Block New Scripts
If this checkbox is selected, scripts newly detected by CCM19 are immediately disabled and blocked. Please use caution here—it may also block necessary functions that you may not have marked as desired.
Also block scripts from your own domain
If this feature is enabled, all scripts from your own domain will also be blocked when they are newly detected. Example:
Also block inline scripts
If this is enabled, inline scripts embedded as snippets in your page will also be disabled when they appear on the page. Example:
``````
Exceptions for Inline-Scripts
If scanning for inline and custom scripts is also enabled in CCM19 (not recommended, as it consumes a lot of resources), you can enter exceptions there that should be ignored due to specific code snippets.
Scripts Found
Here you will find a list of all external scripts that the CCM19 widget’s automatic scanner finds on your page.
List of Scripts
This list shows you which scripts are present on your site (the entire code snippet is displayed). It also includes a link indicating where the script was first found and whether it is active.
The red “Delete” button removes the script from this list—it does not cause the script to be removed from your page. It remains on the page and is still executable.
Disable Scripts
You can manually and globally disable the scripts found here. For example, if you do not have 100% control over the page’s source code (as is often the case with many cloud--providers), you can use this feature to access it and prevent the scripts from being embedded.
To disable a script, set the toggle to “inactive.” This will block it in the frontend as long as the CCM19 widget is active.
Change the Management Structure
By default, CCM19 is configured so that customers/visitors to your website can choose whether or not to consent to the scripts in the block along with their associated cookies. Take Google Analytics as an example: users can consent to or decline its use, but not to the use of individual cookies—this simply doesn’t make technical sense.
The old version of CCM19 did allow this, but we changed this a long time ago. Some older versions still use the outdated cookie setting, so we’re offering the option to change this here.