The cookie banner
built for HubSpot.
Your HubSpot pages exist to convert, and consent decides how much of that you get to see. Velo keeps your CMS pages compliant across the EU, UK and US and wires Google Consent Mode v2, so the leads your ads drive stay measurable — modelled when visitors decline, counted when they accept.
Live in minutes — one tag through Google Tag Manager, or one line in your site header settings.
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 HubSpot
Paste the snippet into your site header in HubSpot's settings and it covers every CMS and landing page on the domain. Or install through Google Tag Manager and keep consent versioned with the rest of your measurement.
Three steps
on HubSpot.
Paste the snippet
In HubSpot, open the site header settings, paste the Velo snippet and save. 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 HubSpot teams ask before switching consent on.
How is this different from HubSpot's cookie banner?
HubSpot's built in banner covers notice and basic blocking of HubSpot's own tracking. Velo adds what ad platforms read: Google Consent Mode v2 signals, region rules across the EU, UK and US, an exportable audit log, and category choices that govern every script on the page — not just HubSpot's.
Does one install cover all my landing pages?
Yes. The site header applies to every CMS page and landing page on the domain, so one paste covers new pages automatically as your team ships them.
What happens to lead attribution when visitors decline?
With Consent Mode v2, declined visitors send cookieless pings and Google models the conversions you can no longer observe directly. Across Amplio Data client implementations that recovers 20–40% of consent hidden conversions. Measured ranges, not a guarantee.
Will it interfere with HubSpot forms or chat?
Velo governs when marketing scripts run; it does not modify them. Essential functionality keeps working before consent, and your marketing stack fires the moment the visitor grants it.
Works wherever you build
Consent handled.
Signal kept.
A compliant banner on HubSpot in minutes,
and the conversions consent hides, modelled back.