A cookie banner
as considered
as your Framer site.
Framer sites are built by people who notice details. Velo's banner holds that standard: its own light or dark theme rendered in Shadow DOM, typography that stays crisp, equal Accept and Reject — and underneath it, Google Consent Mode v2 wired the way Google expects.
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 Framer
Paste the snippet into Site settings → Custom code, in the start of the head tag, and publish. One paste covers the whole site. If you run Google Tag Manager, the Velo template from the community gallery does the same job from your container.
Three steps
on Framer.
Paste the snippet
In Framer, open Site settings → Custom code, add the Velo snippet to the start of the head tag, and 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 Framer teams ask before switching consent on.
Will the banner look right on a designed site?
That is the point of it. The banner renders in Shadow DOM with its own theme, so your styles never distort it and it never leaks into yours. Light or dark, it reads as considered rather than bolted on.
Does Velo work on Framer's plans?
Custom code in Framer requires a paid site plan. On any paid plan, the install is one paste in Site settings → Custom code and a publish.
Do I need Google Tag Manager?
No. The snippet works standalone through Custom code. Teams that already run GTM can use the Velo gallery template instead and keep measurement in one place.
Why care about Consent Mode v2 on a portfolio or product site?
If Google Ads or GA4 touch the site and EEA visitors reach it, Consent Mode v2 is required — and it is what keeps declined visitors from vanishing from your numbers. Google models what consent hides; across Amplio Data client implementations that recovers 20–40% of it. Measured ranges, not a guarantee.
Works wherever you build
Consent handled.
Signal kept.
A compliant banner on Framer in minutes,
and the conversions consent hides, modelled back.