VBOUT's automation, lead scoring and campaign reporting live in the VBOUT SaaS. The VBOUT WordPress plugin handles the WP-side job: render signup forms, bridge Contact Form 7 and Gravity submissions to VBOUT lists, inject the VBOUT tracking script and persist the API key, list mappings and the submission log to wp_options and wp_postmeta.

The default plugin admin walks an operator through configuration, but it is not a working surface for the captured rows themselves. SleekView reads the plugin's local submission log and the per-form bridge postmeta directly. Each row becomes a typed table entry: submitted_at as a date, form_id as a reference, source_plugin as a string, email as text, list_id as a label and page_slug as a URL. Sort, filter and save views once, then open the right slice in one click.

The scope is honest. SleekView does not mirror VBOUT contacts, lead scores or campaign reports, all of which belong in VBOUT. It surfaces the WordPress half of the bridge as a unified table, which is where capture health and per-page signup quality actually live.

Multi-form sites are the norm in VBOUT installs because VBOUT bridges CF7 and Gravity in addition to its own shortcode. That flexibility is exactly why the operational picture inside WordPress fragments quickly: each form plugin keeps its own list screen, and the connecting tissue (which list does this form post to, on which page was it embedded, when did it last fire) is spread across three different admin surfaces. A single capture table collapses the bridge into one view.

Source_plugin becomes a filter, list_id becomes a column, page_slug becomes a sortable axis and the whole intake reads as one ledger. Same VBOUT plugin data, organised as something a team can actually run from.