The plugin records signups into a local subscribers table and SMTP sends into a local log table when the corresponding features are enabled. Make sure form tracking and SMTP logging are both turned on in the plugin settings so the tables accumulate rows for SleekView to chart on the dashboard.

Yes. The list_id column on the subscribers table identifies which Brevo list each signup landed in. Group by list_id on a Bar or Donut card to see per-list growth over the dashboard's date range, useful for confirming each form is pushing into the right Brevo list configured in the plugin settings.

Yes. The status column on the Brevo SMTP log separates sent from failed rows. A Donut card on status surfaces the deliverability mix and an Area card filtered to failed rows shows the failure trend across the date range without manual cross-referencing of multiple screens in the plugin admin.

Yes. The source column on the subscribers table records which form widget submitted the contact. A Bar card on source ranks the top-converting form placements, useful for optimising which forms to promote and which to retire based on actual signup performance over time.

No. SleekView reads the local tables that the Brevo plugin writes during normal operation. No additional API calls are made to Brevo, which keeps the dashboard fast and avoids consuming Brevo API rate limits even on high-volume WordPress sites with frequent dashboard refreshes.

Yes. Aggregations run on indexed columns on the Brevo plugin tables, so high-volume sites with tens of thousands of signups a month render charts in seconds. Pagination on detail drill-downs keeps the dashboard responsive even on the busiest WordPress installs running Brevo at scale.

Yes. Each chart card exposes the underlying rows for CSV export with the active filters applied. Useful for handing signup data to ad platforms or for cross-checking against the Brevo control panel when reconciling local WordPress signups with the Brevo central list totals.

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