Monarch by Elegant Themes caches per-network share counts as et_social_* postmeta keys on every post that carries a share button. The bundled Stats panel shows top-shared posts and a small set of breakdowns, designed for a glance rather than an audit. The data is much richer than the panel exposes, especially on Divi sites where Monarch is often the only share-tracking surface installed.

SleekView reads the same et_social_* keys, derives a Total column from the per-network values and renders the cache as a queryable per-post grid. Filter to posts with zero Pinterest shares to find the visual-content backlog. Filter to high-Facebook plus low-LinkedIn rows to spot the audience-mismatch cohort. Sort by Total to plan refreshes against the real top hundred rather than the bundled top five.

The plugin keeps owning button rendering and cache refresh. The table view owns the per-post audit, so the cached data Monarch already maintains stops hiding inside postmeta and becomes a working editorial surface on a Divi or Elegant Themes site.

Monarch's value proposition is that it captures share counts at all, on a refresh schedule the network APIs still allow. The numbers sit in et_social_* postmeta as a small structured dataset on every post that carries a Monarch button. The Stats panel turns that dataset into a top-shared list, which is fine for spotting hits and incomplete for everything editorial teams want from it.

SleekView reads the same keys and renders them as a queryable grid, with per-network columns, a derived Total, last-cached timestamps and joined author and post fields. Filters stack into one query, so the Pinterest backlog, the high-Facebook-low-LinkedIn cohort and the stale-cache rows become one-click views rather than spreadsheet exports. Monarch keeps doing what it does on Divi sites; the table view turns its cache into the editorial surface it always could have been.