From Brave's local lead storage, which is the same source SleekView's table view reads. If your install routes a popup only to an ESP without saving locally, those leads do not appear because they are never persisted in your database. The fix is to enable Brave's local-save toggle for the popups you want on the dashboard.

No. Brave's capture counters still tick as forms submit; SleekView Charts reads the resulting lead rows and groups them. Use both: Brave's per-popup counter for the in-context glance, SleekView Charts for the rollup that crosses popups and time.

Yes when Brave captures it. A filter chip for granted, pending, or denied scopes every card to that consent state. Compliance dashboards typically show only granted-consent totals; acquisition dashboards typically show the full mix.

Yes. If Brave records the referring page on captures, a Bar or Pie grouped by source page ranks the pages that drive signups. Useful for content teams trying to understand which posts and pages convert.

An Area card grouped by the capture date with Count aggregation plots one point per day. The shape is what matters: campaign spikes, weekday baselines, and quiet weekends all surface without separate analysis.

Yes. Add a popup filter chip and the same cards re-aggregate to that popup only. Useful when a campaign manager owns one specific popup and wants its dashboard on its own screen.

Yes. SleekView Charts joins popup_id to wp_posts so chart labels show readable names instead of integer IDs. If a popup has been deleted, the ID appears with a deleted indicator so the card still makes sense.

No. The charts are read-only. Capture counts and analytics still live with Brave's own counters which fire on form submission. SleekView Charts aggregates the persisted lead rows, not the counters.