Add Velo
to Drupal.
Install the Velo cookie banner and Google Consent Mode v2 on Drupal with one line in your theme template. 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
before the head closes.
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 running Google Tag Manager? Take that route instead ↓
Three steps · about five 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
Add the snippet in your custom theme
In your custom theme’s html.html.twig, paste the complete Velo snippet inside the head, before measurement scripts. Preserve Drupal’s existing head placeholders and markup. Deploy the theme change and rebuild Drupal’s caches. A body block is not a substitute for head placement.
Drupal · theme template
{# In your custom theme’s html.html.twig #} <head> {# Paste the complete Velo snippet from your dashboard here. #} {# Keep the existing head placeholders and theme markup. #} </head>Verified configuration reference · 23 September 2026 Configuration reference checked against the platform documentation. This is not an admin screenshot.
Platform documentation ↗ -
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 ↗
Drupal caches rendered pages aggressively, so flush caches once after the edit. The snippet is identical for every visitor, so page cache and CDN cache both keep working. Region resolution and the decision happen in the visitor's browser and at the edge, not in Drupal.
Still comparing options? Read why teams use Velo on Drupal, or see every supported platform.
Or add the tag
in Tag Manager.
Already have a Google Tag Manager web container on this site? Add Velo from the Community Template Gallery and configure it there. If you need to install the container first, use your platform’s supported integration and check it on the published URL.
- 01Add the Velo CMP templateTemplates→Tag Templates→New→Search Gallery
- 02Create the tagTags→New→Velo CMP template
- 03Review the advanced optionsAdvanced→url_passthrough→ads_data_redaction
- 04Fire it on Consent Initialization – All PagesTriggering→Consent Initialization – All Pages
- 05Enable the consent overviewAdmin→Container Settings→Enable consent overview
- 06Preview, then publishPreview→Submit→Publish
Velo CMP · tag configuration
- Velo site ID
- Copy the exact site ID from your Velo dashboard.
- Banner theme
- Light or Dark
- Velo API endpoint (optional)
- Use the API endpoint shown in your Velo installation settings.
Field names checked against the published Velo CMP template. Use your own site ID and API endpoint.
Velo CMP template ↗Drupal questions,
answered.
What teams installing on Drupal ask first.
Which Drupal versions does this cover?
The steps are written for Drupal 10 and 11 and work the same on 9. Velo is one script tag with no module dependency, so core and module updates do not affect it.
Do I need a dedicated module?
A custom theme can load the snippet without a dedicated Velo module. If using a code-injection module instead, confirm it supports the complete script in the head. Disable overlapping consent tools before going live.
Will Drupal’s caching break it?
No. The snippet is identical for every visitor, so page cache and CDN cache both keep working. Region resolution and the consent decision happen in the visitor’s browser and at the edge, not in Drupal.
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.
From the journal.
Website privacy, in one place.
Scan your site →