Help centre · Consent Mode v2

Check what your Google tags receive

Set the correct consent defaults, connect visitor choices and test the four core signals in Tag Assistant.

7 min readReviewed 18 November 2026

Know the four signals

Velo maps the visitor’s analytics and advertising choices to Google’s consent signals. Check the signals themselves when debugging; a visible banner is not proof that a tag received them.

SignalPurposeVelo category
analytics_storageAnalytics-related storageAnalytics
ad_storageAdvertising-related storageAdvertising
ad_user_dataSending user data to Google for advertisingAdvertising
ad_personalizationPersonalised advertisingAdvertising

Set defaults before measurement runs

With GTM: configure the Velo CMP template on Consent Initialization – All Pages. Use the exact site ID and API endpoint from your installation settings. Follow the GTM installation guide and inspect tag consent settings in your container.

With a direct installation: consent defaults must be established before Google’s measurement commands, including config and event. Loading an async banner script high in the head does not on its own establish that order. Follow Google’s consent setup instructions for your tag implementation.

Keep one owner for the defaults. An old CMP, a second template or a separate consent script can overwrite the state that Velo sets.

Choose basic or advanced behaviour

ImplementationWhat happens
BasicGoogle tags are held back until consent is given.
AdvancedGoogle tags load with denied consent and can send cookieless measurements.

Choose the implementation that matches your organisation’s policy and configure tags accordingly. Consent Mode does not automatically block every non-Google tag. Pixels, embeds and custom scripts need their own consent controls.

Google’s modelling has eligibility requirements. Passing these tests confirms your implementation’s behaviour; it does not promise modelled conversions or a particular uplift.

Test in Tag Assistant

  1. Open your web container in GTM, choose Preview and connect to the published website. Start with a fresh visitor session.
  2. Before interacting with the banner, inspect the earliest consent event. For an opt-in test, the four signals above should begin as denied.
  3. Accept all categories and inspect the consent update. Verify that analytics and advertising signals become granted.
  4. Repeat in a fresh session and reject optional categories. Their signals should stay denied.
  5. Save a partial choice: allow analytics while refusing advertising. Expect analytics storage to be granted and all three advertising signals denied.
  6. Reopen preferences, withdraw that choice, then reload and navigate to another page. Confirm the update and saved state are applied.

Also inspect the tags and network requests. In advanced mode, a request while consent is denied can be a cookieless measurement; its presence alone does not prove cookies were used. See Google’s Tag Assistant debugging guide for interpreting the consent events.

To confirm that the same state reaches Google Analytics, with a screenshot at each step, follow Check Consent Mode in GA4.

Read gcs and gcd in the network requests

Every request a Google tag sends carries the consent state it ran with. You can read it without Tag Assistant.

  1. Open the published website in a fresh private window and open your browser’s developer tools.
  2. Choose Network, type collect in the filter and reload the page.
  3. Click a request and find gcs and gcd in its address or under Payload.
  4. Make a choice in the banner, reload and read the two values again.

The requests go to a Google domain. With Google tag gateway or server-side tagging they go to your own domain instead. In basic mode no request leaves before the visitor allows a category, so there is nothing to read until then.

What gcs shows

gcs covers two of the four signals. It starts with G1. The next digit is ad_storage and the last one is analytics_storage: 1 means granted and 0 means denied.

These are the values veloconsent.com sent in our test from Spain, an opt-in region, on 18 November 2026.

VisitorgcsMeaning
Has not chosen yetG100Both denied, by Velo’s default
Rejects everythingG100Both denied
Allows analytics onlyG101analytics_storage granted, ad_storage denied
Allows advertising onlyG110ad_storage granted, analytics_storage denied
Accepts everythingG111Both granted

G100 before a choice and after a rejection is the expected result in an opt-in region. If you see G111 there before the visitor has chosen, the tag did not run with a denied default. Check the tag order.

A dash in place of a digit, as in G1--, means no consent state was set for that signal when the tag ran. We did not see it in this test.

What gcd shows

gcd covers all four signals, and it also shows where each state came from. Read the letters and skip the digits between them. The first four letters stand for ad_storage, analytics_storage, ad_user_data and ad_personalization, in that order.

The same test gave these values.

VisitorgcdHow to read it
Has not chosen yet13p3p3p2p5l1All four denied by the default. No choice yet.
Rejects everything13q3q3q2q5l1All four denied by the default and still denied after the choice.
Allows analytics only13q3r3q2q5l1The second letter changed: analytics_storage was granted by the choice.
Allows advertising only13r3q3r2r5l1The three advertising signals were granted by the choice. analytics_storage stayed denied.
Accepts everything13r3r3r2r5l1All four denied by the default, then granted by the choice.

Each letter combines the default with the visitor’s choice.

LetterDefaultAfter the choiceState the tag used
pDeniedNone yetDenied
qDeniedDeniedDenied
rDeniedGrantedGranted
tGrantedNone yetGranted
uGrantedDeniedDenied
vGrantedGrantedGranted
lNoneNoneNever set
mNoneDeniedDenied, with no default before it
nNoneGrantedGranted, with no default before it

With Velo in an opt-in region you should only see p, q and r. An l, m or n in one of the first four places means that signal had no default when the tag ran. Check the tag order and look for a second consent tool.

The value in our test ends with a fifth letter, l. Google does not say what it stands for, so read the first four.

What changes right after a choice

When a visitor chooses or changes a choice, the next requests on that page also carry gcu=1. It marks a consent update. In our test, after Accept all, Google Analytics sent the page view again with gcs=G111 and gcu=1. After a rejection, no new request was sent.

Resolve unexpected consent states

Google tags run before the default consent event.

Check that Velo’s GTM tag uses Consent Initialization, not a page-view trigger. For a direct installation, review execution order and the handling of asynchronous loading. Remove conflicting defaults from other consent implementations.

The state never updates after clicking the banner.

Confirm the correct Velo site ID, check for JavaScript errors and duplicate installations, and inspect a new session. Verify the choice was saved rather than closing a preference panel without saving.

Rejecting advertising still leaves a third-party pixel running.

Consent Mode signals are for supported Google tags. Configure that pixel’s own trigger, consent checks or blocking mechanism, then retest the request before and after the choice. For Meta, follow the Meta Pixel and Signals Gateway guide.

Still stuck?

Tell us where you got to and we will pick it up from there.