Smash Balloon Custom Twitter Feeds (Feeds for Twitter, sometimes referenced as X feeds) stores feed instances as ctf_feeds custom posts, caches Twitter API responses in wp_ctf_feed_caches and stores cached tweets in wp_ctf_feed_tweets, with API credentials in wp_options. The default plugin admin shows a per-feed customizer and a feed list, neither of which gives you a flat table of every feed, its source handle or list, last refresh, and current cache size.

SleekView reads the ctf_feeds CPT alongside the cache tables and surfaces feed name, source type (handle, list, hashtag, search, mentions), source value, layout (list, masonry, carousel), items per page, last refresh, cached tweet count, and error state as first-class columns. Saved views like all handle feeds, feeds with stale caches, or feeds throwing API errors are one click away.

Inline edits route through Smash Balloon's settings API so cache invalidation and Twitter API re-fetch fire correctly. Bulk actions cover refresh now, clear cache, and update source value. The Twitter API request counter stored in wp_options surfaces as a dashboard tile so quota usage is visible alongside the feeds driving it.

Twitter embeds carry an unusual amount of operational risk for what looks like a simple integration. API access rules change, rate limits get hit, handles get suspended, lists get reordered, and hashtags get hijacked. The default Smash Balloon admin treats each feed as a standalone object behind its own customizer, which is fine for editing one feed but wrong for monitoring fifteen across landing pages, blog sidebars, and event templates.

A flat table of every feed with its source, layout, last refresh, cached tweet count, and current error state answers the monitoring questions that the customizer cannot. Which feeds threw rate-limit errors last night, which feeds have not refreshed this week, which feeds point at a handle that just changed, which embeds are pulling from a list that the client just retired: these need a queryable surface, not a per-feed dialog. SleekView pivots the existing ctf_feeds CPT and the cache tables Smash Balloon already maintains into the table view that monitoring needs.

Social media managers, agencies on retainer, and support teams running mentions feeds all benefit from one screen that ties feed identity to feed health, while Smash Balloon keeps doing the actual fetching, caching, and rendering exactly as it does today.