Logging is configurable in the plugin settings. Enable it so the log table accumulates rows for SleekView to chart, and configure the SparkPost webhook endpoint so delivered, bounced, complained, opened, and clicked events flow back into the plugin's event table as they arrive from SparkPost.

Yes. The plugin captures opened and clicked webhook events when the webhook endpoint is configured. SleekView reads the event table and charts engagement as Area or Bar cards alongside the send log, so the dashboard combines volume, deliverability, and engagement on one screen.

Yes. Configure the Number card target to your SparkPost plan's monthly limit and the card renders progress as a percentage. Plan pressure becomes visible a week before the cap is hit, which gives time to upgrade the plan or split transactional and marketing sends across separate SparkPost subaccounts.

Yes. Use the from address or a SparkPost campaign tag header to split rows on the dashboard. A Donut card on tag surfaces the mix and a Bar card on tag ranks the top categories, so transactional and marketing sending can be reviewed separately on the same dashboard without rebuilding it.

Yes. SleekView aggregates against indexed columns on the SparkPost plugin tables, so high-volume sites sending hundreds of thousands of messages a month render charts in seconds. Pagination on detail drill-downs keeps the dashboard responsive even on the busiest WordPress installs.

Yes. Each chart card exposes the underlying rows for export with the active filters applied. That gives a clean handoff to SparkPost support or to upstream auditors when a deliverability incident needs documenting across a particular date range, status filter, or recipient domain.

Yes. If the WordPress site sends through multiple SparkPost subaccounts (one per sub-brand or environment) the plugin records the subaccount per row. SleekView groups by subaccount on a Bar card so per-subaccount sending and deliverability sit side by side on the same dashboard.

Yes. SleekView reads the SparkPost plugin's existing tables, so as long as the plugin keeps writing those tables the dashboard continues to render. If a major update renames a column the dataset is updated once centrally and every card on the dashboard picks up the change automatically.