Deutsche Version

Back to overview

Klaro Cookie Consent: Configuration

Live Demo: Try this and other plugins live — no installation, no risk: demo.markus-michalski.net

The configuration has two parts: the module settings and the cookie services.

Module settings

You find them in the admin under Extensions > Modules > Klaro Cookie Consent Manager > Settings. The settings apply per shop.

General Settings

Consent Behavior

Storage Settings

Google Consent Mode v2

Styling

The admin also shows the fields "Accept All Button Color" (#1a73e8), "Save Selection Button Color" (#2581c4) and "Decline All Button Color" (#5c5c5c). They currently have no effect in the storefront, because the bundled stylesheet does not use the CSS variables they set. You can ignore them.

Managing cookie services

You manage the services under Customer Info > Cookie Consent. The list shows the services of the current shop with the columns Active, Technical Name, Title, Purpose, Required and Sort order. Use "Add new service" to create one.

The "Title" column of the list shows the technical name, not the saved title. You see the title in the edit view.

Each service stands for a third-party service or script that needs consent. Creating a service does not add a script to the shop. Which scripts a service controls is defined in your template, see Storefront.

Service fields

You maintain title and description per language: pick the language in the admin and save the service once per language. The storefront has texts for German (language ID 0) and English (language ID 1). If the title is missing in a language, the module uses the German title, then the technical name.

Saving with an empty technical name does nothing: no error message appears and nothing is saved.

Cookie deletion rules

When a visitor withdraws consent, Klaro deletes the cookies you entered. You can enter them in one of two notations.

One line per cookie in the format name,path,domain, path and domain are optional:

_ga
_gid
_pk_id,/,.example.com

As a JSON list:

[
    {"pattern": "_ga", "path": "/", "domain": ".example.com"},
    {"pattern": "_gid"}
]

This is how pattern is evaluated:

• A value that does not start with ^ is an exact cookie name.
• A value that starts with ^ is a regular expression, for example ^_ga_.*$.
• Wildcards such as _ga_* do not work, they are read as part of the name.

An entry that starts with [ but is not valid JSON is read line by line as a cookie list. Check the JSON before you save.

Practical examples

Google Analytics 4

[
    {"pattern": "_ga", "path": "/", "domain": ".your-shop.com"},
    {"pattern": "^_ga_.*$", "path": "/", "domain": ".your-shop.com"},
    {"pattern": "_gid", "path": "/", "domain": ".your-shop.com"}
]

You mark the Google script itself in your template with data-name="google-analytics".

YouTube embed with placeholder

You mark the iframe with data-name="youtube" and data-src, see Storefront.