Instagram Feed Pro uses Smash Balloon's own table set for feed config (wp_sbi_feeds), cached feed output (wp_sbi_feed_caches), and connected sources or accounts (wp_sbi_sources) plus serialised settings in wp_options for global plugin config. Tokens and refresh metadata live alongside source records. The default Smash Balloon admin shows feeds in a paginated screen with a fixed column set; cached posts live behind individual feed-edit screens; source accounts live on a separate tab. None of those cross-cut into one queryable view, which makes ops at agency scale tedious.

SleekView reads the Smash Balloon tables directly. For feeds: feed type (user, hashtag, tagged, mentions), source account, layout (grid, masonry, highlight, carousel), header style, lightbox toggle, cache duration, and last-rendered date all become first-class columns. For sources: account handle, token expiry date, last sync, post count cached, and refresh status. For cached posts (when the cache is enabled): post type (image, video, carousel, reel), caption length, hashtag count, and cached timestamp. Saved views like feeds with token expiring in 14 days, hashtag feeds last refreshed over 48 hours ago, or feeds set to a stale layout load with one click.

Inline edits route through Smash Balloon's own update functions where they exist (feed config, layout, cache duration). For row-level cache invalidation SleekView calls Smash Balloon's documented cache clear hook, and token refresh prompts open the standard Smash Balloon reconnect flow. Posts and accounts stay on Instagram, the WP database stays the source of truth for feed config and cached output, and SleekView keeps the boundary honest.

Agencies running Smash Balloon's Instagram Feed Pro across many client sites face the same problem at every account review: which feeds are healthy, which have stale caches, and whose tokens are about to expire. The default Smash Balloon admin solves the single-site case fine, but a 40-client agency cannot click through 40 dashboards every Monday morning. Token expiry without a renewal queue means a feed quietly goes blank on a client's homepage and the agency hears about it from the client instead of catching it first.

Stale caches mean campaign hashtag feeds show last month's posts during this month's launch. Feed-type drift means somebody changed a hashtag filter and nobody noticed because the change lives inside wp_sbi_feeds with no audit. SleekView reads the Smash Balloon tables directly and exposes feed config, token status, and cache age as columns.

The agency's weekly check becomes a saved view and the renewal queue runs itself. Operations at scale needs the schema visible, and that is what SleekView gives Instagram Feed Pro users.