SleekView for Tidio Lyro AI
SleekView reads the Tidio plugin's wp_options, per-page postmeta, the form plugin's submissions table and any local webhook log. Widget status, exclusion reasons, captures and events line up as columns you can sort and filter.
♾️ Lifetime License available
Tidio reports on conversations. WordPress holds the embed surface.
The Tidio plugin admin lists the public key and a visibility section, and that is roughly the whole picture you get on the WordPress side. It does not resolve those visibility rules into the actual list of URLs the widget loads on, it does not sit next to the form submissions that route into the Tidio Inbox, and it does not show webhook events the site stores.
SleekView reads the WordPress-side data as one dataset. The plugin settings come from wp_options. Per-page overrides come from postmeta. Capture submissions live in the form plugin's submissions table. Webhook event records, when the site logs them, sit in a custom table.
Tidio's own panel still owns conversation analytics, Lyro AI resolution rate and agent workload. SleekView covers the half the panel cannot see: per-URL widget status, why a page is excluded, which forms feed the Inbox and whether webhook delivery into WordPress is still alive.
Workflow
Turn the Tidio plugin's footprint into a table
Pick the source rows
Compose your column set
Save and scope the view
Edit inline and export
Sample columns
A typical Tidio widget and capture view
wp_options (tidio_*) + form plugin submissions + webhook log table
| Source URL | Widget | Exclusion | Captured email | Last webhook | Received |
|---|---|---|---|---|---|
| /pricing/ | Loaded | — | ana@northwind.io | visitor.created | Apr 24 14:02 |
| /blog/lyro-vs-fin/ | Loaded | — | tom@studio.dev | lead.captured | Apr 24 11:47 |
| /contact/ | Loaded | — | ria@design.co | conversation.replied | Apr 24 09:21 |
| /docs/install/ | Excluded | post-type rule | — | — | — |
| /members/ | Suppressed | per-page override | — | webhook.failed | Apr 23 17:08 |
Comparison
Default Tidio plugin admin vs SleekView
Default Tidio plugin admin
- Plugin admin lists settings, never resolves them into a per-URL row
- No view of which post types or templates actually load the widget
- Exclusion reasons stay scattered across settings and per-page meta
- Lead-capture form submissions live in a separate form plugin screen
- Local webhook event records have no list or filter view
SleekView
- Per-URL rows resolved from Tidio's enable and exclusion rules
- Inline widget status (Loaded, Excluded, Suppressed) per row
- Exclusion reason column for fast audit of why a page is silent
- Joined columns for the latest capture and webhook event per page
- Save filtered views per role (marketing, support, integration owner)
Features
What SleekView gives you for Tidio Lyro AI
Custom column sets per view
Build a marketing view with URL, widget status and exclusion reason. Build an integration view with webhook event, status code and received_at. Each role gets the columns it actually uses.
Inline edits on overrides
Flip a per-post embed override, mark a webhook event row as triaged or update a capture-submission note without bouncing through three admin screens.
Compose precise filters
Combine widget status, post type, exclusion reason, form_id and webhook event_type. Save the filter as a named view your team reuses every week.
Audience
Who uses SleekView for Tidio Lyro AI
Marketing leads
Confirm the widget loads on every campaign landing page, and that no recent theme update silently excluded a high-traffic template from the chat surface.
Support leads
Filter capture rows by form_id to see which WordPress entry points still feed Tidio and which forms quietly stopped routing after a migration or form rebuild.
Integration owners
Filter on webhook.failed events to catch a broken Tidio callback days before the Inbox shows a quiet automation queue and visitor messages back up.
The bigger picture
Why Tidio's WordPress half needs a real table
Tidio's panel puts conversation analytics and Lyro AI resolution rate front and centre, and that view is the right one for what Tidio does. The WordPress side of the integration is where visibility stops. Embed coverage lives behind a settings toggle.
Exclusions sit in scattered rules and overrides. Capture submissions route through whichever form plugin a particular page uses. Webhook event records, when they exist, gather in a custom table.
SleekView reads those four sources as a single dataset and renders them as one row per URL, submission or event. Marketing sees the widget surface. Support sees the capture flow.
Integration owners see whether webhook delivery is still alive. Same database, completely different governance posture, no replacement for the Tidio panel.
Questions
Common questions about SleekView for Tidio Lyro AI
No. Conversation volume, Lyro AI resolution rate and agent workload stay inside the Tidio panel, which is the right tool for those views. SleekView only renders the WordPress-side surface: per-URL widget status, exclusions, captured leads and any local webhook event records.
WordPress-native rows: the Tidio plugin's wp_options entries, any postmeta used for per-page overrides, the form plugin's submissions table for captures routed to Tidio and a webhook log table if the site writes one. No Tidio API call is required for these views.
SleekView resolves the plugin's enable and exclusion rules into a per-URL flag column plus a separate exclusion-reason column. Sort or filter on either to find every page that should be loading the widget but is not, or every page that should not be loading it and still is.
Yes. Each form plugin stores submissions in its own table. Add each table as a dataset and the view normalises form_id, submitted_email and submitted_at into shared columns spanning Gravity Forms, WPForms, Forminator, Fluent Forms and database-extended Contact Form 7 setups.
Yes. SleekView writes through the plugin's CRUD layer where one exists, so any filters the Tidio plugin registers on option updates or postmeta saves still fire. Bulk operations iterate the same path so side effects match a manual edit.
Queries hit standard WordPress indexes on options, postmeta and form submissions. Filters and sorts use indexed columns where possible, and expensive resolutions like per-URL embed flags are cached per page-load, so default views stay quick even on installs with high traffic.
Yes. Every SleekView view is gated by WordPress capability, so a marketing-facing Tidio audit can be limited to marketing and support roles while developers see a separate, more technical view with raw event logs and override meta.
Yes. The plugin that embeds the Tidio widget stores its public key and visibility rules as standard WordPress options. SleekView reads those options, plus any related form submission and webhook log rows, without needing a paid Tidio plan.
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