WP GDPR Cookie Consent Pro is the Pro extension of the WPEka Cookie Consent plugin. It writes each consent decision into a plugin-owned table (typically wp_wpl_cookie_consent_logs on most installs) and stores categories, cookies, and policy revisions in companion tables such as wp_wpl_cookie_scan_categories and wp_wpl_cookie_scan_cookies. The default consent log screen renders a flat list, which works for compliance spot checks but is unforgiving when a regulator asks for evidence by region or by policy version.

SleekView reads the consent log table, joins it against the category and cookie tables, and exposes every meaningful field as a column: visitor ID, country, consent state per category, policy version, IP hash, and timestamp. Saved views let the privacy team pin slices like accepted analytics consents this month, rejected marketing consents by region, or all consents recorded against the previous policy version.

Writes route through the plugin's own update path. Toggling a category's default behaviour or correcting a category description writes back through the plugin so the consent banner, the scan results, and the public policy page all stay in sync. Reviewer annotations and owners are kept in a separate SleekView table so the original consent record remains immutable.

Cookie consent is one of the few areas where WordPress site owners are routinely asked to produce evidence in a specific shape, on a deadline, for a regulator they cannot ignore. The plugin already records the right data inside wp_wpl_cookie_consent_logs and its companion tables, but the default UI is designed for spot checks rather than for evidence assembly. That gap shows up the moment a DPO needs to answer questions like which policy version was in force when a specific visitor consented, or how analytics acceptance moved across regions after a banner copy change.

SleekView removes that friction by turning the consent tables into a real grid with proper filters and saved views. Privacy teams gain a per-question view they can revisit, marketing teams gain an honest acceptance-rate report, and developers gain a way to audit category mappings against the live scan output. Consent records remain immutable by default so the regulator-facing chain stays intact.

Annotations live in their own table, and exports follow the saved view exactly. The plugin keeps writing as it always did. SleekView only changes how the recorded data can be browsed and reviewed.