How does CookieConsentHQ set consent defaults before Google tags?
CookieConsentHQ sets Google Consent Mode defaults synchronously before Google tags run when its loader is correctly placed first. It sends one default command per configured region rule using Google's region parameter, so regional defaults are available from the first Google tag.
Consent defaults tell Google tags which storage and data-use permissions apply before a visitor makes a choice. Google's Consent Mode setup documentation explains that defaults should be established before commands that send measurement data.
CookieConsentHQ uses regional rules to select those starting values. This matters when one location uses an opt-in banner and another uses an opt-out model. The defaults can reflect the applicable configuration without waiting for a visitor to click the banner.
Script placement still matters. If Google tags are hardcoded directly into the page, the CookieConsentHQ loader must appear first in the document head for its blocking controls to run before those tags. Loading the banner after existing tracking code leaves a period when that code may already have executed.
See geo-targeting for the available regional models and custom country, US state and Canadian province rules.
Which consent signals change after a visitor makes a choice?
After a visitor chooses, CookieConsentHQ sends a consent update containing all four Google Consent Mode v2 signals. It also updates functionality_storage and personalization_storage.
The four v2 signals are:
ad_storage: Advertising-related storage.analytics_storage: Analytics-related storage.ad_user_data: Consent for sending user data to Google for advertising purposes.ad_personalization: Consent for personalized advertising.
The two additional signals cover functionality-related and personalization-related storage. CookieConsentHQ also pushes a cchq_consent event to the dataLayer, making the consent event available for Google Tag Manager triggers.
Consent Mode communicates consent states to Google. Google's documentation also places responsibility on the website operator to ensure tags behave according to those states. You should therefore check both the reported signals and what your installed tags do.
For the testing procedure, use How to check Consent Mode v2. This page describes the integration controls rather than repeating the testing guide.
Can I choose Basic or Advanced Consent Mode?
CookieConsentHQ uses Advanced Consent Mode by default, and you can select Basic mode instead. In Advanced mode, Google tags load and may send cookieless pings while consent is denied; in Basic mode, Google tags wait until consent is granted.
Google explains these behaviors in its Consent Mode overview. The choice affects what Google tags do before consent, so select the mode that fits your website's requirements.
CookieConsentHQ also provides the following settings:
wait_for_update: 500 milliseconds by default, configurable from 0 to 5000 milliseconds.ads_data_redaction: Enabled by default.url_passthrough: Disabled by default.
The waiting period gives consent updates time to arrive before Google proceeds with processing affected requests. Advertising data redaction and URL passthrough are separate Google settings, and their documented behavior depends on consent state and tag configuration.
Advanced mode's cookieless requests should be considered when reviewing pre-consent network activity. The mode selection does not establish whether a particular website's implementation meets applicable legal requirements.
Can Google Tag Manager handle the defaults instead?
Yes, CookieConsentHQ offers a Google Tag Manager community template that can set Consent Mode defaults when the banner is loaded through GTM. The template uses Google's setDefaultConsentState API rather than relying on the standalone loader to establish those defaults.
Google's template documentation describes its consent APIs, including setDefaultConsentState and updateConsentState. The distinction matters because consent commands placed into ordinary queued tag operations may execute too late.
CookieConsentHQ's cchq_consent event can also be used in GTM triggers. The event provides a defined point for working with banner consent updates.
The installation method does not eliminate script-order considerations. Hardcoded tracking tags outside GTM are only blocked before execution when the CookieConsentHQ banner script is first in the head.
Use the Google Tag Manager integration when choosing between template-based loading and a direct installation.
How does CookieConsentHQ monitor Consent Mode?
From Starter, the Consent Mode Health Monitor checks signals during every scheduled scan. It reads the gcs and gcd parameters that Google's own network requests carry.
Google doesn't fully document those parameters, so the monitor decodes them using the layout that consent tool vendors and testing guides describe. Reading them shows what Google's requests report, including defaults set through a Tag Manager template, rather than relying only on the banner's displayed state.
Starter scans weekly. Growth, Business and Agency scan daily. Monitoring frequency follows those schedules, so the Health Monitor should not be described as continuously checking every visitor.
The banner can also send consent updates to Microsoft UET, Microsoft Clarity, Meta Pixel and HubSpot when their respective integrations are enabled.
For a separate inspection of one public page, use the free checker.
Is CookieConsentHQ a Google-certified CMP?
CookieConsentHQ supports Consent Mode v2 but is not a Google-certified consent management platform. It also does not support the IAB Transparency and Consent Framework (TCF).
Google's consent management requirements state that certified CMPs integrated with TCF are required for publishers using its covered publisher products to serve personalized ads to EEA, UK and Swiss users. The relevant requirements began in January 2024 for the EEA and UK, and July 2024 for Switzerland.
That certification requirement is distinct from supporting Consent Mode v2 signals. Publishers needing a certified TCF CMP should choose a product that supports those requirements.
This page describes product behavior and Google's published requirements as checked on October 20, 2026. It is not legal advice.