SleekView for Olark: live chat embed config as tables
The Olark plugin connects a WordPress site to an Olark account using a site ID in wp_options and optional per-post visibility settings. SleekView surfaces those records as an editable audit table.
♾️ Lifetime License available
Olark configuration as a working list
Olark's WordPress plugin is a small embed: it stores the Olark site ID in wp_options under olark_site_id (and a few related sub-keys for visibility and chat behavior). Per-post visibility toggles are saved as postmeta. Olark itself stores all chats, transcripts, and operator data in its own SaaS app, never in WordPress.
Day-to-day operations don't need access to chats; they need to know which pages show the widget, which environment connects to which Olark site, and when the last configuration change happened. None of that is visible from the plugin's settings screen as a list. SleekView reads the option group, joins per-post toggles, and presents the configuration as a sortable, filterable table with inline edits.
Writes flow through update_option() and update_post_meta(), so any audit log, cache layer, or sync tool that listens for those events behaves exactly as it would after a settings-screen save.
Workflow
From a single option to a queryable configuration
Read options and postmeta
olark_site_id, olark_settings, and the per-post olark_disable postmeta as a single source.
Compose columns
Save audit views
Edit inline
Sample columns
A typical Olark configuration view
wp_options (olark_site_id, olark_settings) + wp_postmeta (olark_disable per post)
| Scope | Target | Setting | Value | Status | Updated |
|---|---|---|---|---|---|
| Global | olark_site_id | Site ID | 1234-456-10-0001 | Active | Apr 22 |
| Page | /pricing | olark_disable | false | Visible | Apr 18 |
| Page | /legal/* | olark_disable | true | Hidden | Apr 06 |
| Global | olark_settings | auto_open | true | Override | Mar 24 |
Comparison
Default Olark admin vs SleekView
Default Olark admin
- Settings screen shows the current site ID but no per-page audit
-
Per-post
olark_disablepostmeta isn't listed anywhere -
Serialized sub-keys in
olark_settingshide auto-open or position drift - No saved view of pages where the widget is intentionally hidden
- No bulk way to confirm that staging connects to the staging site ID
SleekView
-
Surface
olark_disablepostmeta as a sortable column -
Expand
olark_settingsinto rows for auto-open, position, locale - Inline-toggle per-post visibility from a single table
- Save audit views per scope (global, page, template, post type)
- Diff site ID and config between staging and production
Features
What SleekView gives you for Olark
Visibility ledger
Every page or pattern that hides the Olark widget becomes a row, sortable by last update. Marketing can confirm campaign coverage without opening posts one at a time.
Inline toggles
Switch a page from visible to hidden in one click. Writes route through update_post_meta() so cache, sitemap, and audit-log plugins respond as normal.
Environment diff
Export the configuration view from staging and from production. A simple CSV diff catches the moment when the wrong Olark site ID slips into a deployment.
Audience
Who uses SleekView for Olark
Marketing operations
Audit which URLs hide Olark before a campaign goes live. A saved view of hidden pages, sorted by last update, surfaces overrides made by editors during regular content edits.
Support leads
Confirm that the chat widget is enabled on the high-intent pages (pricing, contact, demo) by filtering by URL pattern and Olark visibility state from one screen.
Site administrators
Diff staging and production configuration with a CSV export. Catches accidental site-ID swaps and serialized-setting drift before either reaches customers.
The bigger picture
Why a small chat plugin still needs a real audit surface
Olark's WordPress plugin is intentionally minimal: a site ID, a few visibility toggles, and a thin embed loader. That minimalism makes it reliable but also makes it operationally opaque the moment more than one person touches the site. Editors disable the widget on a single legal page and forget about it.
A developer copies the production database to staging and the site ID quietly carries over. A theme migration changes the page-template visibility rule and nobody remembers what it used to be. The chat experience customers see depends on configuration spread across one option and a handful of postmeta entries, with no list view anywhere in WP Admin to ground it.
SleekView treats that scattered configuration as the table it deserves to be. Each rule becomes a row, each environment becomes an exportable snapshot, each edit fires the same WordPress hooks the settings screen would. Olark keeps storing its data exactly the same way.
The WordPress side gains a working operational surface.
Questions
Common questions about SleekView for Olark
No. Chats and transcripts live entirely in Olark's SaaS app. SleekView only reads what the plugin stores in WordPress, which is the option group and per-post toggles.
Posts and pages with an olark_disable postmeta entry appear as rows. SleekView lists them next to global rules, so a single screen covers both site-wide and per-post configuration.
Yes. Writes go through standard WordPress option and postmeta APIs, so any plugin listening for those changes (audit logs, cache invalidation, sync tools) reacts as expected.
If the plugin stores pre-chat survey toggles in olark_settings, those become their own rows. Survey content itself is configured in Olark's app and is not stored locally.
Operator availability lives in Olark's app and isn't exposed to the WordPress plugin. SleekView focuses strictly on the configuration that WordPress owns.
Anyone with manage_options capability can read it directly from WP. SleekView respects WordPress capabilities so views can hide sensitive rows from roles that shouldn't see them.
Pair SleekView with a standard option audit-log plugin to see the previous value. The row in SleekView is still inline-editable to revert with one click.
Yes. Each subsite has its own Olark option group and postmeta. SleekView reads the current site, and network admins can switch sites to audit each one.
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 checkoutBrowse more
- Woocommerce Shipping Multiple Addresses
- Bigcommerce Bridge
- Funnelkit Cart
- Woocommerce Checkout Manager
- Woocommerce Quickbooks Sync
- Woocommerce Multilingual Currency
- Payu Money Woocommerce
- Yith Woocommerce Product Image Gallery Slider
- Woocommerce Sendcloud
- Woocommerce Dhl Express
- Woocommerce Product Table
- Presta Shop Bridge
- Yith Woocommerce Affiliates
- Site Reviews
- Yith Woocommerce Anti Fraud