A cookie banner
that respects
your Webflow design.
You did not spend weeks in Webflow so a consent tool could paint over it. Velo's banner renders in Shadow DOM with its own light or dark theme, sits politely over your layout, and installs with one line in Site settings → Custom code. Compliant, fast, and out of your way.
Live in minutes — one tag through Google Tag Manager, or one line in Site settings → Custom code.
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 Webflow
Paste the snippet into Site settings → Custom code, head section, and publish. That is the entire install — no embeds on every page, no interaction hacks. Run Google Tag Manager instead? The gallery template does the same job from your container.
Three steps
on Webflow.
Paste the snippet
In Webflow, open Site settings → Custom code and add the Velo snippet to the head code. Publish. Or add the Velo template in Google Tag Manager.
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 Webflow teams ask before switching consent on.
Will the banner clash with my Webflow styles?
No. It renders inside Shadow DOM, so your classes never reach it and its styles never leak out. You pick a light or dark theme to sit with your design, and the type stays clean at every breakpoint.
Do I have to add anything per page?
No. One snippet in Site settings → Custom code covers the whole project, every page, including CMS collection pages. Publish once and it is everywhere.
Can my client's marketing team still use Google Tag Manager?
Yes — that is the recommended install. The Velo template lives in the GTM community gallery, sets the consent default before any tag fires, and keeps the whole measurement stack reviewable in one container.
Does Velo handle more than the EU?
Yes. Region rules apply the right behaviour by location: GDPR consent in the EU and UK, opt out regimes in US states that require them. One banner, correct everywhere.
Works wherever you build
Consent handled.
Signal kept.
A compliant banner on Webflow in minutes,
and the conversions consent hides, modelled back.