SleekView Kanban for Matomo Analytics
Matomo gives you full Google-Analytics-class data, fully owned by you. SleekView Kanban turns Matomo visits, goals, and segments into a triage board inside WordPress so the team can act on the numbers without ever calling the cloud.
♾️ Lifetime License available
An owned-data board for Matomo
The Matomo Analytics WordPress plugin embeds the tag, exposes the Matomo reporting UI in an iframe, and lets you point at either a self-hosted Matomo or Matomo Cloud. When Matomo is self-hosted alongside WordPress, the visit log and goal conversion tables sit in the same database cluster, which means SleekView can read them directly without an API call.
SleekView Kanban points at the Matomo matomo_log_visit or matomo_log_conversion tables and renders one card per visit or conversion. A workflow status column gets added next to the row so triage state lives where the data lives. Cards show the visitor country, the entry page, the referrer, the goal name, and the goal revenue pulled straight from Matomo.
Dragging a card writes the new status to WordPress through the REST API. Matomo keeps tracking and reporting in its own UI, the visit log keeps growing, and the workflow column carries the team's progress without ever leaving your database. Fully owned analytics, fully owned workflow.
Workflow
From Matomo table to kanban board
Pick the Matomo source table
Add the workflow column
Pick card fields and columns
Drag to update the row
Sample board
Matomo goal conversions as a kanban board
Comparison
Matomo reports vs SleekView Kanban
Matomo reporting UI
- Matomo's UI is powerful but lives in an iframe inside WordPress, with no workflow column
- Per-visit and per-conversion triage state has no home in Matomo's standard reports
- Segments are great for filtering but cannot carry status or owner information per row
- Multiple editors cannot easily collaborate on triage inside the Matomo dashboard
- There is no drag-and-drop view at all, so workflows always live outside Matomo entirely
SleekView Kanban
-
Reads
matomo_log_visitandmatomo_log_conversiondirectly with no API call - Helper adds a workflow status column to the Matomo tables without disturbing core schema
- Card fields cover visit datetime, country, entry page, referrer, goal name, and revenue
- Drag updates use the REST API and respect a configurable capability per view
- Self-hosted Matomo and Matomo Cloud are both supported through the WordPress plugin
Features
What SleekView Kanban gives you for Matomo Analytics
Group by any visit column
Pick the workflow status column you added, or any existing column such as country, channel type, or campaign name from the Matomo tables. SleekView reads the distinct values and turns them into kanban columns with your colors.
Drag writes the Matomo row
Moving a card updates the underlying Matomo row through a capability-checked REST endpoint. The change is visible in every SleekView and in any custom Matomo segment that references the workflow column.
Goal revenue on the card
When Matomo tracks goal revenue, that value appears on the card next to the goal name and entry page. Sort each column by revenue to focus a board on the highest-impact conversions without writing a custom Matomo segment.
Audience
Where Matomo teams use it
Goal conversion follow-up
Sales reviews fresh goal conversions on a board grouped by follow-up status. High-revenue goals sort to the top of New, move through Qualified and Followed up, and end in Won once the deal closes in the CRM.
Visit triage and bot review
Group a board by referrer or country to spot suspicious visit patterns. Suspicious visits move through Reviewed and Excluded so future Matomo segments can filter them out of campaign reports.
Channel attribution review
Group by campaign name to see which channels are landing converting traffic. Drag cards through the attribution workflow to surface winning channels and demote ones that look promising but never convert.
The bigger picture
Why an operational board belongs inside owned analytics
The reason teams choose Matomo over Google Analytics is data ownership. Every visit, every goal, every event stays in your database, which means you can build whatever workflow you need on top of it without asking a cloud product for permission. SleekView Kanban is the most useful expression of that ownership for a working team.
The board reads the same tables Matomo writes, attaches a workflow column next to the metric, and lets editors drag cards to update state. Nothing leaves your infrastructure, nothing breaks Matomo's reports, and nothing depends on an external API. Compare that to the alternative, which is to export conversions from Matomo, paste them into a spreadsheet, and lose the link back to the row that produced the number.
Within a sprint or two the spreadsheet has drifted, the team is making decisions based on a stale snapshot, and the data ownership advantage of self-hosting Matomo gets thrown away the moment the analyst opens Excel. Putting the workflow column on the row preserves the ownership story end to end. The metric lives in your database, the action on it lives in the same row, and the board is just a view over rows you already own.
Questions
Common questions about SleekView Kanban for Matomo Analytics
No. SleekView reads directly from the Matomo log tables in the database, which means there is no API call on render and no risk of hitting Matomo's rate limits. For Matomo Cloud, SleekView reads from a local sync table populated on a configurable cron schedule.
In a column added to the Matomo table itself for self-hosted installs, or in a local sync row for Matomo Cloud installs. Either way the data stays inside your database and is not synced back to any cloud product through the workflow column.
Matomo's archiving leaves the log tables intact and operates on a separate archive table, so the workflow column on the log rows is unaffected. Sites that prune the log table after a long window can configure SleekView to keep the workflow rows for as long as needed.
Yes. The view editor supports any column comparison including idsite, campaign name, channel type, and date range. A campaign board can match a specific UTM campaign and a date window without rewriting the underlying view.
Yes. The REST endpoint that handles drag updates is gated by a capability you configure per view, defaulting to manage_options. Editors and analysts can be allowed to triage rows on a board without gaining access to the Matomo plugin settings.
Yes. For Matomo Cloud installs, SleekView ships a sync template that pulls visits and conversions through the Matomo Reporting API into a local table. The board reads from the local copy and the workflow column lives there, fully owned by WordPress.
Yes. Any column in the Matomo log tables, including custom_dimension_1 through custom_dimension_5 and the custom_var fields, can be added as a card field. The card layout supports up to six fields with sensible formatting applied.
No. SleekView issues paginated, indexed queries on the columns you group and filter by, and those queries do not contend with Matomo's write path. We tested on Matomo databases of tens of millions of visits with no measurable impact on the tracking endpoint.
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 checkout