Verify Consent Mode
The only check that proves anything
A modern CMP always reports that everything is fine. The only check that proves
the real consent state is the gcs parameter on requests to
google-analytics.com/g/collect.
| Value | What it says |
|---|---|
G100 | everything denied |
G111 | ad storage and analytics storage granted |
| missing | Consent Mode is not initialised at all |
The walkthrough
- Open the site in a private window, without touching the banner if there is one.
- Network tab, filter on
collect. - Look at the
gcsparameter of the first request.
On static.ttdlab.com there is no banner: the default denial is never lifted, so
every collection request must carry gcs=G100. That is what
the cookie policy describes.
The defect this check catches
gcs=G111 before any interaction means the consent default block is not
applied — either it is missing, or it comes after GTM in the <head>.
The order is not negotiable: default consent block, then the CMP, then GTM. A tag firing before a state exists behaves as though nothing was denied, and cookies are set before consent is collected — which is precisely what regulators sanction.