Yes. Brave Pro can save leads in your WordPress database, which is unusual among popup builders since most route directly to an ESP. SleekView reads that store directly. If your install is configured to skip local saving, those leads won't appear because they're never written to the database in the first place.

Brave's lead storage is in a plugin-owned table on most versions, or as serialized rows in postmeta against the popup on older builds. SleekView's agent UI inspects your schema and maps whichever shape your install uses, so you don't have to write the SQL or the meta key list yourself.

Yes. Custom-field values are pivoted out of the underlying meta-style storage into typed columns so you can filter and sort on them. Pick the keys that matter, name them, and SleekView turns them into first-class columns. Fields that show up in only some popups simply render empty for rows that didn't capture them.

Yes. SleekView uses standard write paths so any save_post or plugin-specific hooks fire as expected. If Brave registers a custom action on a lead-status change, that action runs when SleekView writes the new status. Webhooks and integrations downstream of those hooks behave the same as if you'd edited from Brave's admin.

Yes. A view over the popup post type with capture-count columns gives you a quick performance overview without leaving SleekView. Sort by capture count to find your top performers, or filter by zero-capture popups to identify candidates for retirement. Pair with date filters on the lead view for trend reads.

If a popup only routes to an ESP and doesn't save locally, those leads won't appear in SleekView since they're never persisted in your database. SleekView is honest about that. The fix is to enable Brave's local-save toggle for the popups you want to audit, or to accept that ESP-only popups live in the ESP.

Yes. Filter the lead store by email and group it; rows with the same address surface together regardless of which popup captured them. That's useful for spotting people who hit the newsletter form, the demo form, and the exit intent over the same week so the ESP doesn't get four duplicate contacts.

No. Capture counts and analytics are owned by Brave's own counters which fire on form submission. SleekView reads those counters as columns but doesn't increment them. Status edits and cohort tagging stay on the SleekView side, while real capture analytics keep flowing through Brave's normal collection path.