✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Matomo Analytics

SleekView reads the matomo_log_visit, matomo_log_link_visit_action and matomo_log_conversion tables that the Matomo for WordPress plugin keeps on the same database, and renders them as sortable, filterable tables inside WP Admin.

♾️ Lifetime License available

SleekView table view for Matomo Analytics

The data is already in your database. Read it like one.

Matomo for WordPress embeds the full Matomo tracker inside the WordPress install and writes hits to a set of matomo_log_* tables in the same database. Visits land in matomo_log_visit, individual actions in matomo_log_link_visit_action, conversions in matomo_log_conversion. The Matomo admin renders those tables as the familiar Matomo reports, which are powerful but laid out as their own UI, with their own filters, separate from anything else in WP admin.

SleekView reads the same matomo_log tables directly and joins them to matomo_log_action for readable URL labels and matomo_goal for goal names. One row per visit shows landing URL, referrer source, country, device type, action count and goal hits as columns. Sort by action count to find the most engaged sessions. Filter to a campaign source, group by post URL, search across referrers, all from a grid that lives alongside the posts and forms those visits land on.

Because the data lives in standard MySQL tables on the same database, queries hit Matomo's existing indexes and respect Matomo's archive logic where useful. Filters apply per view, saved views can be scoped per role, and the table sits inside WordPress so an editor never needs to learn the Matomo UI just to read traffic for their own posts.

Workflow

From matomo_log tables to a real analytics grid

1

Connect the log tables

SleekView detects Matomo for WordPress and registers matomo_log_visit, matomo_log_link_visit_action and matomo_log_conversion as sources, plus matomo_log_action and matomo_goal lookups for readable labels.
2

Build the columns you actually want

Pick landing URL, referrer, country, device type, action count, goal hits and visit duration. Skip Matomo's preset reports and design the row that matches the question an editor or marketer is asking.
3

Save editorial and ops views

Pin views like Top posts this week, Organic traffic only, Conversions by source or Mobile sessions over 2 minutes. Editors, marketers and clients each open the queue that matches their role.
4

Group and export

Group rows by post URL, country or goal for editorial reports. Export any filtered view to CSV with the columns and grouping configured.

Sample columns

A typical Matomo visits table

One row per visit with landing URL, source, country, device, action count and conversion status.
Source: wp_matomo_log_visit, wp_matomo_log_link_visit_action, wp_matomo_log_conversion
Landing URL Source Country Device Actions Goal
/blog/dpia-checklist/ google DE desktop 7 Newsletter
/pricing/ twitter NL mobile 3
/blog/cookie-banners/ direct FR desktop 12 Contact
/landing/spring-sale/ newsletter GB tablet 2 Bounced
/docs/install/ google US mobile 5

Comparison

Default Matomo reports vs SleekView

Default Matomo reports

  • Matomo's UI is powerful but lives outside the standard WP admin chrome
  • Editors need to learn a separate report UI to read traffic for their own posts
  • Mixing Matomo metrics with WP post or user data requires manual export
  • No native way to scope a view per role using WordPress capabilities
  • Sharing a read-only snapshot means a Matomo user with its own permissions

SleekView

  • Visits, actions and conversions as one WP-native sortable table
  • Filter by source, country, device, goal or any matomo_log column
  • Group rows by URL, post, category or goal for editorial reports
  • Read-only sharing gated by WordPress capability, not a Matomo user
  • Same database, same indexes, no separate sync or export pipeline

Features

What SleekView gives you for Matomo Analytics

WP-native visits grid

Render matomo_log_visit joined to matomo_log_action and matomo_goal as a sortable table inside WP admin. Editors never leave the screen they already work in.

Multi-dimensional filtering

Stack source, country, device, goal and date filters in one panel. Get the exact slice you want without rebuilding a Matomo segment in a separate UI.

Editor-friendly views

Hand each editor a column set scoped to their author URLs or category prefix. They see traffic for the posts they own, not the rest of the analytics dashboard.

Audience

Who uses SleekView for Matomo Analytics

Editorial teams

Read post traffic, top sources and engagement directly in WP admin. Writers see their own articles without learning the Matomo report tree or asking an analyst for a screenshot.

Marketing leads

Build a goal-funnel view combining matomo_log_conversion with utm-campaign data. Track campaign performance per source without exporting CSVs into a separate tool.

Privacy-first agencies

Run a self-hosted Matomo for clients who refuse third-party trackers, then expose a SleekView table that scopes per role so clients only see their own properties' rows.

The bigger picture

Why self-hosted analytics still needs a WP-native table

Matomo for WordPress is the GDPR-friendly answer to Google Analytics for teams that want to keep their visitor data on their own database. The trade-off is that Matomo's UI is its own world, with its own report types, its own user system and its own filters, sitting next to but not inside the WP admin where editors and marketers actually work. SleekView closes that gap.

The same matomo_log tables that Matomo's reports read become a sortable, filterable table inside WordPress, with WP capabilities deciding who sees what. An editor reads their own post traffic next to their post list. A marketer reads a goal funnel next to the form plugin that filled it.

A privacy officer reads anonymization coverage next to the policy page itself. Same data, same indexes, same numbers, but a query surface that respects how a WordPress team thinks.

Questions

Common questions about SleekView for Matomo Analytics

The matomo_log_visit, matomo_log_link_visit_action and matomo_log_conversion tables Matomo for WordPress writes inside your WordPress database, plus the matomo_site, matomo_goal and matomo_log_action lookup tables for readable labels. No external API is involved.

 

No. Since Matomo for WordPress writes its log tables in the same database as WordPress, SleekView reads those tables directly and never round-trips through the Reporting API. Queries respect Matomo's existing indexes, and there is no extra HTTP call to schedule.

 

For raw counts over a date range, yes. SleekView counts rows in the same tables Matomo's reports aggregate. Matomo's archive-based reports add deduplication and visitor stitching across visits; SleekView can use the archive tables directly if you prefer pre-aggregated values over raw log scans.

 

Yes. matomo_log_conversion stores idgoal, revenue and visitor identifiers. Add idgoal as a filter to the grid to surface only converting visits, then group by source or landing URL to see which posts drove which goal.

 

The deepest integration is with Matomo for WordPress, since the tables live in the same database. For an external self-hosted Matomo, SleekView can read its database directly if your WordPress server can reach it; otherwise the Reporting API route is the right tool, and SleekView's job ends at the WordPress-side tables.

 

Yes. SleekView reads whatever Matomo has stored. If anonymize-IP, do-not-track or other privacy options are on in Matomo, the data already lands anonymized; SleekView surfaces the same values without re-identifying anything. Scoping a view per role uses WordPress capabilities, not a separate Matomo user.

 

Queries hit indexed columns on the matomo_log tables (idvisit, visit_last_action_time, idsite, idaction_url) and pagination is built in. For high-traffic sites where raw scans get expensive, you can point the grid at Matomo's pre-built archive tables instead of the raw logs.

 

Yes. Saved views can be exposed via a read-only URL gated by WordPress capability, and any filtered set exports to CSV. The stakeholder gets the table without needing a Matomo login, while raw Matomo access stays gated by the plugin's own permissions.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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