Consent Mode v2,
done right in GTM.
Most Consent Mode installs fail on one detail: the default fires too late. Velo is a CMP that lives where your measurement lives — one template from the GTM community gallery, on the Consent Initialization trigger, so the denied default is guaranteed to land before any tag fires.
Live in minutes — one tag through Google Tag Manager, or one line in your container.
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 Google Tag Manager
Add the Velo template from the community template gallery, enter your site ID, fire it on Consent Initialization – All Pages. The template is reviewed by Google and updates centrally — no code on the page, nothing to maintain, and your consent setup stays versioned with the rest of the container.
Three steps
on Google Tag Manager.
Add the template
In your container, open Templates → Search Gallery, add the Velo Consent Banner template by Amplio Data, and create the tag with your site ID.
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 Google Tag Manager teams ask before switching consent on.
Why does the Consent Initialization trigger matter so much?
It is the one trigger Google guarantees runs before everything else in the container. Fire the consent default anywhere later — Initialization, All Pages — and some tags can beat it, which is exactly the failure auditors and Google's own diagnostics flag. Velo's guide makes this the install's one non negotiable step.
What are url_passthrough and ads_data_redaction?
Two advanced Consent Mode settings the template exposes as checkboxes. url_passthrough lets ad click identifiers survive navigation in URL parameters while storage is denied, preserving attribution. ads_data_redaction additionally drops ad click identifiers on denied traffic — the strict EU stance. Both are one tick in the Velo tag.
How do I verify the setup actually works?
GTM's Preview mode shows it end to end: the Velo tag firing first, every consent signal denied by default from an EEA location, and the update event when a visitor accepts or declines. The install guide walks through exactly what to look for, including enabling consent overview under Admin.
What does a correct install recover?
Denied visitors send cookieless pings and Google models the conversions consent hides — across Amplio Data client implementations, 20–40% of them come back into reporting. Measured ranges, not a guarantee.
Works wherever you build
Consent handled.
Signal kept.
A compliant banner on Google Tag Manager in minutes,
and the conversions consent hides, modelled back.