SleekView for Autopilot for WordPress
SleekView reads the Autopilot/Ortto WordPress plugin's local options, form-bridge postmeta and submission log across both legacy and current key shapes, and exposes timestamp, form, email, list mapping, storage shape and source page as a single audit table.
♾️ Lifetime License available
A rebrand changes the name. The captures still need a ledger.
Autopilot rebranded to Ortto, and the WordPress plugin kept its data layout across the rename. Installs that have not re-saved settings since the rebrand still write to legacy autopilot_* option keys; installs that have been touched write to the current Ortto-era keys. Either way, the plugin persists the capture-script flag, the API token, per-form list mappings and a submission audit log to wp_options and wp_postmeta.
SleekView reads both shapes directly. Each row becomes a typed table entry: submitted_at as a date, form_id as a reference, email as text, list_id as a label, storage_shape as a string indicating legacy or current keys and page_slug as a URL. A mixed-vintage install still produces one clean table, which is exactly the point.
The scope stays honest. SleekView does not mirror Autopilot/Ortto contacts, journeys or reporting, all of which belong in the cloud. It surfaces the WordPress half of the bridge as a table, which is where capture health, legacy cleanup and per-page signup quality actually live.
Workflow
Turn legacy and current Autopilot storage into one table
Read both option shapes
autopilot_* options and the current Ortto-era keys. The agent reads either path and exposes submitted_at, form_id, email, list_id, storage_shape and page_slug as typed columns.
Compose the table
Filter and save the view
Inline-edit and export
Sample columns
A typical Autopilot/Ortto for WordPress submission table
wp_options + wp_postmeta (Autopilot/Ortto submission log, settings and per-form list mappings, across legacy and current key shapes)
| Submitted | Form | Mapped list | Storage shape | Source page | |
|---|---|---|---|---|---|
| 2026-05-15 13:02 | Newsletter | alex@studio.co | Newsletter | Current | / |
| 2026-05-15 11:46 | Lead magnet | ria@design.io | Lead magnet | Current | /blog/lead-magnet |
| 2026-05-14 23:18 | Webinar | tom@hello.dev | Webinar | Legacy | /webinar |
| 2026-05-14 19:09 | Contact | mia@brew.coop | General leads | Legacy | /contact |
| 2026-05-14 15:41 | Trial signup | sam@northbeam.io | Trial onboarding | Current | /trial |
Comparison
Default Autopilot/Ortto for WordPress admin vs SleekView
Default Autopilot/Ortto for WordPress admin
- Plugin admin works one bridge at a time, with no unified submission table
- No visible distinction between legacy and current storage on the captures
- List mapping is a setting, not a filterable column on submissions
- Source page is logged but not surfaced as a sortable column
- No inline editing of triage notes or review flags at scale
SleekView
- Single submission table that reads both legacy and current option keys
- Storage_shape column makes the rebrand cleanup measurable
- List_id rendered as a friendly label from the mapping option
- Source page surfaced as a sortable, filterable column
- Inline-edit triage notes or review flags without leaving the table
Features
What SleekView gives you for Autopilot for WordPress (legacy Ortto)
One table across both key shapes
Read submissions from autopilot_* and the Ortto-era keys in a single audit table. Mixed-vintage installs produce one clean signal.
Rebrand cleanup checklist
Filter to storage_shape = legacy and the table becomes a finite checklist of bridges that still need re-saving to leave legacy fallback safely behind.
Honest scope
Autopilot/Ortto contacts, journeys and reporting stay in the cloud. SleekView surfaces the WordPress submission log, which is where capture health and cleanup state live.
Audience
Who uses SleekView for Autopilot for WordPress
Email marketers
Filter by list_id and sort by submitted_at to see which forms fed which list this week. The table replaces a settings screen with a working ledger that doesn't care which key shape backs each row.
Migration and ops
Open the legacy-storage view as a cleanup checklist. Each bridge that gets re-saved drops out of the slice and the cleanup becomes a measurable, completable task.
Agencies
Hand a client one table that covers their entire Autopilot/Ortto bridge audit on day one. The legacy slice tells the cleanup story without a slide deck.
The bigger picture
Why a unified table makes a rebrand finite
Vendor rebrands are rarely as clean as the press release suggests. Autopilot's rename to Ortto kept the WP-side plugin's data layout intact and added a thin compatibility layer over the legacy autopilot_* option keys. That compatibility is correct engineering, but it leaves operators without a way to see how much of an install is still relying on legacy storage.
A unified table that exposes storage_shape as a column turns the rebrand into a finite, completable cleanup. Each bridge that migrates off the legacy keys drops out of the legacy view. The submission count confirms that nothing broke during the cleanup.
Same plugin data the runtime bridge already reads, organised as something a team can actually finish.
Questions
Common questions about SleekView for Autopilot for WordPress (legacy Ortto)
Only the WordPress-side data the Autopilot/Ortto plugin already writes: submission rows from the plugin's log option, per-form mappings from wp_postmeta and settings from wp_options, across both legacy and current key shapes. Contacts and journeys are not duplicated into WordPress.
Yes. The plugin's data layout did not change at the rebrand; only branding strings changed. SleekView reads both the current Ortto-era option keys and the legacy autopilot_* keys, so an install with a mix of vintages still produces one clean dataset.
Settings, the capture-script flag, the API token and the tracking domain live in wp_options. Per-form bridges live in wp_postmeta on the bridged form post. SleekView reads both paths and falls back to legacy keys on installs that have not been re-saved since the rebrand.
Yes. Filter to storage_shape = legacy and the slice becomes a finite checklist. Re-saving each legacy bridge moves it out of the view, so the cleanup is a measurable task with a clear finish line.
No. SleekView queries options and postmeta on read, never on write. Form submissions continue to flow through the plugin's runtime bridge with no added work, which keeps visitor-facing latency unchanged.
No. Contacts, journeys and reporting stay in the Autopilot/Ortto SaaS. SleekView only reads the WP-side plugin storage: settings, form bridges and the submission log. The data flow is one direction by design.
Bridges keep posting into the void with no error visible inside WordPress. The submission table surfaces the resulting flat row count per list_id as a visible signal, well before a quarterly cloud review would catch the same problem.
Yes. SleekView's multisite roll-up handles both option shapes on every site in scope and presents the merged dataset on the table. A 20-blog agency setup with mixed vintages still produces one filtered audit ledger.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout