✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Ortto: WP-side capture & tracking config as tables

Ortto contacts, journeys, and reports live in the Ortto SaaS. The WP plugin stores capture-script config, form-to-list mappings, consent defaults, and the API token in wp_options. SleekView turns that into a proper table.

♾️ Lifetime License available

SleekView table view for Ortto for WordPress

Ortto's WP-side surface is config, not contacts

After the Autopilot rebrand, the WordPress plugin still does what it always did: inject a tracking script and bridge a few forms. All contact data flows to Ortto's cloud. SleekView reads what's local — settings, capture flags, form-target mappings, consent strings — and presents them as one inline-editable table.

Sample columns

A typical Ortto capture & form mapping view

Ortto's settings array lives in wp_options. Per-form mappings sit in wp_postmeta when the form integration is enabled.
Source: wp_options + wp_postmeta
Surface Form/page Ortto target Consent text Last seen Status
Capture script (global) site-wide Default Apr 24 Loading
Form bridge Contact list:leads Custom Apr 23 Synced
Form bridge Newsletter list:newsletter Default Apr 20 Synced
Form bridge Old quiz list:archived Default Feb 11 List archived

Comparison

Default Ortto plugin UI vs SleekView

Default Ortto plugin UI

  • Plugin UI shows one form mapping at a time
  • No filter for forms whose target list was archived in Ortto
  • Capture-script enable flag is global with no per-page audit
  • Consent-string overrides aren't summarized anywhere
  • No diff between staging and production capture configs

SleekView

  • All form bridges in one filterable list
  • Consent-text overrides surfaced as a column
  • Capture-script flag visible alongside form mappings
  • Inline-edit which Ortto list a form posts to
  • Multisite roll-up so agencies see every client at once

Features

What SleekView gives you for Ortto for WordPress

Bridge audit

If you bridge a contact form (Gravity, Fluent, etc.) to Ortto, the plugin keeps the mapping in postmeta. SleekView pulls every mapping into one screen.

Consent-text governance

Custom consent strings drift over time. SleekView surfaces every override so legal can spot stale wording before it goes to a regulator.

Stale list detection

When a list is archived in Ortto, mapped forms keep posting into the void. Filter for mapped lists no longer in the active set.

Audience

Who uses SleekView for Ortto

Privacy & legal

Audit consent strings and capture-script enable flags before a compliance review.

Lifecycle marketers

Inventory which WP forms feed which Ortto journeys without bouncing between two tools.

Agencies

Hand a client a single audit table of their Ortto WP integration on day one of an engagement.

Questions

Common questions about SleekView for Ortto for WordPress

No — contacts and journey state stay in Ortto. SleekView surfaces only the WP-side settings, form mappings, and consent flags the plugin stores in your database.

 

In wp_options as a serialized array. The capture-script enable flag, API token, and tracking domain are all there. SleekView pivots them into named columns.

 

When you bridge a form to Ortto, the form-to-list mapping is saved on the form's metadata. The exact location depends on which form plugin you bridge — SleekView reads the standard locations for Gravity, Fluent, and Contact Form 7.

 

Yes — the next form submission posts to the new list. SleekView writes the mapping back to postmeta; the runtime bridge picks it up immediately.

 

Ortto kept the same WP-side data shape across the rebrand. SleekView reads the current option keys and falls back to legacy autopilot_* keys on older installs.

 

Tracking events stream straight to Ortto's cloud — they aren't queued in WordPress. To audit those, use Ortto's own activity log.

 

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.

...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