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 — and wires Google Consent Mode v2 so strict consent stops meaning blind reporting.
Live in minutes — one tag through Google Tag Manager, or one line in your storefront template.
Compliant. Fast.
Nothing Lost.
Compliant by default
Region rules apply the right law by location — GDPR consent in the EU and UK, opt out where US states require it. Equal Accept and Reject, per category choices, and every consent recorded in an exportable audit log.
Consent Mode v2, wired right
The denied default lands before any tag fires — the step most installs get wrong. Declined visitors send cookieless pings, and Google models the conversions consent hides instead of dropping them.
Made for Shopware
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.
Three steps
on Shopware.
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.
Denied by default, banner up
Velo sets the 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.
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.
Real Results.
Not Promises.
+37%
Average ROAS lift
Reported across paid channels once consent signal is restored and modelled the compliant way.
20–40%
Conversions recovered
Won back through Consent Mode v2 and server side tagging, so reporting reflects revenue that was already happening.
34%
Sessions brought back
Otherwise hidden by consent, brought back into view, so the data you pay for actually shows up.
Measured ranges across Amplio Data client implementations, not a guarantee.
Questions,
answered.
What Shopware teams ask before switching consent on.
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.
Works wherever you build
Consent handled.
Signal kept.
A compliant banner on Shopware in minutes,
and the conversions consent hides, modelled back.