Cookie Compliance Capabilities Overview
|
Applies to: All users This article summarizes capabilities documented in detail across the articles linked below. |
This page is a single, consolidated answer to “what does Cookie Compliance support?” Each section below restates a capability that has its own dedicated article with full setup steps — use this page to see the full picture at a glance, and follow the links for configuration details.
Consent Signal Integrations
Cookie Compliance drives the standardized consent signals used by major ad and analytics platforms, so tags adjust automatically as visitors make their choice.
Google Consent Mode v2
Cookie Compliance sets a default consent state on page load and updates it the moment a visitor chooses an Access Level, driving all four Google Consent Mode v2 signals: ad_storage, analytics_storage, ad_user_data, and ad_personalization. Available on both the Free and Professional plans. See Google Consent Mode.
Microsoft Consent Mode
Covers Microsoft Advertising UET, Invest/Curate/Monetize pixels, and Microsoft Clarity, driving the ad_storage / analytics_Storage signals those tags expect. Requires the Professional plan. See Microsoft Consent Mode.
Facebook/Meta Consent Mode
Keeps the Meta Pixel revoked by default and grants it automatically once a visitor accepts Ad Personalization (e.g., the Personalized Access Level). Requires the Professional plan. See Facebook/Meta Consent Mode.
WP Consent API Integration
On WordPress v3.1.0+, Cookie Compliance registers as a Consent Management Platform (CMP) for the WP Consent API, so cooperative plugins (WooCommerce, Google Site Kit, Burst Statistics, WP Statistics, Pixel Manager, AddToAny, AFL UTM Tracker) can read the visitor’s choice directly and self-gate — no custom “trust the banner” code required. On by default; unconditional across both Free and Professional plans, and in Banner Only mode as well as Connected mode. See WP Consent API Integration.
Autoblocking (Pre-Consent Blocking)
Autoblocking is Cookie Compliance’s consent-first safeguard: it holds non-essential third-party scripts and iframes — they don’t execute, set non-essential cookies, or contact their endpoints — until a visitor makes a choice, then releases only what matches the Purpose Categories accepted. This is a fail-closed default: providers stay blocked unless a matching consent is on record. Withdrawals are respected immediately, and it applies to traditional sites and modern SPAs alike.
The built-in provider database recognizes 250 patterns across 165 providers and 4 Purpose Categories (Basic Operations, Content Personalization, Site Optimization, Ad Personalization) out of the box. Self-hosted or uncommon loaders can be added with a custom URL pattern. See Autoblocking Overview.
Global Privacy Control (GPC)
Cookie Compliance can honor the Global Privacy Control (GPC) browser signal as an opt-out preference: when present, the session starts in a conservative default where sale/sharing-related purposes (typically Ad Personalization) are held off until the visitor explicitly opts in. GPC is a Professional plan feature (free accounts that had it enabled before May 2026 are grandfathered). See Global Privacy Control (GPC).
Server-Side Consent Records (Proof-of-Consent)
Beyond the in-app Consent Logs, Cookie Compliance can generate a Privacy Proof-of-Consent record for a form submission — a server-side, exportable record carrying stable identifiers (consent_id, form_id, session_id) plus an HTML snapshot of exactly what the visitor was shown and agreed to. Used for audit evidence, DSR/complaint response, and vendor or legal review. See Proof-of-Consent.
Plans & Deployment
Cookie Compliance is available on a Free (Basic) plan and a Professional plan. Both include the consent banner and model (Access Levels mapped to Purpose Categories), Revoke Consent, policy links, core Autoblocking, in-app Consent Logs, and Google Consent Mode. Professional adds multi-domain bundles, Meta and Microsoft Consent Modes, GPC, multilingual tooling, custom providers/URL patterns, data anonymization, CSV/Proof export, unlimited retention, and priority support. See Basic vs Professional.
Laws & Regions Covered
Cookie Compliance is designed to help meet the requirements of GDPR, CCPA/CPRA, other U.S. state privacy laws, UK PECR, LGPD, PIPEDA, and POPIA. For what each law requires and where it applies, see What laws are covered by Cookie Compliance?