Slimstat writes one row to wp_slim_stats for every pageview, with browser, OS, country, referrer, user role, and visit duration on the same record. Events land in wp_slim_events, outbound clicks in wp_slim_outbound. The default Access Log report shows that data with fixed columns and limited grouping; the Pro Pack adds some sorting and export but still spreads pageviews, events, and outbound activity across separate widgets.

SleekView reads each Slimstat table directly so the same rows become a working surface. Sort by latency to triage a slow page, filter by country plus browser plus referrer to investigate a suspicious traffic burst, or join pageviews to their matching events for a complete picture of a session. Inline edits to excluded IPs and tracked roles update the same Slimstat options the plugin's settings page writes, so exclusions remain the source of truth.

Because the access log is real-time, SleekView paginates against Slimstat's existing indexes and never loads more than the visible page. The External DB add-on works as is: when Slimstat reads from a separate database, SleekView follows the same connection. Saved views like Last hour failed referrers or Outbound clicks from logged-in editors can be scoped per role, so a junior admin gets a clean triage queue without exposure to the full Slimstat settings tree.

Slimstat is one of the few WordPress analytics plugins that keeps the raw access log on your own server, with every pageview, event, and outbound click queryable in SQL if you want it. That makes it useful for the things hosted analytics cannot do: investigating which bot just spiked traffic to /wp-login.php, finding the slowest pages from a specific country, or auditing exactly who triggered a tracked event on a private page. The catch is that the default report UI is a set of widgets, not a database UI.

Anyone who needs the raw data ends up either running ad-hoc SQL queries from phpMyAdmin or buying the Pro Pack to get more flexible filters. SleekView treats Slimstat's tables for what they are. The same access log becomes a sortable, filterable, joinable surface where pageviews and events sit next to each other, exclusions can be edited inline, and triage views can be saved and shared.

The plugin's privacy promise stays intact because nothing leaves the server; you simply get a UI that matches the data Slimstat was already collecting.