Freshmarketer is the marketing automation product in the Freshworks Customer Service Suite stack. Its own dashboards cover journeys, A/B tests and conversion analytics, which is exactly where that data belongs. The WordPress plugin's role is narrow: render the Freshmarketer JavaScript with the right bundle code, fire identify calls for logged-in users, optionally bridge form submissions to Freshmarketer lists and persist settings to wp_options. Per-form mappings sit in wp_postmeta when a Contact Form 7, Gravity or Fluent bridge is enabled.

The default plugin admin in WordPress shows the configuration screen and a connection check. It does not aggregate, and it does not chart. Questions like "how many identify calls fired this week", "which form is feeding which Freshmarketer list" and "did the tracking flag go off on a staging environment" all have answers in the plugin's option store and event log, but they are not surfaced.

SleekView Charts reads those storage paths directly. A Number card anchors weekly identify calls. A Pie distributes events across mapped Freshmarketer lists. A Bar groups form bridges by source plugin. An Area trends events over time so a regression after a theme switch is visible the same day. Same Freshmarketer plugin data, organised as a WP-side bridge dashboard.

Freshmarketer sits in a larger Freshworks stack, which means the bridge between a WordPress site and the marketing automation engine has to coexist with CRM-side workflows, A/B tests and journeys that change without WP-side warning. The plugin's option store and event log are the only signal that the bridge is alive on its own side. Charting that data turns the quiet WP admin into a real complement to Freshworks' own reports.

A journey with zero events on the pie is a journey whose WP-side entry just broke. A flat area chart the day after a release means an embed disappeared from a layout. Freshworks' dashboards stay where they belong; the WordPress side gets the early-warning view it deserves.