Census › Plugin profiles › WP Consent API
WP Consent API
Figures from the Plugin Directory Census · as of 28 Aug 2026
200,000
Active installs, lower bound
Group: 100,000 to 999,999 installs
9
Days since the last release
Group median: 12
5.0
out of 5, from 2 ratings
Group median: 4.7 (10+ ratings)
100.0%
Support threads marked resolved, two months
Group: 68.2%
Full profile on wordpress.orgShow on the mapCompare with your own plugins
What is WP Consent API and who is behind it?
WP Consent API is a WordPress plugin in the “Analytics and privacy” field, made by Rogier Lankhorst. It has been listed in the directory since 6 Feb 2020, so for 6 years. It is the only plugin by Rogier Lankhorst with at least 10,000 installs. With 200,000 to 299,999 active installs it belongs to the 100,000 to 999,999 installs group; its last release came 9 days before the reference date, and it is tested up to WordPress 7.1.
This is how the author describes the plugin on wordpress.org:
“Simple Consent API to read and register the current consent category.”
Self-description on wordpress.org, retrieved on 10 Sept 2026
When was WP Consent API last released?
The last release of WP Consent API came 9 days before the reference date; the group median is 12 days.
How many installs does WP Consent API have?
WP Consent API had 200,000 to 299,999 active installs on the reference date. Within its group, 139 plugins had a higher band and 79 plugins the same band.
The API reports installs only as a lower bound with one significant figure: 200,000 means at least 200,000 and at most 299,999.
Which WordPress version is WP Consent API tested with?
No directory notice: tested up to WordPress 7.1, 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 WP Consent API compare with its group?
The group holds 399 listed plugins. 36.1% of them had a more recent last release than WP Consent API; 5.3% had no release for more than 365 days.
| Figure | WP Consent API | Group, 399 plugins |
|---|---|---|
| Days since the last release | 9 | median 12 |
| Rating | 5.0 (2) | median 4.7 (10+ ratings) |
| Support threads marked resolved | 100.0% | 68.2% |
| Tested up to | 7.1 | 47.6% on 7.1 |
| Requires PHP | 7.4 | most often 7.4 (41.6%) |
All values on the reference date
| Slug | wp-consent-api |
|---|---|
| Author | Rogier Lankhorst |
| Active installs | 200,000 to 299,999 |
| Last release | 9 days before the reference date |
| Tested up to | WordPress 7.1 · core on the reference date: 7.1 |
| Requires WordPress | 5.0 |
| Requires PHP | 7.4 |
| Rating | 5.0 out of 5 from 2 ratings |
| Support threads, two months | 1 of 1 marked resolved |
| Listed since | 6 Feb 2020 |
| Total downloads | 982,554, updates included |
| Tags | api, compliance, consent, cookies, privacy |
Tags
| Tag | Plugins with 10,000+ installs and this tag | Rank by installs | Median days since release |
|---|---|---|---|
| api | 9 | 1 | 34 |
| compliance | 7 | 1 | 38 |
| consent | 8 | 3 | 42 |
| cookies | 10 | 2 | 48 |
| privacy | 22 | 2 | 19 |
Rank 1 has the highest installation band among plugins with 10,000+ installs and this tag; equal bands share a rank.
Class of 2020
WP Consent API has been listed since 6 Feb 2020. Of the 150 plugins with 10,000+ installs added in 2020, 87.3% released within the 365 days before the reference date.
Same group, shared tags
Not a recommendation; the same figures for comparison. Alphabetical.
| Plugin | Active installs | Last release | Rating |
|---|---|---|---|
| Cookie Compliance for WordPress | 900,000 to 999,999 | 2 days before the reference date | 4.8 (3,025) |
| CookieAdmin | 400,000 to 499,999 | 48 days before the reference date | 5.0 (4) |
| Cookiebot by Usercentrics | 100,000 to 199,999 | 67 days before the reference date | 4.4 (438) |
| Gravatar Enhanced | 100,000 to 199,999 | 164 days before the reference date | 5.0 (3) |
| Statify | 100,000 to 199,999 | 21 days before the reference date | 4.8 (51) |
Do you maintain WP Consent API?
If you maintain WP Consent API, you can link to this profile, for example from your readme or your website. Both snippets show this badge:
HTML
<a href="https://hafenstudios.com/en/census/plugins/wp-consent-api/"><img src="https://hafenstudios.com/census/plugins/badge-en.svg" alt="WP Consent API in the Plugin Directory Census 01/2026" width="220" height="40"></a>
Markdown
[](https://hafenstudios.com/en/census/plugins/wp-consent-api/)
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): WP Consent API, profile in the Plugin Directory Census 01/2026, reference date 28 Aug 2026. https://hafenstudios.com/en/census/plugins/wp-consent-api/
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.
