CensusPlugin profiles › Cookie Compliance for WordPress

Cookie Compliance for WordPress – Cookie Consent, GDPR & CCPA

Figures from the Plugin Directory Census · as of 28 Aug 2026

900,000

Active installs, lower bound

Group: 100,000 to 999,999 installs

2

Days since the last release

Group median: 12

4.8

out of 5, from 3,025 ratings

Group median: 4.7 (10+ ratings)

0.0%

Support threads marked resolved, two months

Group: 68.2%

Full profile on wordpress.orgShow on the mapCompare with your own plugins

What is Cookie Compliance for WordPress and who is behind it?

Cookie Compliance for WordPress is a WordPress plugin in the “Analytics and privacy” field, made by Humanityco. It has been listed in the directory since 8 Jul 2013, so for 13 years. It is the only plugin by Humanityco with at least 10,000 installs. With 900,000 to 999,999 active installs it belongs to the 100,000 to 999,999 installs group; its last release came 2 days before the reference date, and it is tested up to WordPress 7.0.

This is how the author describes the plugin on wordpress.org:

“Consent management platform for WordPress — GDPR, CCPA & ePrivacy cookie consent, autoblocking, consent records, Google Consent Mode v2 & GPC.”

Self-description on wordpress.org, retrieved on 10 Sept 2026

When was Cookie Compliance for WordPress last released?

The last release of Cookie Compliance for WordPress came 2 days before the reference date; the group median is 12 days.

Cookie Compliance for WordPress · 2 days today1 month3 months1 year3 years10 years
Each dot is a plugin in the 100,000 to 999,999 installs group, placed horizontally by days since its last release, on a logarithmic scale. The dashed line marks 365 days.

How many installs does Cookie Compliance for WordPress have?

Cookie Compliance for WordPress had 900,000 to 999,999 active installs on the reference date. Within its group, no plugin had a higher band and 5 plugins the same band.

The API reports installs only as a lower bound with one significant figure: 900,000 means at least 900,000 and at most 999,999.

Which WordPress version is Cookie Compliance for WordPress tested with?

No directory notice: tested up to WordPress 7.0, while core stood at 7.1 on the reference date. The notice appears once the field falls below 6.9; that applied to 8.0% of the group.

How does Cookie Compliance for WordPress compare with its group?

The group holds 399 listed plugins. 6.8% of them had a more recent last release than Cookie Compliance for WordPress; 5.3% had no release for more than 365 days.

FigureCookie Compliance for WordPressGroup, 399 plugins
Days since the last release2median 12
Rating4.8 (3,025)median 4.7 (10+ ratings)
Support threads marked resolved0.0%68.2%
Tested up to7.047.6% on 7.1
Requires PHP7.4most often 7.4 (41.6%)

All values on the reference date

Slugcookie-notice
AuthorHumanityco
Active installs900,000 to 999,999
Last release2 days before the reference date
Tested up toWordPress 7.0 · core on the reference date: 7.1
Requires WordPress4.9
Requires PHP7.4
Rating4.8 out of 5 from 3,025 ratings
Support threads, two months0 of 2 marked resolved
Listed since8 Jul 2013
Total downloads41,928,564, updates included
Tagsccpa, consent, cookies, gdpr, privacy

Tags

TagPlugins with 10,000+ installs and this tagRank by installsMedian days since release
ccpa12316
consent8142
cookies10148
gdpr36334
privacy22119

Rank 1 has the highest installation band among plugins with 10,000+ installs and this tag; equal bands share a rank.

Class of 2013

Cookie Compliance for WordPress has been listed since 8 Jul 2013. Of the 131 plugins with 10,000+ installs added in 2013, 82.4% released within the 365 days before the reference date.

Same group, shared tags

Not a recommendation; the same figures for comparison. Alphabetical.

PluginActive installsLast releaseRating
CookieAdmin400,000 to 499,99948 days before the reference date5.0 (4)
Cookiebot by Usercentrics100,000 to 199,99967 days before the reference date4.4 (438)
Disable and Remove Google Fonts100,000 to 199,99943 days before the reference date4.5 (46)
GDPR Cookie Compliance300,000 to 399,99938 days before the reference date4.6 (205)
Gravatar Enhanced100,000 to 199,999164 days before the reference date5.0 (3)
iubenda200,000 to 299,9994 days before the reference date4.7 (396)
Local Google Fonts100,000 to 199,999484 days before the reference date4.6 (83)
Matomo Analytics100,000 to 199,99924 days before the reference date4.6 (177)

Do you maintain Cookie Compliance for WordPress?

If you maintain Cookie Compliance for WordPress, you can link to this profile, for example from your readme or your website. Both snippets show this badge:

Cookie Compliance for WordPress in the Plugin Directory Census 01/2026

HTML

<a href="https://hafenstudios.com/en/census/plugins/cookie-notice/"><img src="https://hafenstudios.com/census/plugins/badge-en.svg" alt="Cookie Compliance for WordPress in the Plugin Directory Census 01/2026" width="220" height="40"></a>

Markdown

[![Cookie Compliance for WordPress in the Plugin Directory Census 01/2026](https://hafenstudios.com/census/plugins/badge-en.svg)](https://hafenstudios.com/en/census/plugins/cookie-notice/)

The image is loaded from hafenstudios.com; as with every request, our server records the usual access data, which is deleted after 14 days. If you prefer not to, use a plain text link.

A value is wrong? Write to moin@hafenstudios.com; a documented correction leads to a new version.

How to cite

hafenstudios (2026): Cookie Compliance for WordPress – Cookie Consent, GDPR & CCPA, profile in the Plugin Directory Census 01/2026, reference date 28 Aug 2026. https://hafenstudios.com/en/census/plugins/cookie-notice/

Source and status

All values come from the full pull of the public wordpress.org API on 28 Aug 2026 (reference time 21:56:30 UTC). The analysis and text on this page are available under CC BY 4.0; the raw values come from the public wordpress.org API and are in the raw data. How the count was made is set out in the method, what the fields do not say under limits. hafenstudios builds WordPress plugins itself, see the conflict of interest. Corrections to moin@hafenstudios.com; a documented correction leads to a new version. From issue 02 this page will also show the change since the previous reference date. Collected and prepared by Horst Wenzel.

Plugin names and trademarks belong to their owners. hafenstudios is not affiliated with the authors named here.