Shopware's cookie consent manager sets and clears cookies, but it blocks nothing: every plugin has to gate its own scripts. Cookifi loads first from a Twig override and governs the lot.
Self-hosted Shopware 6 (including the free Community Edition) takes plugins and themes, which is all this needs. On Shopware SaaS plugins cannot be installed at all — you need a Store app that can change storefront templates or inject a header snippet.
Shopware has no admin field for head scripts. In your child theme or plugin create src/Resources/views/storefront/layout/meta.html.twig starting with {% sw_extends '@Storefront/storefront/layout/meta.html.twig' %}.
Override the block layout_head_javascript_hmr_mode: emit the Cookifi <script> tag, then {{ parent() }}. Dropping {{ parent() }} kills the Storefront JavaScript bundle, so keep it.
Admin → Extensions → My extensions → install and activate, then assign the theme under Sales Channels → Storefront → Theme.
Run bin/console theme:compile && bin/console cache:clear. A reverse proxy in front of the shop may still serve the old HTML until its cache is cleared too.
Settings → Shop → Basic information → Legal and compliance: untick 'Use default cookie notification' so the shop does not render two banners.
In the Cookifi admin click Add, enter a name and your domain — a sitemap URL is optional — and click Create.
Open the property and copy the script under General → Integration script.
Click the Google icon in the script toolbar to include the Consent Mode default command. The defaults themselves are set under Regions, together with URL Passthrough and Ads Data Redaction.
Paste it as high in the <head> as the platform allows, on every page. Save, reload, and confirm the banner appears.
If the platform strips data- attributes and the banner does not load, switch to Query string mode in the Installation script section and copy the script again.
Cannot touch the head at all? Use the GTM Installation script in a Custom HTML tag with the Consent Initialization – All Pages trigger. Direct installation is still the recommendation, because ad blockers can suppress GTM.
Because the core sends no gtag consent commands, Consent Mode v2 has to come from the CMP. Cookifi replaces the native manager and pushes the defaults itself; if you keep the native manager on as well, subscribe to document.$emitter's COOKIE_CONFIGURATION_UPDATE and mirror the state. Note that changing the cookie configuration changes the cookie-config-hash, which re-prompts every visitor.
Cookie consent manager
One script in the head, a scan that suggests the categories for you, and a 14-day trial that needs no card.
One monthly base from €10 plus usage on read events — the first 10,000 each month are free. Subdomains and team members are unlimited, so a second site is not a second plan.
Live chat and email on every plan, with a human response within one business day on Enterprise. We are a small team, which is why the things customers ask for tend to ship quickly.
Google and Microsoft Consent Mode v2 are first-class, GA4 and GTM are the default path, and Cookifi is a Google-certified CMP partner.
Not through a plugin: Shopware's cloud product does not allow plugin installation. You need a Store app that supports storefront template changes or header snippets, and then the script goes in through that app.
Yes, otherwise visitors see two consent UIs. Untick 'Use default cookie notification' under Settings → Shop → Basic information → Legal and compliance.
Almost always a cache: run theme:compile and cache:clear, then clear the reverse-proxy or Varnish cache. If the HTML has the script tag but nothing renders, check the browser console for a blocked request.
Every fact on this page comes from the pages linked below. Spotted something out of date? Tell us and we will correct it.
Last reviewed November 2, 2026
14 days, no credit card. If the install takes you longer than ten minutes, tell us — on our side that counts as a bug.