Features Pricing GDPR cookie banner Google Consent Mode v2 WordPress plugin Cookiebot alternative For Agencies GDPR ePrivacy About Contact
RO | EN
Start Free →
Necessary

cmplz_statistics Cookie (Complianz) – Full Guide

cmplz_statistics is a technical cookie set by the Complianz plugin (widely used on WordPress sites) to remember whether a visitor accepted the "statistics" cookie category in the consent banner. It doesn't collect traffic or behavioral data itself — it only stores the choice made, so the banner doesn't reappear unnecessarily on every page.

Name
cmplz_statistics
Provider
Complianz
Category
Necessary
Type
HTTP cookie
Lifetime
1 year
Consent
No, but it must be listed in the cookie policy

What is the cmplz_statistics cookie?

cmplz_statistics is a first-party cookie set by Complianz, a popular Consent Management Platform (CMP) used mainly on WordPress sites. It is created as soon as a visitor interacts with the Complianz consent banner and makes a choice regarding the "statistics" cookie category (for example, Google Analytics or other traffic-measurement tools).

The cookie is not set by an external third party but directly by the Complianz code installed on that domain, so it only appears on websites using this plugin for consent management.

What data it stores

The stored value reflects the consent status for the "statistics" category — typically a simple yes/no value or a short decision identifier (e.g. "allow" or "deny"). The exact value format can vary depending on the Complianz version and site configuration.

The cookie stays on the visited site's own domain (it is not sent to external servers) and is read by the Complianz script on each page load to determine whether the banner needs to be shown again or whether statistics scripts can be loaded.

What it is used for

The cookie's purpose is purely functional: it lets the site "remember" the visitor's choice about statistics cookies, avoiding a repeated consent banner on every visit or page navigation.

For the site owner, this cookie is part of the internal mechanism Complianz uses to enable or block analytics scripts (such as Google Analytics) based on the user's decision, supporting compliance with prior-consent requirements.

Does it require consent?

In CookieFix's classification, cmplz_statistics is categorized as strictly necessary, since it doesn't track user behavior but only stores the visitor's own consent preference — a technical function essential for the CMP to work.

  • It does not require prior consent under GDPR and the ePrivacy rules, as it is strictly necessary to deliver the requested service (consent management).
  • It must still be disclosed in the site's cookie policy, with its purpose, category, and duration, for transparency toward visitors and data protection authorities.
  • Site owners should verify Complianz is configured correctly so that the actual statistics scripts (not this cookie) remain blocked until consent is given.

How to block or delete cmplz_statistics

Visitors can delete or block this cookie anytime from their browser settings (Chrome, Firefox, Edge, Safari), in the per-site cookie management section. Deleting it will cause the Complianz consent banner to reappear on the next visit.

For site owners not using Complianz who want an alternative CMP that automatically blocks statistics and marketing scripts until consent is given, a platform like CookieFix can take on that role, preventing third-party scripts from loading before the visitor makes a choice.

Frequently asked questions

No. It is classified as strictly necessary since it only stores the consent preference itself, not tracking data, though it must still be listed in the cookie policy.

The Complianz consent banner will appear again on your next visit, since the system no longer has your previous choice recorded.

Not directly. It only remembers whether you accepted or declined the "statistics" category; actual traffic data is collected separately by scripts like Google Analytics, only if you consented.

Its typical duration is around 1 year, after which the browser removes it automatically and the visitor is asked for consent again.

Updated 7 September 2026 · Information comes from the provider’s public documentation and CookieFix scans; it is not legal advice.