SleekView for CookieYes
When a regulator asks for proof, you do not want a screenshot. SleekView turns the wp_cli_cookie_scan and wp_cli_cookies tables into a real auditor-ready grid you never have to leave WP Admin to query.
♾️ Lifetime License available
Local consent logs deserve a real view
CookieYes' WordPress plugin stores consent events into wp_cli_* custom tables and syncs categorised cookies discovered by its scanner. The cloud dashboard summarises that data nicely, but a Data Protection Officer answering a Schrems II review or a UK ICO request needs the raw rows: timestamp, region, banner version, source URL, outcome. SleekView lifts every event into one filterable grid you can hand to an auditor without leaving the admin.
The plugin already collects banner version (v4.0, v4.1), region codes (EU, UK), category combinations (necessary, analytics, all, none), and the source URL where the prompt fired. Those columns are present in the database; what is missing is a sortable view that pivots them together. SleekView surfaces all six fields side by side, lets you filter by outcome, and groups events by URL so a leaky page is one click from being identified.
Crucially, consent records are read-only by default. Editing a logged event would defeat its evidentiary value, so SleekView treats CookieYes log tables the way an audit trail expects: queryable, exportable, and untouched. When the request is for proof of consent at 09:11 on April 25 from /pricing in the EU, that row is on screen in seconds, not buried under three dashboard tabs.
Workflow
From CookieYes log tables to one auditor-ready grid
Point at log tables
Map the columns
Save the daily view
Export on demand
Sample columns
Consent events
wp_cli_cookie_scan, wp_cli_cookies and related CookieYes tables
| Array | Array | Array | Array | Array | Array |
|---|---|---|---|---|---|
| Array | Array | Array | Array | Array | Array |
| Array | Array | Array | Array | Array | Array |
| Array | Array | Array | Array | Array | Array |
| Array | Array | Array | Array | Array | Array |
Comparison
CookieYes dashboard vs SleekView
CookieYes dashboard
- Dashboard summarises, does not enumerate
- Banner version filters are limited
- No grid view of category combinations per event
- Exports come pre-shaped
- Source URL is hidden in tooltips
SleekView
- Reads CookieYes log tables directly
- Filter by banner version and outcome together
- Group events by source URL to spot leaky pages
- Export current filters to CSV
- Saved views for daily compliance review
Features
What SleekView gives you for CookieYes
Auditor-ready rows
When proof of consent is requested, you have the exact row, timestamp, region, and source URL on screen. No screenshots, no spreadsheet rebuild.
Multi-axis filters
Filter by region and banner version at the same time, save the view, and the next compliance review starts where the last one left off.
Per-URL breakdowns
Group by source URL to see where rejection rates spike. Then investigate the page itself, not the chart that summarises it.
Audience
For DPOs and growth teams
Data protection officers
Find the consent record for any user, page, or banner version in seconds. SAR responses move from days of digging to minutes of filtering.
Growth teams
Track how a new banner version changes opt-in rates by region. v4.0 vs v4.1 is two saved views, not a custom dashboard build.
Legal counsel
Filter to the exact rows that match a subject access request, export to CSV, and attach the file to the response without involving engineering.
The bigger picture
Why row-level consent visibility matters
Cookie consent is one of the few areas where WordPress sites are routinely asked to produce evidence on demand. A GDPR Article 7 request, an ICO complaint, or a TCF audit all hinge on showing the exact moment a visitor agreed to which categories on which page, with which banner version. CookieYes already records that data, but the default dashboard rolls it up into charts and totals.
Charts are useful for trends; charts are not evidence. The auditor wants to see the row. SleekView matters here because it removes the gap between what CookieYes captures and what a DPO can produce.
The same plugin powers the proof; SleekView just exposes it the way regulators expect. It also helps growth teams: rejection spikes by URL or banner version are visible long before they show up in conversion reports, so a poorly worded prompt on /pricing gets fixed before it costs three weeks of opt-ins.
Questions
Common questions about SleekView for CookieYes
No, and it does not try to. The CookieYes dashboard is still the right place to manage cookie categories, scanner schedules, and banner design. SleekView covers the row-level inspection the dashboard cannot, which is where DPO and audit work actually happens. Both screens read the same data and stay in sync.
 Consent records should never be edited because the moment they are altered they stop being evidence. SleekView treats CookieYes log tables as read-only by default. You can hide columns, rename labels, and save filters, but the underlying rows the auditor cares about remain exactly as CookieYes wrote them.
 Yes. As long as the local plugin writes the wp_cli_cookie_scan and wp_cli_cookies tables, SleekView reads those rows directly. The cloud account adds banner sync and analytics aggregation, but the consent records themselves live on your site, which is what SleekView surfaces.
 Yes. Region is just a column in the log table, so whatever values CookieYes records, SleekView filters on. If you split EU into individual member states or add a CCPA region for California traffic, those values appear automatically in the filter dropdown.
 Yes. Each subsite gets its own wp_NN_cli_cookie_scan tables and its own SleekView instance pointed at them. Cross-site reporting requires switching subsites, the same way every other multisite-aware plugin works in WP Admin.
 Queries are paginated and indexed-aware. SleekView never pulls millions of rows up front; it requests one page at a time using the same indexes CookieYes already maintains on event timestamp and user hash, so the table stays responsive even on sites with high banner volume.
 Yes, when the visitor is logged in. CookieYes records a user identifier alongside the consent event, and SleekView exposes that as a column you can filter or join against the standard wp_users table to surface display name and email beside the consent record.
 Retention is governed by CookieYes itself and your own policy. SleekView neither prunes nor extends the data, so if your retention is 13 months you will see 13 months of rows. A saved view filtered to the last 90 days is the cleanest way to keep the daily review fast.
 Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- Woocommerce Cart Abandonment Recovery
- Instamojo
- Woocommerce Pdf Product Vouchers
- Site Reviews
- Yith Woocommerce Points And Rewards
- Woocommerce Extra Product Options
- Paystack Woocommerce
- Pretty Links
- Slicewp
- Woocommerce Pdf Invoices Packing Slips
- Woocommerce Distance Rate Shipping
- Restropress
- Yith Woocommerce Gift Cards
- Wpc Grouped Product
- Shipment Tracking