Consent management for Shopware
Shopware decides what it may do by reading its own cookie flags. Consent Studio writes those flags from your customer’s answer and publishes Shopware’s own consent events alongside them, so wishlists and core analytics wait for permission rather than assuming it.
- Drives Shopware’s own flags
- Flags you configure yourself
- Integration in testing
From €10 a month. No credit card, no per-visitor billing.
A cookie banner that works with Shopware
This integration is in testing: it works and it is in the product, and we are still gathering results across themes and versions before calling it finished. Everything below describes what it does today.
It writes the flags Shopware reads
Shopware gates its own features on cookie flags rather than on a consent interface, so this integration writes them. A granted category sets its flags; a refused one clears them outright. Alongside that, Consent Studio publishes Shopware’s own analytics and cookie-configuration events, so a theme listening for either hears the change the moment it happens.
- In testing
- Shopware’s own events
You decide which flags belong to which category
This is the only integration here whose mapping is yours rather than ours. Three lists, one per category, and you fill them with whatever flag names your theme and plugins actually use. Shopware’s own consent flag is always in the functional list whatever you type, because nothing works without it.
- Three lists you fill
- One flag always on
It refuses to overwrite your data
Flag names and data sometimes share a cookie name on Shopware, and a recently-viewed list is not a yes or no. So each flag is read before it is written and skipped unless it is empty or already a flag, and every write happens both across your domains and host-only, because Shopware sets its own cookies that way on www subdomains.
- Reads before writing
- Domain and host-only
Serving California as well as the EU?
The GDPR and the CCPA ask for opposite defaults, and a banner built for one of them quietly gets the other wrong.
Opposite defaults, one banner
The GDPR wants marketing denied until a visitor agrees. The CCPA runs the other way, as an opt-out. Region rules give each visitor the right starting state, so one banner answers both without a second install for the US.
Global Privacy Control is respected
California treats a browser opt-out signal as a request you have to honour. Consent Studio reads GPC and can apply it before the banner is ever shown, on every plan.
One record, both regimes
Whichever default a region gets, the decision goes into the same consent log. There is nothing separate to keep in step when an auditor asks for one history.
One answer controls every tool on your site
A banner that only governs the platform leaves everything you added on top of it running. Consent Studio speaks to the tools around it as well, and by default holds anything it does not recognise until the visitor says otherwise.
Discover All Integrations
Choose how to install the cookie banner
Every route ends with the same banner and the same consent record. Pick the one that fits how your site is built.
Direct code
Recommended RouteAdd the snippet to your theme’s head, or ship it from a plugin if you would rather keep the theme untouched. It has to load before Shopware’s own scripts so the flags are correct on the first request.
- Full control
- No dependencies
Google Tag Manager
Already running a container? Add our official tag from the Community Template Gallery on the Consent Initialization trigger, and nothing goes into your theme at all.
- Official tag template
- No site deploy
How to set up cookie consent for Shopware
The install is ordinary. The step that decides whether this works is the third one, and it is the only step in this whole family that asks you to look something up first.
Add your store in Consent Studio
Create the site and the banner is generated for your domain, with your categories, your text and your styling. All of that lives in Consent Studio rather than in Shopware, so changing it later never means touching your theme again.
Load the banner before Shopware’s own scripts
Add the snippet to your theme’s head, or ship it from a plugin if you would rather leave the theme alone. Order matters more here than on most platforms: the flags have to be right on the first request, because Shopware reads them as it renders rather than asking again later.
Find your flag names, then fill in the three lists
Open Web CMP, go to Integrations and enable Shopware. You will find three fields, one per category, and they are yours to fill: the flag names your theme and your plugins actually check. Shopware’s own consent flag is always in the functional list and does not need typing. This is the step to do carefully, because a flag left out of every list is a feature that never gets permission, and a flag in the wrong list is a feature that gets it too early.
Test a refusal, not just an acceptance
Load your store in a private window and decline everything, then check that the features you mapped are actually off. Accepting is the easy path and almost always looks right; refusing is where a missing or misfiled flag shows up. Consent Studio’s weekly crawl will list what your pages load either way, which is the second half of the same check.
A cookie banner alone is not enough
Most sites are leaking before anyone notices. Not through malice, but through a tag somebody added in a hurry, a vendor that changed its script, a plugin that phones home.
- Unconsented tracking
- Unwanted overseas transfers
- Consent records you cannot produce
- Scripts you never approved
The Full Consent Stack.
Three products, one consent record. What a visitor agreed to in the banner is what every downstream tag sees.
Which plan Shopware needs, and why
Essential covers this. The Shopware integration is identical on every plan, so what changes as you grow is how many integrations you run and how closely you watch them.
Essential is enough
€10/month
- The Shopware integration and its flags
- Three integrations included, then charged
- Unlimited pages, 200,000 consent actions a month
What Professional adds
€36/month
Worth it once the store runs more than a handful of tools, or you want to check a flag change straight away.
- More depth: HTTP consent cookies, accessibility, re-prompting
- Unlimited integrations, Essential includes three
- On-demand scans, after changing your flags
- Sitemap scanning, for every product page
Every plan includes
Trusted by organisations that care about privacy
Frequently asked questions about Shopware
What does it mean that the Shopware integration is in testing?
It is in the product and you can switch it on today; we have not yet seen enough results across Shopware themes and versions to call it finished. Consent Studio itself is not in testing, only this platform integration, so the banner, the consent record and Google Consent Mode all behave exactly as they do everywhere else.
Does Shopware have a built-in cookie consent manager?
Shopware ships a cookie configuration panel that lists cookie groups and lets a shopper toggle them. It handles Shopware’s own features and stops there: it does not keep a per-visitor record you can produce on request, and it does not govern the tags and plugins you added around the platform.
Does Consent Studio work with Shopware Analytics?
Yes. Analytics consent is published on Shopware’s own analytics event as well as written to the flags, so Shopware Analytics sees the decision through the mechanism it already listens to. Refusing analytics clears the flag and publishes the refusal rather than simply not sending anything.
Which cookie flags do I need to configure?
The ones your theme and plugins actually check, which differ between stores, so Consent Studio asks rather than guesses. There are three lists, one per category. Shopware’s own consent flag is always applied to the functional list without being typed, and a general cookie-preference flag is always set.
Will it overwrite Shopware’s existing cookies?
No. Every flag is read before it is written and skipped unless the value is missing or is already a simple yes or no, which is what protects data stored under a cookie name, such as a recently viewed products list. Flags are also written both across your domains and host-only, because Shopware sets its own that way on www subdomains.
Get Started with the Full Consent Stack
Everything you need in one bundle. Consent Studio provides you with a consent banner, scanner and client-side tag manager that guarantees no data ever gets transferred overseas.
Read the documentation
Our help center walks through every integration, plugin and template step by step, with screenshots. It is written and kept current by the people who build Consent Studio.