Add Velo
to HubSpot.
Install the Velo cookie banner and Google Consent Mode v2 on HubSpot with one line in Site header HTML. Most installs take a few minutes when you already have admin access to the site. If you run Google Tag Manager, that route is on this page too.
Instructions and image sources reviewed 23 September 2026.
Paste one line
into Site header HTML.
Add your site’s snippet to the site-wide head, then publish and test the result. If your measurement tags already run through Google Tag Manager, use the route below.
Already using Google Tag Manager? Skip the code and do it there ↓
Three steps · about two minutes
-
01
Copy the line
Copy the complete installation snippet for this site from your Velo dashboard. The example below shows the format; replace your-site-id before using it. Keep the API endpoint supplied by your dashboard.
<script src="https://cdn.veloconsent.com/v1/velo.js" data-api="https://app.veloconsent.com" data-velo-site="your-site-id" async></script> -
02
Open Settings → Content → Pages
Choose the domain to update, then the Templates tab. Paste your complete Velo snippet into Site header HTML and save. To override inherited settings for a specific domain, enable Override default settings. Check page-level overrides before assuming every page inherits the header.
Official documentation image, reviewed 23 September 2026 HubSpot’s domain-wide Site header HTML field. Its documentation shows Google Analytics as an example; paste your Velo snippet in this field.
HubSpot documentation ↗View full size ↗ -
03
Publish and check the live site
Save and publish the change using the platform steps above, then clear any site or CDN cache. Open the published URL in a fresh browser session. Check the banner where your region rules require it, test accepting and rejecting, and verify consent defaults and updates before your measurement tags run. Confirm the site appears as installed in your Velo dashboard.
Live interface capture · 23 September 2026 The real banner on veloconsent.com, captured on 23 September 2026. Your banner’s copy, layout and region settings may differ.
Velo live site ↗View full size ↗
Turn HubSpot's own banner off under Privacy & Consent first. And note that HubSpot's analytics is not a Google tag, so Consent Mode does not gate it by itself. If compliance requires that, load it through Tag Manager and gate it on the velo_consent_update event.
Still comparing options? Read why teams use Velo on HubSpot, or see every supported platform.
Use Tag Manager?
Skip the code.
If Google Tag Manager is already on your site, this is the easiest way to add Velo. There’s no code to touch, it takes four short steps, and all your tags stay in one place.
- 01
Add Velo to Tag Manager
Open the Velo template, click Add to workspace, then pick your container.
Open the Velo template ↗ - 02
Paste your site ID
In Tag Manager, open Tags and click New. Click Tag Configuration, choose Velo CMP and paste your site ID. You’ll find it in your Velo dashboard. Leave everything else as it is.
- 03
Make it load first
Click Triggering, choose Consent Initialization – All Pages, then click Save. This lets Velo start before your other tags.
- 04
Publish and check it
Click Submit, then Publish. Preview alone doesn’t put Velo live. Then open your site in a private window, try the banner, and check that it shows as installed in your Velo dashboard.
HubSpot questions,
answered.
What teams installing on HubSpot ask first.
HubSpot already shows a cookie banner.
Turn HubSpot’s banner off under Privacy & Consent so Velo is the only layer your visitors see. Two banners confuse people, and two consent tools send Google conflicting signals.
Does it cover landing pages and the blog?
The domain-wide header applies to content that inherits those settings. Check page-level overrides and test website pages, landing pages and blog pages on your chosen domain.
What about HubSpot’s own tracking code?
HubSpot’s analytics is not a Google tag, so Consent Mode does not gate it by itself. If compliance requires it, load it through Tag Manager and gate it with the velo_consent_update event. The GTM guide shows the exact trigger.
Will it slow the site down?
The dashboard snippet loads asynchronously. As with any script, measure its effect on your site and check your tag order; asynchronous loading alone does not guarantee consent defaults run before other tags.
Can an AI assistant do this for me?
Yes. Copy the prompt in Install with agents, just below, into Claude, ChatGPT, Cursor or whichever assistant you already use. It carries the steps on this page, the order the tags have to load in, and the checks the agent has to run before it tells you the job is done.
Or hand it
to an agent.
Copy the prompt into Claude, ChatGPT, Cursor or whichever assistant you already use. It carries everything on this page: both routes, the order the tags have to load in, and the checks that prove it worked.
Paste this prompt into your assistant, then provide your site ID and the complete installation snippet or GTM settings from your Velo dashboard.
Working with an agent that reads the web? Point it at veloconsent.com/llms.txt and /install.md for the same context in plain text.
