The Ortto WordPress plugin keeps its surface small. A serialized settings array in wp_options holds the capture-script 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. To answer "which forms feed which lists, which consent strings are non-default, which bridges have not been touched in months" the lifecycle team opens every form individually. The data is queryable, the list view is missing.

SleekView reads the postmeta and surfaces every bridge as one row. Source form plugin, source form ID, target Ortto list, consent override and last edit sit as real columns. Sort by Ortto list to find the targets carrying the work, filter to non-default consent to scope a legal review, bulk-repoint bridges from a retired list to its replacement.

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 lists those three across the site at once.

SleekView treats them as a dataset and renders every bridge as a row, so the lifecycle team scans which bridges carry the work and the legal team scopes which consent strings are still default. Same data the plugin already writes, organised as a table instead of a tab tour.