Skip to main content

Google Consent Mode v2 setup and verification guide

Installation follows one of two paths, and which applies is decided by how Google Analytics fires, not by preference. Expected signal values were measured live on cookietrace.com on 17 September 2026: gcs=G100 before consent, G111 on accept all, G100 on reject all and G101 with analytics only.

Which installation path applies to you

Search the page source for googletagmanager.com/gtag/js?id=G-. If it is present the tag is embedded and path A (direct tag) applies. If only gtm.js?id=GTM- is present, GTM injects GA and path B applies. If both are present, GA is embedded and does not go through GTM, so path A still applies. The most common mistake is choosing the GTM method merely because a GTM container exists; a consent setting made in GTM never sees an embedded tag.

Path A — direct tag

Turn on Google Consent Mode v2 in Banner Design and save; the generated snippet embeds the consent-default block, so no separate gtag block is needed. Three steps are all required: enable and save Consent Mode in the panel, re-copy the snippet and replace the old block on the site, then place the snippet above the Google tag. The block runs synchronously so no cookie is written before consent, and the widget sends the update signal once the visitor chooses.

Path B — GTM

When GTM injects GA, the consent-default block must run before the container. Place it in the page head above the GTM snippet, or use a consent initialisation trigger inside GTM. The decisive test is the same in both cases: the gcs parameter must be present on the first collect request.

Expected Tag Assistant values

In the Consent tab before consent, security_storage is granted and the other six signals are denied. After accept all, seven signals are granted; after reject all, everything except security_storage is denied. Tag Assistant is an interpretation — the evidence is the gcs parameter on the collect request.

Test scenarios and results

Measured with a real browser and a clean profile on cookietrace.com on 17 September 2026.

  • Before consent: 8 collect requests, all gcs=G100, no _ga cookie
  • Accept all: gcs=G111, _ga and _ga_JZXBBVK46B written
  • Reject all: gcs=G100, no _ga cookie, security_storage still granted
  • Analytics only: gcs=G101
  • Marketing only: gcs=G110 (derived from the signal model, not separately measured)
  • Broken setup: no gcs parameter at all

Accuracy boundaries

Consent Mode v2 is not a blocking mechanism; tags load and requests reach Google without cookies. This describes Advanced Consent Mode; in Basic mode tags do not fire before consent, and any legal claim about that needs counsel. wait_for_update: 500 adds a latency budget, analytics numbers drop after correct configuration, and setup cannot be completed remotely because the snippet lives in the customer's HTML.

How Cookietrace works

A single script tag installs in about 3 minutes, directly or through Google Tag Manager. It scans the site for cookies, pixels and storage use, classifies every tracker, shows a consent banner in the visitor's language, and only then allows non-essential tags to run. Recurring deep scans alert you when a new tracker appears.

  • Automatic cookie, pixel and fingerprinting discovery with scheduled re-scans.
  • Granular categories: strictly necessary, functional, analytics, marketing, social.
  • Google Consent Mode v2 and IAB TCF v2.2 signalling out of the box.
  • Optional tracker request blocking stops rejected trackers' requests in the browser.
  • Cryptographically signed, timestamped consent logs retained for 3+ years.

Regulations covered

GDPR and ePrivacy for the EU and UK, KVKK and the 2022 KVKK Cookie Guide for Turkey, CCPA/CPRA for California, plus AI Act Article 50 disclosure support. Banners, retention and proof of consent follow the rules of the visitor's jurisdiction.

Plans and pricing

Pricing is per month in USD, based on the number of domains: Pro: $39/month · Premium: $79/month · Enterprise: custom pricing. Every plan keeps the compliance features; the 14-day trial needs no card.

Company

Cookietrace by Ezeratech Digital (EZERA DIGITAL TECHNOLOGIES FZCO), founded in 2024. Offices: IFZA Business Park, Dubai Silicon Oasis, Dubai (AE) · İstanbul (TR) · London (GB). Interface and support in English, Turkish, Spanish and Italian. Contact: [email protected] (sales), [email protected] (support), [email protected] (privacy).