For Google advertisers

Google Consent Mode v2, set up from the start

Velo gives your site a consent banner that meets Google's requirements, with Consent Mode v2 switched on from the first install. The consent default is in the snippet, a scan checks every page, and Velo support is there when a signal goes missing.

Free covers one site and 1,500 sessions a month, with Google Consent Mode v2 included. Read the banner requirements.

Works with the platforms you build on

WordPressShopifyWebflowWixHubSpotPrestaShopDrupalBigCommerceShopwareNext.jsAstroSquare

What you get

Every plan, Free included, gives Google’s tags what they need from a consent platform.

A banner Google accepts

  • The default banner meets Google's technical requirements.
  • The only thing you add is your own privacy policy link.
  • Accept and reject sit on the first layer, with the same weight.
  • Personalised ads are named, with a link to Google's page on how it uses data.
  • A reopen icon lets visitors change their mind at any time.

Consent Mode v2, built in

  • The snippet sets the consent default before your Google tags and updates it on every choice.
  • ad_storage and analytics_storage are set.
  • ad_user_data and ad_personalization are set.
  • Denied by default in the EEA, the UK and Switzerland.
CMConsent Mode v2GPCGlobal Privacy ControlEUGDPRUSUS state laws

When a signal goes missing

A scan checks every page, and if something is wrong, we email you how to fix it. When you write to support, a person replies with a technical first step.


We find the gaps for you

The Scanner checks Consent Mode on every page it opens, and debug mode checks a page as it loads. When a scan finds a problem, such as a tag that ran before consent, we flag it and email you the fix.

Support from people

For Consent Mode and TCF questions, Velo support is your first contact. A person replies with a technical first step within 2 business days on Free, or within 1 business day on Pro, Server and Custom. Every plan includes ongoing troubleshooting.

Four signalsSet by default before any Google tag, and updated on every choice
Eight stepsIn Google Tag Manager, about ten minutes
2 business daysFor a first reply on Free, or 1 business day on Pro, Server and Custom
The Velo CMP tag fires on Consent Initialization, before every other trigger, so the default always comes first and you manage consent next to the tags it controls.
→
Google Tag ManagerThe install we recommend
Install with Tag Manager

Read the guides

How to set up a banner that meets Google's technical requirements, and how to check and fix Consent Mode.


Accept all and Reject sit side by side, personalised ads are named with a link to Google's page on how it uses data, and visitors can change their mind at any time.

The Velo snippet sends the Consent Mode default as soon as it runs, and the Velo CMP template does the same in Google Tag Manager.


Google's banner requirementsEach requirement, what Velo's default banner does about it, and the one thing you add.
Consent Mode v2The four signals, the tag order and how to test them in Tag Assistant.
Debug modeCheck that Velo sets consent before your Google tags, and fix a tag that loads first.
Google tag gatewayServe Google tags from your own domain and keep Velo's consent default first.
Google Tag ManagerInstall the Velo CMP template on Consent Initialization, step by step.
Consent Mode supportHow to reach us, how fast we reply and what support covers.

Set it up in three steps

You go from a new account to Consent Mode v2 you’ve checked without writing a line of consent code. If you’d rather have your account manager do it, agencies and Velo’s team can switch Consent Mode on, set up the banner and install the snippet for you. Ask us.

Set up Consent Mode free

Create your free account

Sign up and add your website. Free covers one site and 1,500 sessions a month, with Google Consent Mode v2 included.

Sign up → Add your website

Install with Consent Mode on

On the Install step, keep Enable Google Consent Mode v2 ticked and choose Google Tag Manager, the install we recommend, then follow the eight steps below. If you don’t use Tag Manager, paste the snippet first in your page’s head. Either way, the consent default is sent with no other code.

Install Velo → Enable Google Consent Mode v2 → Copy snippet

Check every page

Run a scan. The Consent Mode check tests the default, the four signals, the state before consent and the update after Accept all, on each page the scan opens. If something is wrong, we email you how to fix it.

Scanner → Consent Mode

How to enable Consent Mode in Google Tag Manager

We recommend installing Velo with Google Tag Manager. The Velo CMP template fires on Consent Initialization, before every other tag, so the Consent Mode default is always in place before your Google tags. It takes eight steps and about ten minutes.

Turn on the consent overview

In Tag Manager, open Admin, then Container Settings, and tick Enable consent overview under Additional settings. Save. It adds a consent view to the Tags screen, so you can see which tags check consent. It does not switch Consent Mode on by itself.

Google Tag Manager Container Settings with Enable consent overview ticked under Additional settings
Admin → Container Settings → Enable consent overview

Add the Velo CMP template

Open Templates and choose Search Gallery under Tag Templates. Search for Velo CMP, pick the template published by veloconsent and choose Add to workspace, then Add.

The Community Template Gallery in Google Tag Manager showing the Velo CMP template by veloconsent with an Add to workspace button
Templates → Search Gallery → Velo CMP → Add to workspace

Create the Velo CMP tag

Open Tags, choose New, then Tag Configuration, and pick Velo CMP. Paste your Velo site ID and API endpoint exactly as they appear on the Install step in Velo, on its Google Tag Manager tab.

A new Velo CMP tag in Google Tag Manager with the Velo site ID and the Velo API endpoint filled in
Tags → New → Tag Configuration → Velo CMP

Keep Consent Mode on

Leave Basic consent mode unticked. That is advanced consent mode: Velo sets the Consent Mode default for all four signals before any Google tag and updates them on every choice. Tick Require opt-in in every region only if every visitor should start denied, not just where the law requires it.

Velo CMP tag settings in Google Tag Manager with Basic consent mode left unticked, so Consent Mode v2 stays on
Velo CMP → Basic consent mode → Unticked

Steps five to eight, from trigger to publish

These screens are drawn from Google Tag Manager, with the Velo CMP template as published in the Community Template Gallery. Your account and container names will differ. The full install guide for every set-up is in Install Velo in Google Tag Manager.

Open the GTM guide

Fire it on Consent Initialization

Under Triggering, choose Consent Initialization – All Pages, then Save. It fires before every other trigger, so the default is in place before any Google tag. Do not fire the Velo tag on All Pages.

The Google Tag Manager trigger picker with Consent Initialization - All Pages selected
Triggering → Consent Initialization – All Pages → Save

Check your tags' consent settings

Open Tags and the consent overview. Google tags such as the Google tag for GA4 and Google Ads have built-in consent checks and read the four signals themselves, so they need nothing more. Give any non-Google tag Require additional consent for its category.

The Google Tag Manager consent overview listing the Velo CMP tag and the GA4 and Google Ads tags with their built-in consent checks
Tags → Consent overview

Preview it in Tag Assistant

Choose Preview and open your site in a fresh window. On the Consent Initialization event, the Consent tab should show an on-page default for all four signals, denied in an opt-in region. Choose Accept all on the banner, and the next event shows them granted.

Tag Assistant preview with the Consent tab open on the Consent Initialization event, showing ad_storage, analytics_storage, ad_user_data and ad_personalization denied by default
Preview → Consent Initialization → Consent

Submit and publish

Choose Submit, keep Publish and Create Version, give the version a name and choose Publish. Then run a scan in Velo, and the Consent Mode check should pass on every page.

The Google Tag Manager Submit Changes screen with Publish and Create Version selected
Submit → Publish and Create Version → Publish

Set up Velo first, then your Google tags

If your Google tags are missing Consent Mode or TCF signals, contact Velo support first. We set the consent signals on your site, so we can find the cause, and Google support asks for proof that you contacted your consent platform first.

Write to contact@veloconsent.com with Google Consent Mode in the subject. See the privacy notice.


A person replies with a technical first step rather than an automatic acknowledgement.
V
Google Consent Mode supportBusiness days are Monday to Friday, except public holidays in Spain.

Within 2 business days

Within 1 business day

Pro, Server and CustomGet support

Send it to Google Consent Mode support

A person replies with a technical first step, not an automatic acknowledgement.

Your message goes to Velo's Google Consent Mode support. Prefer email? Write to contact@veloconsent.com with Google Consent Mode in the subject. See the privacy notice.

Consent Mode questions

Do I need extra code to set the Consent Mode default?

No. The Velo snippet sends the Consent Mode default as soon as it runs, and the Velo CMP template does the same in Google Tag Manager. Put the snippet first in the head, or fire the template on Consent Initialization – All Pages.

Does the banner meet Google's requirements out of the box?

Yes. Accept all and Reject sit side by side, personalised ads are named with a link to Google’s page on how it uses data, and visitors can change their mind at any time. Add your privacy policy link and you’re done. See Google’s banner requirements.

A scan says a Google tag loaded before Velo. What do I do?

First check whether that tag uses Google tag gateway: open your browser's developer tools, choose Network and reload. If gtm.js or gtag/js loads from your own domain, it does, and the tag gateway guide shows how to put Velo first. If not, move the Velo snippet above your Google tags.

Does Velo support the TCF?

Velo sends consent to Google through Consent Mode. It is not registered as an IAB TCF consent platform yet. See Velo and the TCF for the current status.

How do I enable Consent Mode in Google Tag Manager?

Add the Velo CMP template from the Community Template Gallery, create a Velo CMP tag with your Velo site ID and API endpoint, leave Basic consent mode unticked and fire the tag on Consent Initialization – All Pages. Then check the Consent tab in Tag Assistant and publish. The eight steps above show each screen.

Should I install Velo with Google Tag Manager or the snippet?

Google Tag Manager, if your Google tags already live there. The Velo CMP tag fires on Consent Initialization, before every other trigger, so the default always comes first and you manage consent next to the tags it controls. Without Tag Manager, paste the snippet first in the head of every page.

Who do I contact when Google tags are missing consent signals?

Contact Velo support before Google. We set the consent signals on your site, so we can find the cause, and Google support asks for proof that you contacted your consent platform first. See how to reach support above or write to contact@veloconsent.com.

How fast does Velo support reply?

Within 2 business days on Free and within 1 business day on Pro, Server and Custom, Monday to Friday. Most messages get an answer the same working day, and the first reply is a technical answer rather than an acknowledgement.

Set up from the start

Free covers one site and 1,500 sessions a month, with Google Consent Mode v2 included.