TikTok Feed plugins pull videos from a TikTok account or hashtag into a local cache, primarily stored in wp_options under feed keys, with some installs using an optional wp_tkf_video_cache table for per-video rows. The default admin focuses on per-feed configuration with no unified inventory of every TikTok feed on the site.

SleekView reads the cache and shows one row per TikTok feed with account or hashtag, last-sync, video count, status, and the shortcode entries that embed each feed. Filters like 'stale this week' or 'feeds tied to hashtag #campaign' become first-class chips. Useful for content audits and for the inevitable token rotation when TikTok updates its API.

The grid handles both modes (feed-level cache only and full per-video cache table) and labels each so admins know what they are looking at. The view is an operations and audit layer; configuration and OAuth still go through the plugin's own admin.

TikTok feeds anchor campaign pages and brand landing pages where a blank embed is a noticeable failure. The data flows from TikTok into a local cache the plugin maintains, and the cache stops refreshing the moment a token expires or the API policy changes. The default plugin admin lets you configure feeds, not monitor them across an entire campaign portfolio.

SleekView reads the cache the plugin already writes and surfaces the operational picture: which feeds are fresh, which are stale, which failed, where each one is embedded, and how recently the account or hashtag was synced. Campaign managers catch broken hashtag feeds before a launch goes live with an empty grid. Maintenance teams clear the re-authorization queue once a sprint instead of after a customer complaint.

Compliance teams produce the third-party embed inventory their cookie policy already implicitly promises. The data is the same; the view is what makes it operational.