The cookie banner
built for Drupal.
Drupal sites tend to be the ones where compliance is checked properly. Velo holds up: nothing non essential runs before consent, every choice lands in an exportable audit log, region rules apply by law, and the install is one tag in your theme or your tag manager — no module chain to maintain.
Live in minutes — one tag through Google Tag Manager, or one line in your theme.
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 Drupal
Add the tag to your theme's html template and clear caches, or keep the theme untouched and install through Google Tag Manager. No contributed module, no dependency updates, no patch schedule — it is one script tag, wherever you prefer to own it.
Three steps
on Drupal.
Add the tag
Add the Velo snippet to your theme's html template and clear caches. Or add the Velo template in Google Tag Manager and leave the theme alone.
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 Drupal teams ask before switching consent on.
Why not a Drupal consent module?
A module is one more dependency to update through every core upgrade. Velo is a script tag: it lives in your theme or your tag container, upgrades centrally on our side, and touches nothing in your Drupal codebase.
Does it satisfy a formal GDPR review?
Velo blocks non essential scripts until consent, keeps Reject as accessible as Accept, applies per category choices, and records every consent event in an audit log you can export for the review.
How does it behave behind caching and a CDN?
The banner is client side and consent is evaluated per visitor in the browser, so full page caching keeps working. Nothing about the install depends on Drupal's render pipeline.
What does Consent Mode v2 add for our analytics?
It keeps GA4 and Google Ads measurement legal in the EEA and lets Google model conversions from declined visitors — across Amplio Data client implementations that recovers 20–40% of what consent hides. Measured ranges, not a guarantee.
Works wherever you build
Consent handled.
Signal kept.
A compliant banner on Drupal in minutes,
and the conversions consent hides, modelled back.