Mautic is open-source marketing automation that most teams self-host (or run on a managed Mautic install). The Mautic Integration WordPress plugin's job is to inject the Mautic tracking script, optionally authenticate via OAuth and bridge WordPress form submissions into Mautic segments and campaigns. Locally that means the Mautic base URL, OAuth client credentials, the tracking-script flag, per-form mappings and an optional identify/event log persisted to wp_options and wp_postmeta.

Mautic's own UI handles segmentation and reporting on the Mautic side, which is exactly where it belongs. The WordPress plugin admin shows the configuration screen and a connection check. It does not aggregate identify calls, it does not chart event volume per segment, and it does not show whether the tracking script is firing on the right pages. The data is in the plugin's option store and event log; the surface to read it is missing.

SleekView Charts reads those storage paths directly. A Number card anchors weekly identify calls. A Pie distributes events across mapped Mautic segments. A Bar groups form bridges by source plugin. An Area trends events over time. Same Mautic plugin storage, organised as a one-screen bridge dashboard.

Mautic's value is that the marketing engine is open and self-hosted, which gives teams unusual freedom over how their lifecycle data is stored. That freedom does not extend to the WordPress side by default; the bridge plugin works exactly as documented, but it does not aggregate. Charting the plugin's identify and event log against its bridge mappings turns the quiet WP admin into a real complement to the Mautic dashboards.

A segment with zero events on the pie is a segment whose WordPress-side entry just broke. A flat area chart the day after a release means a layout lost the tracking embed. Mautic's own reports stay where they are, the WordPress side gets the early-warning view it always needed.