Zum Inhalt


CCM19 can store the data for consent in a cookie, in local storage or in session storage. The individual methods have advantages- and disadvantages.

screenshot-2020.09.30-14_25_38-CCM19 - Cookie Consent Management Software (1).jpg

Saving the consent in a cookie allows the consent to be shared across several subdomains and different ports, but can slightly increase the page load time. This is the classic storage of data.

Storage in local storage

Storing the consent in local storage allows the information to be retained indefinitely in many browsers. However, the consent is limited to a hostname-port-combination.

Storage in session storage

Saving the consent in the session storage keeps the consent separate for each browser-tab. The moment the tab is closed, the consent is also forgotten.

Properties of the CCM19 element

screenshot-1641906509765 (1).jpg

You can use the mask to specify how long the CCM19 cookie should be stored (default is 365 days). If you enter a "0", the cookie will be deleted when you close the browser.

The option for "secure" cookies should only be deactivated if HTTPS/SSL is only used optionally. This allows the consent to be shared between the page without HTTPS and the one with HTTPS - but this is extremely rare nowadays. In addition, disabling this option can cause problems with the remaining consent-sharing-functions and when embedding the website in iframes due to the security functions of modern browsers.


With CCM19 it is possible to share the consent across any number of domains and subdomains independently of third-party-cookies. To do this, enter the list of desired domains in the field.

This function is only available in Business- and Enterprise-tariffs and the Agency-variant.

For each domain entered, the consent can be shared between the subdomains of the domain entered, as long as the same code-snippet is used. For example, enter example.com so that consent only needs to be granted once for example.com, www.example.com and all other subdomains ending in .example.com. Invalid entries can cause the saving of the consent to function unreliably

The consent is passed on via HTML-links, HTML-forms and iframes.

If you have a website where an iframe of another of your pages is used (e.g. a booking form), the iframe will not display another query, but the consent will be transferred. This only works if they are entered above and therefore also share the same scripts and cookies.

With these settings you can force all visitors who have given their consent before the set date to give their consent again. This happens if you have changed the mask and want to request consent again.

Consents older than this period are always canceled. If you leave the field empty or set it to "0", CCM19 will not automatically cancel the consent. Please note that if you use TCFv2, a maximum of 390 days (approx. 13 months) is enforced.


If the option "Automatically revoke consent on legally relevant changes" is activated, legally relevant changes to integrations and cookies mean that consent is no longer valid and is requested again. This includes the following changes:


  • Name
  • Purpose
  • Manufacturer/provider (also TCF-provider)
  • Description
  • Privacy Policy-URL
  • Data collected
  • Purpose of the collection
  • Legal basis
  • Place of processing
  • Cookie & Co. (Add/Delete/Edit [See EmbeddingAsset])
  • Google Consent Mode consents
  • TCF purposes
  • TCF special processing options

Embedding Asset: (list of cookies and storage elements in an embedding)

  • Name
  • Name Description
  • Storage type
  • Expiration

Cookies: (Old management structure)

  • Cookie name
  • Name of the cookie in the browser
  • Purpose of cookie
  • Manufacturer/provider
  • Cookie description
  • Lifetime of the cookie
  • Data protection-URL
  • Data collected
  • Purpose of the collection
  • Legal basis
  • Place of processing