Complianz

What Is Complianz?

Complianz is a privacy and cookie-consent plugin for WordPress that helps website owners comply with data-protection laws such as the GDPR, the ePrivacy Directive, the CCPA, and similar regulations around the world. It generates a cookie banner, a consent-management layer, and the legal documents a site needs, then blocks tracking scripts until a visitor agrees to them. Although consent management is a privacy function, it sits squarely in the analytics and tracking part of a site's stack because its entire job is to govern when analytics, advertising, and other tracking technologies are allowed to run, which is why StackOptic files it under the analytics category.

Complianz is widely regarded as one of the most popular consent-management plugins in the WordPress ecosystem, alongside tools like Cookiebot and CookieYes. It is built specifically for WordPress rather than as a generic JavaScript snippet, which means it integrates directly with the WordPress admin, plugin hooks, and the wider ecosystem of analytics and marketing plugins that a typical WordPress site runs.

The plugin is published by Complianz, a company based in the Netherlands, and is distributed in a free edition through the official WordPress plugin directory plus paid premium tiers that add features such as multi-region consent, more granular script control, and priority support. Because it is region-aware, Complianz can show different consent experiences to visitors depending on where they are located, applying GDPR-style opt-in consent in Europe and opt-out notices in jurisdictions that require them.

Complianz is not a browser extension and not a standalone analytics product. It is server-side WordPress software paired with a small front-end JavaScript layer: the plugin runs inside WordPress and renders a consent banner and script-blocking logic into the pages it serves. That combination of a recognizable front-end script and WordPress-specific asset paths makes it relatively straightforward to detect from the outside.

It helps to frame what Complianz actually does in the daily life of a website. Modern sites load a surprising number of third-party scripts, analytics, advertising pixels, video embeds, social widgets, and chat tools, and most privacy laws now require that the non-essential ones do not run until the visitor has agreed. Manually wiring up that behavior is tedious and error-prone. Complianz exists to automate it: it scans the site, categorizes the scripts it finds, generates the legal text describing them, and then enforces consent so the right scripts fire only after permission is given. For a WordPress site owner without a legal team or a developer on call, that automation is the entire value proposition.

How Complianz Works

Complianz begins with a configuration wizard inside the WordPress admin. The site owner answers questions about which regions they serve, which analytics and marketing tools they use, and how they want consent handled. From those answers the plugin builds a tailored consent configuration rather than a one-size-fits-all banner, and it generates the supporting legal documents, a cookie policy, a privacy statement, and related notices, populated with the specifics of the site.

The core mechanism is conditional script blocking. Complianz intercepts known tracking scripts, Google Analytics, Google Tag Manager, advertising pixels, embedded video, social widgets, and many others, and prevents them from executing until the visitor grants consent for the relevant category. It does this by rewriting or deferring the script tags so that the browser does not run them on load. When a visitor accepts a category, the plugin releases the corresponding scripts; if they decline, those scripts never fire. This is the technical heart of "prior consent" compliance.

Consent is organized into categories such as functional, statistics or analytics, marketing, and preferences. The banner lets visitors accept all, reject all, or open a granular panel to toggle individual categories. Complianz records each consent decision and can log proof of consent, which regulations often require. It also re-prompts visitors when the consent configuration changes or after a defined period, so consent stays current.

Because it is region-aware, Complianz detects (or is configured for) the visitor's jurisdiction and applies the appropriate model: explicit opt-in before scripts run for GDPR regions, opt-out style notices where that is the legal standard, and tailored language for frameworks like the CCPA. The plugin integrates with Google Consent Mode so that Google's tags adjust their behavior based on the visitor's choices rather than being blocked outright, which preserves a degree of measurement while respecting consent.

A useful way to picture the workflow is to follow a single page load on a Complianz-protected site. When the browser requests the page, WordPress renders the HTML with Complianz's consent script included and the third-party tracking scripts held back. The consent banner appears. If the visitor accepts statistics and marketing, Complianz releases the analytics and advertising scripts, which then initialize as if they had loaded normally. If the visitor rejects them, those scripts stay dormant for the entire session, and the analytics platform simply records nothing for that user, or records a privacy-preserving, cookieless signal where Consent Mode is in play. The consent choice is stored so the banner does not reappear on every page.

Under the hood, Complianz leans on WordPress's plugin architecture, hooking into the rendering pipeline to inspect and rewrite output, store settings in the database, and expose an admin interface for ongoing management. This deep WordPress integration is what distinguishes it from platform-agnostic consent snippets, and it is also why its fingerprints show up in WordPress-specific locations.

How to Tell if a Website Uses Complianz

Complianz leaves several reliable fingerprints. Because StackOptic analyzes a URL from the server side, it inspects the same signals you can check by hand with browser tools, View Source, or a detection extension.

The Complianz front-end script. The strongest signal is the plugin's JavaScript, which is served from the WordPress plugins directory at a path like /wp-content/plugins/complianz-gdpr/ (the premium edition uses a closely related folder name). A request to a complianz path under /wp-content/plugins/ is close to definitive.

JavaScript globals and config. Complianz injects a configuration object and helper functions into the page, commonly under a complianz or cmplz namespace (for example a cmplz object or functions and CSS classes prefixed with cmplz-). Seeing cmplz- class names on the banner markup or a cmplz object in the console is a strong tell.

Consent cookies. After a visitor interacts with the banner, Complianz sets cookies that record the consent state, typically named with a cmplz_ prefix (such as cmplz_consent_status or cmplz_marketing). Spotting cmplz_ cookies in DevTools confirms the plugin.

Banner markup and CSS. The consent banner is rendered with recognizable container IDs and classes (again using the cmplz- convention) and loads the plugin's stylesheet from the same plugins path. The banner's HTML structure is a visible fingerprint even before any interaction.

WordPress context. Because Complianz is a WordPress plugin, its presence implies WordPress. The asset paths under /wp-content/plugins/ are themselves a WordPress signal, so detecting Complianz simultaneously confirms the underlying CMS.

Here is how to check each signal yourself:

Method	What to do	What Complianz reveals
View Source	Right-click, "View Page Source"	Script and stylesheet URLs under /wp-content/plugins/complianz-gdpr/, cmplz- banner markup
Browser DevTools	Inspect the banner element and the Network tab	cmplz- classes/IDs, requests to the Complianz plugin path
DevTools Console	Type cmplz or complianz	The plugin's JavaScript object and helper functions
DevTools Application	Open the Cookies panel after interacting with the banner	cmplz_ consent cookies recording the visitor's choices
Wappalyzer	Run the extension on the live page	Identifies "Complianz" under cookie compliance, plus WordPress

A quick command-line check is curl -s https://example.com | grep -i "complianz". If that returns plugin-path references or cmplz markup, you are almost certainly looking at Complianz on WordPress. Because consent banners and analytics are tightly linked, our guide on how to find out what analytics a website uses is a natural companion, as is the broader walkthrough in how to find out what technology a website uses.

It is worth noting how these signals behave on real sites. The consent cookies only appear after a visitor has interacted with the banner, so a first, untouched page load may not show them; the script path and banner markup, however, are present from the start regardless of interaction. Some site owners customize the banner's appearance heavily, but the underlying cmplz- class names and the plugin asset path are generated by the plugin and rarely changed, which keeps them dependable. Because Complianz's job is to block other scripts until consent, server-side analysis is especially useful here: a tool that fetches the unmodified HTML sees both the Complianz layer and the tracking scripts it is holding back, giving a clearer picture than a browser that only reveals scripts after consent is granted.

Key Features

• Consent wizard. A guided setup that tailors the consent configuration to the regions served and the tools in use.
• Conditional script blocking. Holds back analytics, advertising, video, and social scripts until the visitor consents to the relevant category.
• Region-aware consent models. Applies GDPR opt-in, opt-out notices, CCPA language, and other regional rules based on the visitor's location.
• Auto-generated legal documents. Produces a cookie policy, privacy statement, and related notices populated with the site's specifics.
• Google Consent Mode integration. Lets Google tags adjust behavior based on consent rather than being blocked entirely.
• Consent logging. Records proof of consent and re-prompts when the configuration changes.
• Cookie scanning. Detects and categorizes the cookies and scripts a site sets to keep the policy accurate.

Pros and Cons

Pros

• Purpose-built for WordPress, integrating directly with the admin and the plugin ecosystem.
• Automates both the technical blocking and the legal documentation that compliance requires.
• Region-aware, so a single site can serve the correct consent experience worldwide.
• A capable free edition makes basic compliance accessible to small sites.

Cons

• WordPress-only; it does not help sites built on other platforms.
• Misconfiguration can either over-block (breaking analytics) or under-block (risking non-compliance), so setup matters.
• Advanced features and multi-region support sit behind the paid tiers.
• As with any consent tool, it cannot guarantee legal compliance on its own; it is one part of a broader privacy program.

Complianz vs Alternatives

Complianz competes with other consent-management plugins and platforms. The table below compares it with common alternatives.

Tool	Platform	Model	Best for
Complianz	WordPress plugin	Region-aware, deep WP integration	WordPress sites wanting native consent and legal docs
Cookiebot	Platform-agnostic script	Cloud-scanned, automatic blocking	Multi-platform sites needing managed scanning
CookieYes	WordPress plugin + script	Banner and scanning, freemium	Smaller sites wanting a quick banner
OneTrust	Enterprise platform	Full consent and privacy suite	Large enterprises with broad compliance needs
Osano	Cloud consent platform	Managed consent and monitoring	Mid-market and enterprise multi-site setups

Because Complianz frequently governs Google's tags, sites that run it often also run Tag Manager; our guide on how to check if a website uses Google Tag Manager pairs well here. You can also compare Complianz with an audience-measurement tool like comScore to see how a consent layer differs from the trackers it controls.

Use Cases

Complianz is most at home on WordPress sites that need to comply with privacy law without hiring a developer or lawyer for the basics. Small businesses and bloggers use the free edition to add a compliant cookie banner and generate the policies their region requires. Agencies install it across client sites to standardize consent handling and reduce legal risk.

It also suits content publishers running multiple analytics and advertising scripts that must be gated behind consent, ecommerce stores on WooCommerce that need to balance marketing pixels with compliance, and organizations serving visitors across several jurisdictions who need region-specific consent from one plugin. For privacy and compliance teams, Complianz provides the consent logging and re-prompting that auditors expect.

Consider a few concrete scenarios. A European media site running Google Analytics, an ad network, and embedded videos can use Complianz to ensure none of those load until a visitor opts in, satisfying GDPR's prior-consent requirement. A US-based store might use it to present a CCPA-style notice and honor opt-out requests while keeping its conversion pixels firing for consenting users. A global SaaS marketing site might rely on Complianz's region detection to show European visitors an explicit opt-in banner while showing visitors elsewhere a lighter notice, all from a single WordPress installation.

From a sales-intelligence and research perspective, detecting Complianz on a site is itself informative. It signals a WordPress site whose owner is actively managing privacy compliance, which often correlates with European traffic or a privacy-conscious audience. For vendors selling privacy, analytics, or marketing tools, that context helps qualify and segment prospects, and surfacing it automatically across many domains is exactly the kind of insight a technology-detection scan delivers in seconds.

Frequently Asked Questions

Is Complianz an analytics tool?

Not exactly. Complianz is a consent-management plugin, but it is filed under analytics and tracking because its purpose is to control when analytics and other tracking scripts are allowed to run. It does not measure traffic itself; instead it governs tools like Google Analytics, deciding whether they fire based on the visitor's consent. That gatekeeping role over analytics is why it belongs in this category.

Can you tell if a site uses Complianz for free?

Yes. View the page source and look for script or stylesheet URLs under /wp-content/plugins/complianz-gdpr/, banner markup using cmplz- class names, or a cmplz object in the DevTools console. After interacting with the banner, check the Cookies panel for cmplz_ consent cookies. Free tools like Wappalyzer also identify Complianz, and a single curl -s URL | grep -i complianz command works from any terminal.

Does Complianz only work with WordPress?

Yes. Complianz is built as a WordPress plugin and relies on WordPress hooks, the admin interface, and the plugins directory. It is not available as a standalone snippet for arbitrary platforms. Sites on other systems use platform-agnostic alternatives such as Cookiebot or enterprise platforms like OneTrust, while WordPress sites benefit from Complianz's deep, native integration.

What is the cmplz prefix I see in cookies and code?

cmplz is Complianz's internal namespace, a shortened form of the product name. The plugin uses it for JavaScript objects, CSS classes on the consent banner (such as cmplz-banner), and the names of the cookies that store consent state (such as cmplz_consent_status). Spotting the cmplz or cmplz_ prefix in code, markup, or cookies is one of the clearest ways to recognize the plugin.

Does Complianz guarantee GDPR compliance?

No tool can guarantee legal compliance on its own. Complianz provides the technical mechanisms, consent blocking, region-aware banners, logging, and generated policies, that support compliance, but proper configuration and a broader privacy program are still required. It substantially reduces the manual work of implementing prior consent and documentation, which is why it is popular, but organizations should still review their setup against the regulations that apply to them.

Want to identify Complianz and the rest of a site's stack automatically? Run any URL through StackOptic at https://stackoptic.com.