✨ 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 Tawk.to: chat widget config and visibility as tables

The Tawk.to plugin embeds the chat widget using property and widget IDs in wp_options with optional per-post visibility metadata. SleekView turns those records into an editable list for marketing and support leads.

♾️ Lifetime License available

SleekView table view for Tawk.to

Tawk.to visibility rules on one screen

The Tawk.to WordPress plugin connects a property and widget to the site by storing two identifiers in wp_options: tawkto-embed-widget-page-id and tawkto-embed-widget-widget-id. Optional visibility configuration adds sub-keys for show/hide on specific page templates, post types, and individual posts. Per-post visibility toggles persist as wp_postmeta rows. The conversations themselves live entirely in Tawk.to's dashboard.

Operating that on a real site means knowing which pages hide the widget, which post types have an explicit override, and which property is connected on each environment. The plugin's settings tab shows the current property ID but doesn't expose the per-page overrides or the postmeta toggles as a list. SleekView reads the relevant wp_options rows, joins them with the post-level overrides, and surfaces the full visibility ruleset as a sortable table.

Inline edits cover the visibility toggles, the rule status, and the property reference. Writes go through update_option() and update_post_meta() so any cache plugin, audit log, or sync tool that listens for those WordPress events fires normally.

Workflow

From scattered overrides to a single audit table

1

Read options and postmeta

SleekView detects Tawk.to and registers tawkto-embed-widget-* options together with tawkto_visibility postmeta as a unified visibility source.
2

Compose columns

Pick scope, target, rule, state, last modified, and optional editor metadata. Reorder per view so support, marketing, and admins each open their own starting table.
3

Save audit views

Save views like Hidden pages, Override per post type, or Property check. Scope by role so each team has the right starting list.
4

Edit inline

Toggle visibility or change a rule from the table. Writes fire the standard WordPress option and postmeta hooks so cache and audit-log plugins react normally.

Sample columns

A typical Tawk.to visibility view

One row per visibility rule or per-post override with current state and last update.
Source: wp_options (tawkto-embed-widget-*) + wp_postmeta (tawkto_visibility per post)
Scope Target Rule State Updated by Updated
Page /contact Show Visible alex@studio.co Apr 24
Page /checkout Hide Hidden ria@design.io Apr 20
Template page-landing.php Show Visible tom@hello.dev Apr 02
Post type docs Hide Override mia@brew.coop Mar 18

Comparison

Default Tawk.to admin vs SleekView

Default Tawk.to admin

  • Visibility overrides aren't surfaced anywhere as a real list
  • Per-post tawkto_visibility postmeta is invisible in WP Admin
  • Property and widget IDs only show in the settings tab
  • No saved view of pages where the widget is intentionally hidden
  • Bulk overrides require direct database edits or manual per-post toggling

SleekView

  • Surface tawkto_visibility postmeta as a sortable column
  • Expand visibility sub-keys from wp_options into rows
  • Inline-toggle per-post or per-template overrides
  • Save audit views like pages where the widget is hidden
  • Diff property ID between staging and production

Features

What SleekView gives you for Tawk.to

Visibility audit

Filter every published page by Tawk.to visibility postmeta. The mystery of why the widget vanishes on one URL but appears on another becomes a single sortable list of explicit overrides.

Inline overrides

Toggle visibility from the table. Writes go through update_post_meta() so any cache plugin, sitemap tool, or audit log that listens to postmeta changes reacts cleanly.

Property comparison

Filter by environment and compare the property and widget IDs to confirm that staging and production talk to the right Tawk.to property after a database refresh or a migration.

Audience

Who uses SleekView for Tawk.to

Marketing operations

Audit which pages show or hide the widget by filtering tawkto_visibility postmeta. Bulk-enable a campaign URL set without opening each post individually.

Support leads

Confirm at a glance that the production property ID matches the documented Tawk.to property, and that no developer accidentally swapped it during a staging-to-live promotion.

Site administrators

Export the visibility ruleset as CSV before a launch and diff it against the post-launch state. Eliminates the usual launch-day mystery of widgets disappearing from random pages.

The bigger picture

Why an embed plugin needs a visibility ledger

Tawk.to's free tier is widely used on WordPress for exactly the right reason: it's a small, stable, well-documented embed. The trade-off is a settings screen that captures the moment the widget was installed and almost nothing about its operational lifetime afterwards. As editors enable and disable the widget on specific posts, as page templates get new visibility rules, as developers test alternative property IDs on staging, the configuration spreads across wp_options and wp_postmeta with no list view to ground it.

Six months in, nobody can answer simple operational questions like which URLs hide the widget or whether staging points at the right property. SleekView fixes that without forking how Tawk.to stores anything. The plugin keeps writing the same options and postmeta.

SleekView reads them and presents them as a real table that supports filter, sort, bulk edit, and CSV export. Conversations stay in Tawk.to's dashboard. The visibility ledger comes home to WP Admin where the team can operate it.

Questions

Common questions about SleekView for Tawk.to

No. Tawk.to conversations and visitor data live in Tawk.to's dashboard, never in WordPress. SleekView only reads the configuration stored in wp_options and wp_postmeta.

 

When the Tawk.to plugin's visibility settings disable the widget on a single post, it stores the override as tawkto_visibility postmeta. SleekView lists those overrides as their own rows.

 

Writes go through update_option() and update_post_meta(), which fire the standard WordPress hooks. The next page render reflects the updated visibility state, the same as it would from the settings screen.

 

Yes. The two identifiers are stored in wp_options and surface as rows in the configuration view. View scoping can hide them from roles that shouldn't see the property ID.

 

Post-type-level overrides are stored in the Tawk.to options group and become their own rows. Filter by scope equals Post type to audit them, and inline-edit the rule from the table.

 

Yes. tawkto_visibility postmeta is per post, so translations have their own override rows. Filter by language taxonomy to audit each translated set independently.

 

Yes. Any saved view exports to CSV, which is the practical way to capture a configuration snapshot before a migration or a theme switch.

 

Each subsite has its own Tawk.to options and postmeta. SleekView reads the current site's data; a network admin 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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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