Consent Mode for GTM
Consent Mode v2, set up inside GTM
A common Consent Mode mistake is a default that fires too late. Velo runs inside your container as one tag from the Velo CMP template, fired on the Consent Initialization trigger, which Google runs before any other trigger in the container.
Free for one site and 1,500 monthly sessions. Pro from €7 a month, plus VAT, for unlimited sites.
Run consent inside GTM instead of blocking it
Made for Google Tag Manager
- It only touches your container.
- It’s one script of at most 40KB that doesn’t block the page from rendering, and there’s no app to install or plugin to keep updated.
In every plan, from €0
- Consent Mode v2 advanced, with defaults set before your other tags run
- Regional defaults by country, and Global Privacy Control honoured
- A receipt for every choice, kept in the consent log
- Reject as easy as accept, and a floating preferences button
- Cookie and tracker scan, with choices by category
Rules, records and signals in one place
Some consent setups block Google Tag Manager until a visitor accepts, and every tag in the container goes down with it. Velo runs inside GTM instead: one tag from the Velo CMP template, fired on Consent Initialization – All Pages, sets the Consent Mode v2 defaults before any other tag in the container, and the container loads as usual. There’s no code to add to the page, and your consent setup stays versioned with the rest of the container.
Region rules and records
Set how the banner behaves depending on where the visitor is: opt in consent for the EU and UK, opt out where US state laws call for it. Accept and Reject carry equal weight, visitors choose per category, and every choice is saved to your consent records.
Google Consent Mode v2
Velo sets the Consent Mode defaults before your other tags run, as long as the snippet sits above them or the tag fires on Consent Initialization. Google tags then adjust to each visitor’s choice. Google may model some conversions when its eligibility and traffic conditions are met, but modelling isn’t guaranteed.
There are three steps, and most installs take a few minutes if you can already publish changes to the site.
Everything a consent setup needs
The same banner, records and scans on every plan. Pro adds unlimited sites, unlimited scans and your own logo.
Your banner asks in the visitor’s language and follows the defaults you set for their region.
Every choice is recorded, and Consent Mode v2 passes it on to your Google tags.
How it goes live on Google Tag Manager
Using a different platform? See every supported platform.
Step by step install guide for Google Tag ManagerConsent Mode v2 in one tag
In your container, open Templates → Search Gallery, add the Velo CMP template by veloconsent, and create the tag with your site ID.
- 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.
Consent default before any tag
Velo sets the Google Consent Mode v2 defaults before your other tags run, with everything denied wherever your region settings ask for opt in, and then shows the banner. Google tags adjust to the visitor’s choice, and tags you gate on Velo’s consent event wait until it’s made. Every choice is saved to your consent records.
Velo’s banner with its default look. Your banner’s copy, colours and region settings may differ.Verify, then publish
Check that the consent signals change in Tag Assistant when you accept and when you reject, then publish. Run the same check again whenever you change your tags or banner settings.
From the journal
Notes on cookie banners, Consent Mode and the data that goes missing between them.
Is your cookie banner sending the Consent Mode v2 signal?
Do Canadian websites need Google Consent Mode v2?
Google Consent Mode v2 in Velo: what is new
Common questions about Velo on Google Tag Manager
Why does the Consent Initialization trigger matter so much?
Google runs it before every other trigger in the container. Fire the consent default anywhere later, on Initialization or All Pages, and some tags can beat it, which is the failure auditors and Google’s own diagnostics flag. That’s why Velo’s guide treats it as the one install step you can’t skip.
What are url_passthrough and ads_data_redaction?
These are two advanced Consent Mode settings that the template shows as checkboxes. url_passthrough passes ad click identifiers through URL parameters while storage is denied, which can help Google attribute conversions without cookies. ads_data_redaction removes ad click identifiers from requests while ad_storage is denied, which is the strict EU approach. Each one is a single 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.
Do rejections still send pings?
Yes, in advanced mode, which every Velo plan includes. Google tags adjust to each choice from the first pageview, and visitors who decline can still send cookieless pings. Google may use them to model some conversions when its eligibility and traffic conditions are met. Modelling is not guaranteed, and reports still show fewer observed conversions from visitors who decline.
Free for one site
Banner, scan and consent records for one site, free. Pro from €7 a month, plus VAT, for unlimited sites.