CookiePrime emits the Consent Mode default and update commands automatically on every page load, region-aware, before any Google tag fires. All four signals. No code from the merchant.
Google Consent Mode is a signal-transport layer. It tells Google tags — Analytics, Ads, Floodlight, and any tag loaded through Google Tag Manager — whether the visitor has consented to being tracked for analytics and advertising purposes.
Consent Mode is not itself a compliance solution, and CookiePrime does not present it as one. CookiePrime is the CMP: it displays the banner, collects the visitor's choice, and stores the audit record. Consent Mode is the plumbing that carries that choice to Google's tags. The two work together.
Consent Mode v2 defines four signals. CookiePrime sets all four, in both the default and update commands.
CookiePrime's loader emits the default command before any Google tag initializes on the page. A wait_for_update window of 500ms ensures tags do not proceed if they initialize first. The update command fires on every consent change — banner accept, banner reject, drawer toggle, and cross-tab sync.
CookiePrime supports both Consent Mode configurations. The merchant chooses from the CookiePrime dashboard, per domain.
Google tags are paused until the visitor accepts. No pings, no cookies, no measurement until consent is given. This is the default for strict opt-in jurisdictions.
Google tags load immediately with all four signals set to denied. They issue cookieless pings. When the visitor consents, CookiePrime sends update, and tags transition to full measurement.
During the quick onboarding wizard, merchants simply check the "Enable Google Consent Mode" toggle to instantly activate the integration. Configurations can also be updated at any time per domain from the CookiePrime dashboard. No changes to the merchant's site, no GTM edits, no JavaScript from the merchant.
CookiePrime's loader sets the Consent Mode default based on the visitor's detected region, using the framework appropriate to that region:
denied for all four signals. Strict opt-in.granted for all four signals. Opt-out model.The banner appears globally — it is not region-gated. On every page load, the loader emits the region-appropriate default before any Google tag fires. On subsequent page loads, the visitor's stored choice is restored via the update command, and the default is never re-pushed with a different value.
CookiePrime is delivered through the loader on every platform it supports. Consent Mode signals are emitted by the same loader regardless of deployment surface.
Custom GTM tag loads the CookiePrime loader. Consent Mode defaults are emitted by the loader before any other tag fires.
Plugin at wordpress.org/plugins/cookieprime/. Integrated with the WP Consent API, so plugins that read wp_has_consent() respect the visitor's choice.
Shopify app integrates with the Shopify Customer Privacy API via setTrackingConsent(). Consent Mode signals are emitted in parallel by the same loader.
BigCommerce app writes SHOP_CONSENT and bc_consent_* cookies. Consent Mode signals are emitted in parallel by the same loader.
The only code the merchant adds to their site is one script tag. Everything else — developer ID, domain authorization, region detection, Consent Mode defaults, banner rendering, cookie blocking, and update commands — is handled by the loader.
The full reference for Consent Mode configuration, technical banner requirements, debug mode, GTG rules, and platform deployment is in the CookiePrime technical docs.