> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/cookie-consent-manager.md). # Cookie Consent Manager ## Why the standard banner is not enough Shopware ships its own cookie notice. It lists cookies and remembers a selection — but it does not hold any scripts back. Google Analytics, the Meta pixel or an embedded YouTube video still load before anyone has agreed to anything. This is exactly where GDPR and TTDSG get uncomfortable: legally it does not matter what you stored, it matters what your visitors' browsers actually loaded. ## What the extension makes of it The Cookie Consent Manager replaces the native Shopware banner with its own consent layer. Scripts are only delivered once the matching cookie group has been accepted. Every decision is logged so you can prove consent under GDPR Art. 7. And Google Consent Mode V2 is served correctly — with defaults in the head and an update after every decision. ## Core features * **Script blocking per cookie group** — external scripts and inline code only load after consent * **Cookie groups and cookies** managed centrally in the administration, with complete GDPR details (provider, purpose, lifetime, privacy policy link) * **Centered modal** and further banner layouts, TTDSG compliant without dark patterns * **Consent log** with a hashed IP address and an automatic retention period * **Google Consent Mode V2** including `dataLayer` events for Google Tag Manager * **Flow Builder** reacts to granted and revoked consent * Enabled **per sales channel**, multilingual and **headless ready** through the Store API ## Additionally in the premium plan Design editor with live preview, automatic cookie scanner, iFrame blocker, consent statistics, A/B tests, geo targeting, third-party presets, GTM container import and multi-domain synchronisation. Details under [Premium Version](/en/plugins/cookie-consent-manager/premium-version.md). ## Where to start * [Pre Requisites](/en/plugins/cookie-consent-manager/pre-requisites.md) — does the plugin run in your environment? * [Quickstart](/en/plugins/cookie-consent-manager/quickstart.md) — a working banner in ten minutes * [Installation](/en/plugins/cookie-consent-manager/installation.md) — every configuration field in detail * [Admin-Dashboard](/en/plugins/cookie-consent-manager/admin-dashboard.md) — your day-to-day workspace ## Result You get consent management that does not just store a selection but actually enforces it — without an external consent service, without a third-party monthly fee and without maintaining your cookie list twice. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.premsoft.de/en/plugins/cookie-consent-manager.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.