The Klaviyo for WooCommerce plugin owns three things in WordPress: the public key, checkout-block consent text for both email and SMS, and the sync state with the cloud. All of them live in wp_options under the klaviyo_settings key. The default page exposes them across separate tabs, which works for one store and stops working at network scale.

SleekView Charts treats those option rows as a chart source. A Number card pins the count of stores connected to Klaviyo. A Pie shows the email-consent and SMS-consent mix across the network. A Bar ranks public-key prefixes (which encode the data center) by how many stores point at each. An Area card tracks sync-timestamp freshness so stale integrations show as a flat shoulder on the curve.

The board uses the same row schema the SleekView for Klaviyo audit table writes, so a saved chart view inherits the table filters. One configuration covers compliance check and leadership report.

Klaviyo's WordPress plugin has the smallest possible WP-side surface, which is the right architecture for a SaaS-first platform. The trade-off is that the few things it does store are the things that legal and ops most need to audit. Consent strings are not a marketing detail; they are the language a regulator reads when a buyer disputes a subscription.

The public key is not just configuration; it is the single value that decides whether checkout flows fire at all. Both can drift between staging and production, between regional stores on a multisite, between team members with admin access and team members who run audits. The default Klaviyo settings page presents these on separate tabs because that is convenient when configuring one store.

It becomes inconvenient when auditing twenty stores at once. The chart layer turns the same data into a one-screen answer for the audit cadence operations actually runs.