Fluent Forms persists every submission in fluentform_submissions, with field values pivoted into fluentform_submission_meta. Conditional notifications fire on submission, sending emails only when the configured field conditions match, and Fluent Forms logs the result in fluentform_logs with the form ID, the notification name, and the dispatch status. Useful, until the team wants to know how often each conditional notification actually triggers across a week.

SleekView Charts treats fluentform_submissions as the dataset and exposes the notification log keys as first-class columns. Count submissions that triggered a given notification, group by form_id to rank forms by conditional volume, split by notification name to see which conditions match most often, and slice by created_at for daily trends. Filters configured at the view level cascade to every card so the dashboard scopes to one campaign in one move.

Charts share filters and saved views with Table mode, so jumping from a Bar of busiest notifications to the submissions behind them is one tab. On a site with dozens of conditional notifications per form, the indexed fluentform_submissions queries the plugin already runs keep cards responsive without a separate reporting layer.

Fluent Forms makes conditional notifications easy to configure, but the value of that logic only shows up in numbers. Each submission rolls through every conditional notification rule, fires the ones that match, and writes the result to fluentform_logs. The log screen paginates rows.

The status filter exists, the notification name exists, the created_at column exists, yet there is no built-in view of total sends per notification across a week. Workflow teams want the busiest notifications. Form admins want failed-dispatch counts.

Editors want confirmation the conditions matched their submissions. None of these are exotic queries. They are aggregations over rows the plugin already writes.

SleekView Charts joins fluentform_submissions and fluentform_logs and turns conditional emails from a silent backend feature into a visible dashboard.