SleekView Charts for Autopilot for WordPress
Autopilot rebranded to Ortto, but installs still running the legacy plugin keep the same shape: capture-script flag, form-to-list bridges, consent text and submission log in wp_options and wp_postmeta. SleekView Charts renders that as Number, Pie, Bar and Area cards.
♾️ Lifetime License available
Legacy Autopilot data and current Ortto data share one shape
Autopilot rebranded to Ortto, and the WordPress plugin kept its data layout across the rename. Installs that haven't re-saved settings since the rebrand still write to legacy autopilot_* option keys; installs that have been touched write to the current Ortto keys. The plugin reads both. Either way, it persists the capture-script enable flag, the API token, the tracking domain and per-form bridges into the database.
The default plugin admin works one screen at a time. There is no dashboard that counts how many submissions hit which list this month, no aggregate of pages the capture script actually fired on, no time series of bridge activity. On an agency multisite with a mix of legacy and rebranded installs, that absence is felt at every quarterly review.
SleekView Charts reads both legacy and current option shapes directly. A Number card anchors weekly submissions. A Pie distributes submissions across mapped lists. A Bar splits bridges by source form plugin. An Area trends submissions over time. The chart cards work the same whether the underlying option is autopilot_settings or its Ortto-era successor, which is exactly the point.
Workflow
Turn the Autopilot plugin's legacy storage into a dashboard
Map both option shapes
autopilot_* options and the current Ortto-era keys. The cards merge rows from either shape, so mixed-vintage installs still produce one clean dataset.
Compose the chart cards
Save and scope the dashboard
Drill back to the rows
Sample dashboard
Charts you can build from Autopilot for WordPress data
Submissions this week
Count
Submissions by mapped list
Count
group by list_id
Bridges on legacy vs current keys
autopilot_* option keys versus the Ortto-era keys. A cleanup signal before turning off legacy fallback.
Count
group by storage_shape
Submissions over time
Count
group by submitted_at
Comparison
Default Autopilot plugin admin vs SleekView Charts
Default Autopilot WP plugin admin
- Plugin admin shows one bridge at a time, no aggregate
- No view of legacy vs current option storage across an install
- Per-list submission volume isn't summarised inside WordPress
- Capture-script coverage across pages isn't visible
- No read-only dashboard URL for a marketing lead or auditor
SleekView Charts
- Number KPI for weekly submissions across legacy and current storage
- Pie split across mapped lists regardless of option shape
- Stacked bar showing legacy vs current bridge counts
- Area trend of submissions to catch post-cleanup regressions
- Filters carry between chart and table view on the same dataset
Features
What SleekView Charts gives you for Autopilot for WordPress (legacy Ortto)
Dashboard over legacy and current keys
Cards merge rows from autopilot_* and the Ortto-era option keys, so an install with a mix of vintages produces one clean signal.
Rebrand cleanup audit
Stacked bar over the storage_shape column makes it obvious which bridges still need re-saving to leave legacy fallback safely behind.
Share a read-only snapshot
Send marketing a URL of the bridge dashboard or export the filtered submission cohort to CSV. Reviews work off live numbers, not last week's screenshot.
Audience
Who builds Autopilot for WordPress charts dashboards with SleekView
Email marketers
Anchor weekly reviews on submission count, list mix and time trend even on a mixed-vintage install. The cards don't care which option shape backs each row.
Migration and ops
Use the legacy-vs-current bar as a cleanup checklist. Each bridge that moves off the legacy keys removes one row from the legacy slice and adds one to the current slice.
Agencies
Hand a client one dashboard that covers their entire Autopilot/Ortto bridge audit on day one. The legacy slice tells the cleanup story without slides.
The bigger picture
A rebrand only finishes when the data layout finishes with it
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.
Charting bridges by option shape, alongside the usual submission KPIs and list mix, turns the rebrand into a measurable cleanup task. Each row that migrates off the legacy keys nudges the stacked bar by one. The submission trend confirms that nothing broke during the cleanup.
Same plugin data the runtime bridge already reads, organised as a finite, completable migration view.
Questions
Common questions about SleekView Charts for Autopilot for WordPress (legacy Ortto)
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 across the cards.
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. SleekView reads both, falling back to autopilot_* keys on installs that have not been re-saved since the rebrand.
Yes. The stacked bar grouped by storage_shape shows which bridges still write to legacy autopilot_* keys and which write to current keys. Re-saving each legacy bridge moves it across the bar, so the cleanup is a measurable task with a clear finish line.
No. Chart queries hit option storage 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 Charts 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 pie of submissions by list_id surfaces the resulting flat slice as a clear visual signal, well before a quarterly review would catch the same problem in the SaaS dashboard.
Yes. Each saved chart dashboard is scoped by WordPress capability. Marketers see the submission and list cards while ops sees the legacy-vs-current cleanup view, with each role saving its own filter presets on the same dataset.
Yes. SleekView's multisite roll-up handles both option shapes on every site in scope and presents the merged dataset on the dashboard. A 20-blog agency setup that contains a mix of pre- and post-rebrand installs still produces one filtered table and one chart per metric.
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