No. Conversations and agent presence live in JivoChat's cloud and apps. SleekView only reads the WP-side install state — the widget code option, page-targeting flags and last-edit timestamp. Pulling conversations into WordPress would duplicate sensitive customer chat data and add legal weight to the WP install, which is not what an install audit needs.

Yes. The JivoChat snippet is a single JS embed that thousands of sites still install via Insert Headers and Footers, custom code, or the older plugin still active on legacy installs. SleekView reads whichever option key holds the snippet, including options written by code-snippet plugins. The audit works regardless of how the snippet got there.

Theme-injected scripts are not in the database, so SleekView cannot list them as rows. Move them to a code-snippet plugin (which stores in options) and they will appear in the audit. SleekByte is one such plugin if you want a clean migration path; once the snippet lives in a database row, it becomes auditable.

Edit carefully. The snippet is JS that JivoChat hosts and references through a unique widget ID. Replace it only with a known-good code from the JivoChat dashboard. SleekView keeps a history of edits via WordPress's option-change hooks (when an option-log plugin is in place) so a bad edit can be rolled back without restoring from backups.

Yes. SleekView aggregates per-blog options into a network-wide audit so agencies can run one report across all client sites. Each blog row carries its own widget ID, page-targeting string and last-edit timestamp. Filtering by widget ID across the network is the most common operation and takes one click.

Those run inside the JivoChat platform and never touch WordPress. SleekView's scope is the install layer: which sites have the snippet, where it loads, and which widget ID is current. For email-channel auditing, the JivoChat dashboard is the source of truth.

The page-targeting flag becomes a column. Filter for "All pages" across every blog, then cross-reference with a list of blogs that have cookie walls. The audit catches snippets loading before consent, which is the most common compliance issue with cloud chat tools in cookie-strict regions.

The last-edit timestamp is read from WordPress's option-update hook if your install logs option changes through a plugin like Stream. Without an option-change log, the database only stores the current value. SleekView shows whichever timestamp is available and falls back to the post-modified date if the snippet lives in a code-snippet post type.