No. Conversations have always lived in Drift's cloud, now Salesloft's. SleekView reads only the WP-side install snippet, wherever it is stored. The dataset covers widget ID, source plugin, target pages, and last-edit timestamp, not chat transcripts or contact history. Conversation data continues to belong to the Salesloft Drift dashboard.

Drift loads as a JS snippet, and most sites today inject it through a code-snippet plugin (Code Snippets, Insert Headers and Footers, WPCode) or directly in theme files. SleekView searches the option keys those plugins use, matches the Drift loader pattern, and reports the source so you know which plugin to edit. Closed-plugin installs still living in wp_options get flagged separately.

Not from the database. header.php snippets aren't in wp_options, so SleekView lists them as "unknown source" rather than inventing a row. Move the snippet to a code-snippet plugin and SleekView picks it up on the next refresh. The honest reporting matters more than a fake inventory.

If the snippet lives in a code-snippet plugin's options, yes. Clearing the field disables the loader on the next page render. If it lives in theme files, you'll need a theme update or to migrate the snippet into a plugin SleekView can reach. SleekView's role ends at the database.

Yes. SleekView aggregates per-blog options network-wide so agencies can produce one cross-site Drift inventory. Each row keeps its blog ID, so filtering to a single subsite or rolling up the whole network are both one-click operations. Closed-plugin still-active rows are surfaced per blog as well.

SleekView matches both legacy drift-XXXX patterns and the current Salesloft loader signatures. As Salesloft updates the snippet, the matcher gets updated alongside, so the same view keeps catching old and new installs without configuration changes.

Yes. SleekView can call the public Drift config endpoint per ID and flag the ones that no longer return a workspace. That column turns the inventory from a list of strings into a triage list, because retired IDs are exactly the rows you want to delete first during a migration cleanup.

It produces the install-side evidence: which subsites load the snippet, on which pages, from which source plugin. Combined with Drift/Salesloft's own data-processing record, that gives a privacy review the missing WP-side half. The conversation log itself stays where it always was, in Drift's cloud.