Borlabs Cookie is the German market leader for consent on WordPress. It models the world as service groups (essential, functional, statistics, marketing), each containing services with their own scripts, and pairs that with a content-blocker system that prevents embeds from loading until the visitor opts in. Consent decisions, service-level acceptance and content-blocker unblock events all live in the plugin's custom tables.

The plugin's admin gives a clean per-service report and a settings tree for groups and content blockers. What it doesn't surface is the shape of the consent posture as one queryable list. Following one visitor across service groups, isolating YouTube unblock events, or filtering one banner-variant change to compare conversion all require a CSV export today.

SleekView reads the Borlabs consent, service and content-blocker tables directly. Sort by decision_date to see the last hour. Filter by service_group to isolate marketing opt-ins, by blocker_service to focus on YouTube friction, by site to compare client installs. The plugin still owns the banner and the content blockers. SleekView only adds the sortable triage surface.

Borlabs Cookie models the consent world precisely: service groups, services and content blockers, each with their own data. The plugin's own report is thorough but tab-shaped, and it stops at the boundary of one screen. Privacy officers and content leads want a queryable consent log: filterable by group and service, sortable by date, exportable for auditors and content reviews.

SleekView reads the same tables Borlabs already maintains and renders them as one sortable workspace. Same plugin, same banner, same logs, but a reading surface that matches how DPIA evidence and content decisions actually get made.