The Ortto WordPress plugin keeps its surface small after the Autopilot rebrand. A serialized settings array in wp_options holds the capture-script enable flag, API token and tracking domain. Per-form bridges to Ortto lists live in postmeta on the source form post when the Gravity, Fluent or Contact Form 7 integration is enabled. Consent string overrides sit alongside the form mappings on the same postmeta rows.

The default plugin UI surfaces one bridge at a time. It does not show how many bridges exist across the site, which Ortto list is referenced most, whether the capture script is enabled on every blog of a multisite, or which bridges point at a list archived in the Ortto cloud. The data is queryable, the operational picture is not.

SleekView Charts reads the Ortto plugin's WP-side data directly. A Number card anchors total active form bridges. A Pie splits bridges by form plugin (Gravity, Fluent, CF7). A Bar ranks Ortto lists by how many bridges target them. An Area trends edits to bridged forms over time, surfacing when the marketing team last touched the lead-capture funnel.

Ortto's WordPress plugin is intentionally thin, and the WP-side surface is small. The things it does store, capture script flag, form bridges, consent overrides, are exactly the things that matter most when the marketing team runs a quarterly audit or the legal team prepares for a regulator question. The default plugin UI never aggregates those three across the site.

SleekView Charts treats them as a dataset and renders the coverage as a chart, so the lifecycle team sees which bridges carry the work and the legal team sees which consent strings are still default. The data already lives in wp_options and wp_postmeta, the chart layer turns it into an operational picture instead of a settings tab.