WP Consent API is the layer maintained by Really Simple Plugins and contributors so that any plugin can declare which consent categories it relies on and any consent banner can read the current visitor decision through a single, well-defined function. It registers consent types (functional, statistics, statistics-anonymous, marketing, preferences), exposes a global cookie hook and tracks which active plugins declare support and which do not.

The trade-off is that the plugin's admin focuses on registration and debug logging. The data needed to answer real questions, how many active plugins declare consent support, which categories they touch, which banner plugin is paired with WP Consent API, when registrations were added, sits across the active-plugin list, the registered consent types and the options metadata.

SleekView Charts pivots those stores. A Number card counts active plugins declaring WP Consent API support. A Pie splits declared categories across functional, statistics, marketing and preferences. A Bar groups sites by paired banner plugin so multisite coverage of a specific consent banner is visible. An Area trends registration updates over time so a fleet rollout appears as a visible curve.

WP Consent API is doing important infrastructure work: a shared function any plugin can call to know whether the visitor has consented and any banner can call to write the decision. The plugin's own admin is intentionally small because the value is at the protocol level. The questions privacy officers and developers ask, though, are coverage-shaped.

How many active plugins on this site declare support, what categories does the stack actually touch, is a consent banner paired correctly, did the last update change category declarations. SleekView Charts pivots the registries and the active-plugin list to answer those in one screen. Same plugin, same protocol, but a coverage surface that respects the questions a real privacy review asks.