No. Klaviyo profiles and segments live in Klaviyo's cloud, where the customer record is canonical. SleekView only reads the WP-side settings, consent text and sync flags the plugin stores. Pulling profiles into WordPress would duplicate sensitive data and add legal weight to the WP install, which is the opposite of what the plugin is designed to do.

In wp_options under klaviyo_settings, a serialized array containing the public key, email and SMS consent strings, list IDs and the checkout-block toggle. SleekView pivots the array into named columns so the same data becomes sortable, filterable, and inline-editable across multisite networks rather than living inside a single opaque settings page.

Klaviyo reads order data via WooCommerce's data layer at runtime. The orders themselves are in wc_orders (HPOS) or posts (legacy). SleekView for WooCommerce covers that side; this view is the Klaviyo configuration layered on top, and a complete audit usually combines both views to confirm both schema and integration are healthy.

No. Flow runs are visible in Klaviyo's analytics. SleekView's WP-side scope ends at "is the integration configured and healthy." That separation is intentional: duplicating flow run data into WordPress would be a bidirectional sync product, not an audit one, and would add complexity that customers do not want.

Yes. The checkout block consent toggle (added in 3.2.0 of the plugin) is part of klaviyo_settings. SleekView shows the value as a column. Toggling it inline updates the option, which the WooCommerce checkout block reads at render time, so the next checkout reflects the new state without a manual republish.

Yes. Checkout reads the option at render time. Edit the string in SleekView and the next checkout shows the new copy. There is no separate cache to invalidate; if a full-page cache is in use, the new string appears on the next regeneration of the checkout page like any other option-driven content.

The plugin writes a last-failure flag and timestamp into options when webhook delivery fails. SleekView exposes both as columns. For a richer history, the Klaviyo dashboard remains the source of truth, but the WP-side flag is enough to catch a broken integration before it silently misses a launch.

Klaviyo's data center selection is encoded in the public key prefix. SleekView surfaces the prefix as a column so a multisite network with mixed regional stores can confirm each blog points at the correct data center. The audit catches the mistake of an EU store accidentally configured against a US-region key, which is otherwise easy to miss.