The cookie banner
built for Shopware.
Shopware stores live where consent enforcement is strictest. Velo gives you a banner regulators and customers can both live with: equal Accept and Reject, category choices, an audit log. It also wires Google Consent Mode v2 so strict consent stops meaning blind reporting.
Compliant, fast,
nothing lost.
Add the tag to your storefront's base template and recompile the theme, or skip theme work entirely and install through Google Tag Manager. Either way the denied default is set before any other script runs, which is the part audits actually check.
How it goes live
on Shopware.
Three steps, about ten minutes.
-
01
Add the tag
Add the Velo snippet to your storefront template and clear the cache, or add the Velo template in Google Tag Manager and leave the theme alone.
your-shop.com/admin · Theme
-
02
Denied by default, banner up
Velo sets the Google Consent Mode v2 denied default before any other tag runs, then shows the banner. Nothing non essential fires until the visitor chooses, and every choice lands in the audit log.
your site
-
03
Verify and forget it
Check the consent signals flip in Tag Assistant or your browser, publish, and you are done. Region rules, records and Google's modelling run on their own from here.
Shopware questions,
answered.
What teams putting a banner on Shopware ask first.
Does Velo fit German market GDPR practice?
Velo defaults to what EU data protection authorities expect: nothing non essential runs before consent, Reject is as easy as Accept, choices are per category, and every consent is recorded in an exportable audit log.
Theme template or Google Tag Manager: which install?
If the store already runs Google Tag Manager, use the gallery template: no theme changes, no recompile, and the whole measurement stack stays reviewable in one place. The template edit is there for stores that keep everything server rendered.
What does Consent Mode v2 recover on a strict setup?
Declined visitors send cookieless pings that let Google model the conversions consent hides. Across Amplio Data client implementations that recovers 20–40% of them, with ads_data_redaction available for the strictest EU setups. Measured ranges, not a guarantee.
Will the banner slow the storefront down?
The script stays at or under 30KB and does not block rendering. Shopware's caching keeps doing its job; the banner arrives after the page paints.
From the journal.
Your banner, your consent,
your data, all in one place.
