Looker Studio WP bridges typically register a custom post type like lookerstudio_report or looker_embed, with the report URL, default parameters, iframe dimensions, and source data connector ID stored in wp_postmeta. Multi-tenant deployments often add a wp_options entry for tenant defaults and a log table such as wp_lookerstudio_log for impression and reload events.

The default WordPress list table for lookerstudio_report shows title, author, and date. Critical context like the underlying Looker Studio report ID, the default URL parameters, the embedded data source, and the page each embed appears on lives in wp_postmeta and never surfaces as a column. Auditing which embeds use which data source means inspecting each post.

SleekView reads the bridge's custom post type plus the supporting wp_postmeta rows and joins them with the log table when present. Report ID, data source, default parameters, iframe size, embedding page, and view count all appear in one row. Edits route through the bridge's own save hooks so iframe cache invalidation continues to fire when you change a URL or parameter set.

Looker Studio is the easiest way to embed a free-tier dashboard into a WordPress page, which is exactly why most sites end up with sprawl. A marketing analyst adds one embed for a campaign in Q1, a content team adds another for a yearly review, an executive asks for a portal full of them, and a year later nobody can list which Looker Studio reports are embedded, which data sources they pull from, or which pages they appear on. The bridges that connect WordPress to Looker Studio almost universally store this as custom posts plus wp_postmeta, but they ship with the default WordPress list table that shows nothing more than title and date.

That works for a handful of embeds and falls apart at scale. SleekView treats the bridge's records as the structured data they actually are. Report ID, data source connector, default parameters, embedding page, and impression counts become joinable columns.

Analytics leads can find every dashboard still bound to a deprecated data source, marketing can see which campaign embeds carry the most weight, and editors can keep the surrounding page copy aligned with the dashboards they show. The result is a Looker Studio deployment that stays legible past its first dozen embeds.