Browse help topics
A banner that meets Google’s requirements.
What Google asks of a consent banner on sites that use its tags, and how Velo’s default banner meets each requirement with no set-up beyond your contact details.
What Google requires, and what Velo does
Google asks sites that use its advertising and measurement tags to collect consent with a banner that meets a set of technical requirements. Velo’s default banner meets each of them as soon as the snippet is installed.
| Requirement | What Velo does by default |
|---|---|
| Set a consent default before any Google tag | The Velo snippet sends the Consent Mode default as soon as it runs, with no other code. Put it first in the <head>, or fire the Velo CMP tag on Consent Initialization – All Pages in Google Tag Manager. |
| Set all four Consent Mode v2 signals | The default and every update set ad_storage, analytics_storage, ad_user_data and ad_personalization. |
| Deny until the visitor chooses where consent is required | In the EEA, the UK and Switzerland, every signal starts as denied. You can require opt-in in every region. |
| Update consent on every choice | Accept, reject and a saved partial choice each send a consent update straight away. |
| Give a real choice | Accept all and Reject sit side by side on the first layer, with the same weight. Visitors can choose by category in the preferences panel. |
| Explain personalised ads and Google’s use of data | The first layer names personalised ads and links to Google’s page on how it uses data, in the visitor’s language. This follows Google’s EU User Consent Policy. |
| Let visitors change their mind | A small icon reopens the banner on every page, so a visitor can change or withdraw consent at any time. |
| Keep a record of consent | Every choice is logged in Records in your workspace. |
| Identify the consent platform | Velo sets its Google developer ID before the default, so Google can see which platform set consent. |
These are Velo’s defaults, not legal advice. Check that the banner wording and categories match your own policies.
What you add: your contact details
The banner needs no configuration to meet Google’s requirements. You only add the details that are yours:
- Your privacy or cookie policy link. Add
data-velo-policy-url="https://example.com/privacy"to the Velo script tag, with your own address. The banner links it, so visitors can see who you are and how to contact you. - Your website. You add it when you set up Velo, and the snippet is made for it.
Keep Enable Google Consent Mode v2 ticked when you install, which is the default. Do not turn off the link to Google’s page on how it uses data.
Basic consent mode sends Google no consent signals, so your Google tags must not load until the visitor consents. See Basic and advanced consent mode.
TCF and Google
Velo sends consent to Google through Consent Mode. Velo is not registered as a CMP for the IAB Transparency and Consent Framework (TCF) yet, so it does not send a TCF string. See Velo and the TCF for the current status. Consent Mode is what Google’s tags read on sites that do not use the TCF.
Check your site meets them
- Run a scan from the Scanner page. The Consent Mode card checks the default, the four signals, the state before consent and the update after Accept all, on every page the scan opens.
- Open a page with
?velo_debug=1in a fresh private window. The debug panel should show the consent default as pass. See Debug mode. - If a Google tag loads before Velo, check first whether it uses Google tag gateway.
- Confirm the result in Google’s Tag Assistant. See Test in Tag Assistant.
If something does not pass, contact Velo support first.