Cookie Consent Manager
Installation
Installing the plugin
You will find the plugin in the Shopware Store. Install it like any other extension:
- Extensions → My extensions → Cookie Consent Manager → Install
- Then Activate
- In the configuration, select the sales channel and turn Activate plugin on
During installation the plugin creates the database tables for cookie groups, cookies, the consent log and the A/B tests in the background, and fills the four default cookie groups. There is nothing for you to do.
Plugin configuration
The settings live under My extensions → Cookie Consent Manager → Configuration. All values can be stored per sales channel — always pick the right channel at the top first.
General
| Setting | What it does |
|---|---|
| Activate plugin | Enables or disables the cookie consent banner for this sales channel. |
Compliance
| Setting | What it does |
|---|---|
| Show banner on first visit | Opens the banner automatically on the first page view. Off: the banner only opens through the cookie settings link. |
| TTDSG mode: all buttons with the same colour | Presents Accept and Reject with equal prominence. Prevents dark patterns — leave it on. |
| Button order | Reject left, accept right (TTDSG recommended) or the other way round. |
Banner base design
These values are the fallback as long as no design has been saved in the design editor (premium). As soon as a design exists there, the design takes precedence.
| Setting | What it does |
|---|---|
| Banner position | Centered modal, Bottom bar, Top bar plus four further layouts (bottom left/right corner, fullscreen overlay, sidebar drawer) that require the premium plan. |
| Darken background | Places an overlay behind the banner. |
| Accept button colour | Base colour of the primary button. |
| Reject button colour | Base colour of the secondary button. |
| Banner design configuration (JSON) | Managed by the design editor. Do not edit manually. |
If you select a premium layout without premium, the banner falls back to Centered modal.
Behaviour
| Setting | What it does |
|---|---|
| Consent validity (days) | Lifetime of the consent. Default 365. After that visitors are asked again. |
| Enable consent logging | Writes every decision with a hashed IP into the consent log. |
| Block scripts before consent | The core function. Off: all scripts load immediately — only useful for testing. |
| Consent log retention (months) | Older entries are removed by a monthly task. Default 36. |
| Cookie configuration version | Increased automatically whenever cookies or groups change, which asks visitors again. Can also be raised manually. |
| Scan the shop for cookies weekly (premium) | Enables the scheduled cookie scanner. |
| Consent renewal mode (premium) | Force: show the full banner again. Gentle: a small notice bar at the bottom. |
Google Consent Mode
| Setting | What it does |
|---|---|
| Enable Google Consent Mode V2 | Sends consent signals to Google tags. |
| Default consent status | Denied (recommended) or Granted. |
| Ads data redaction (premium) | Strips identifiers from ad requests while there is no marketing consent. |
| URL passthrough (premium) | Carries click parameters through the URL instead of cookies. |
| Region-specific defaults (JSON) (premium) | e.g. [{"region":["DE","AT"],"default":"denied"}] |
| Debug mode (premium) | Logs consent mode changes to the browser console. Turn off on production. |
Details and pitfalls: Google Consent Mode & Tracking.
Tracking integrations
| Setting | What it does |
|---|---|
| GA4 Measurement ID | e.g. G-XXXXXXX. |
| Google Ads ID | e.g. AW-XXXXXXX. |
| Load gtag.js directly through the plugin | Renders gtag.js as a script of the Statistics group. Do not enable it when Google Tag Manager already loads GA4 — that causes double tracking. |
| Facebook/Meta Consent API (premium) | Controls the Meta pixel via fbq('consent', ...). |
| Send consent status to server-side tracking (premium) | Sets the X-Prems-Cookie-Consent response header and posts the consent record as JSON. |
| Server-side consent endpoint URL (premium) | Target of the JSON POST. Absolute HTTPS URL or a relative path. |
iFrame blocker (premium)
See iFrame Blocker.
Geo targeting (premium)
See Geo Targeting.
Multi domain (premium)
See Multi-Domain Synchronisation.
Uninstalling
When uninstalling you can choose whether the data is kept. If you remove it, cookie groups, cookies, A/B tests and the entire consent log are deleted.
Remember that you have to be able to prove consent under GDPR Art. 7. Export the consent log as CSV before deleting the data.
Next steps
Have a look at the Quickstart or jump straight into the Admin-Dashboard.