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 on both the Free and Professional plans. The visitor’s choice is passed only on a site connected to a Cookie Compliance account, because the Cookie Compliance banner is what passes it; in Banner Only mode (no account) no choice is passed. 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, so their code sets no cookies and sends no tracking data (the browser may still download a held script file, but it does not run) — 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 (subject to the two limits below). Withdrawals are saved immediately and take full effect on the next page load, and it applies to traditional sites and modern SPAs alike.

The built-in provider database recognizes 282 patterns across 181 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. Two limits: a script that an already-allowed script adds later is not held (for example a tag that Google Tag Manager fires while Google Consent Mode lets GTM run, so gate those inside GTM), and on the Free plan blocking stops once the site passes its visit limit for the current cycle. 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 every non-essential purpose is held off (only Basic Operations run) until the visitor explicitly opts in. (In Show full banner mode, if Consent on Scroll, Click or Close is on, scrolling, clicking or closing the banner saves the preselected Default Consent Level as that choice.) GPC is a Professional plan feature (a site that already had it on keeps it). 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 plan and a Professional plan. Both include the consent banner and model (Access Levels mapped to Purpose Categories), Update consent, policy links, core Autoblocking, in-app Consent Logs, and Google Consent Mode. Professional adds multi-domain bundles, Meta and Microsoft Consent Modes, GPC, unlimited languages (Free includes one additional language), custom providers/URL patterns, data anonymization, full CSV/Proof export (on Free, the dashboard shows and exports a 7-day Cookie Consent log history, and CSV export in the WordPress plugin needs Professional), unlimited retention, and priority support. See Free 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 Geolocation.

AI assistants (MCP)

Cookie Compliance runs a hosted MCP (Model Context Protocol) server so an AI coding assistant can add the banner instead of writing one by hand. No account is required to start. Endpoint: https://mcp.cookie-compliance.co/mcp. See Connect your AI assistant (MCP) and the MCP page.

Related Articles

Was this article helpful?
YesNo