COKIQ docs

Basic vs Advanced Consent Mode

Choose basic or advanced Google Consent Mode v2 per site in COKIQ, see what each mode sends to Google, and test it with Tag Assistant.

Best for

Site owners, marketers and agencies who run GA4, Google Ads or Google Tag Manager behind the COKIQ banner.

What the report shows

These are the product-side evidence areas COKIQ can surface when the site has the required scan, banner, consent log, and blocker data.

Basic (default for existing sites)

COKIQ holds gtag.js and the GTM container until the visitor accepts analytics or marketing. Before that, no Google tag loads and nothing is sent to Google. If the visitor declines, Google tags never load on that visit.

Advanced

Google tags load straight away. COKIQ sets ad_storage, analytics_storage, ad_user_data and ad_personalization to denied before any tag runs, so Google tags send cookieless pings only. Google can then model conversions for visitors who decline.

Same in both modes

Denied defaults are set first (with wait_for_update 500 ms), the consent update is sent after every choice, the cokiq_consent_update event is pushed to the dataLayer, and the choice is logged as evidence.

Setup steps

Step 1

Open Banner settings

In the COKIQ dashboard, open Banner, pick the domain and find the Google Consent Mode v2 card.

Step 2

Pick a mode and save

Choose Basic or Advanced and save. The live script for that domain changes on the next page load; no new embed code is needed.

Step 3

Keep the COKIQ script first

Load the COKIQ script before your Google tag or GTM container (top of <head>, or the COKIQ GTM template on the Consent Initialization trigger).

Step 4

Test with Tag Assistant

Open tagassistant.google.com, connect your site, and check the Consent tab: the default state should show all four signals denied, and an update should appear after you click a banner button. In basic mode the Google tag only appears after you accept.

Step 5

Compare with our demo

Our public demo pages show both modes side by side: cokiq.com/demo/consent-mode/basic and cokiq.com/demo/consent-mode/advanced.

Implementation checklist

COKIQ script loads before Google tags
Default consent shows denied for ad_storage, analytics_storage, ad_user_data, ad_personalization
Update fires after Accept, Reject and Save
Basic: gtag.js / gtm.js not requested before consent
Advanced: gtag.js requested on load, pings carry gcs=G100 until consent

Important boundaries

Advanced mode sends cookieless pings to Google before consent. Check with your legal adviser whether your region and policy allow that; if unsure, use basic.
Basic mode can only hold Google tags that load through a script tag added by code (the standard GTM snippet, or our GTM template). A plain <script src="googletagmanager.com/gtag/js"> written in the HTML must be marked type="text/plain" data-cokiq="google" data-src="..." so COKIQ can release it.
Consent Mode does not make a site compliant on its own. Your banner text, categories and tags still need review.

FAQ

Which mode should I choose?

If you run Google Ads and want conversion modelling, and your legal adviser accepts cookieless pings before consent, choose advanced. If you want nothing sent to Google before consent, choose basic.

Did my existing site change?

No. Sites created before this option keep basic behaviour (Google tags held until consent) until you switch.

Does this work with Google Tag Manager?

Yes. With the standard GTM snippet or the COKIQ GTM template, basic mode holds the container and advanced mode lets it load with denied defaults.