Social Warfare Pro tracks share counts, Pinterest pin overrides, and click totals per post as postmeta on each wp_posts row. Keys like _shared_count_total, _shared_count_facebook, _shared_count_pinterest, and swp_cache_timestamp sit alongside Pinterest-specific overrides (swp_pinterest_image, swp_pinterest_description). The default WordPress post list does not surface any of this.

SleekView reads the swp_* and _shared_count_* meta keys directly and renders one row per post with per-network share columns next to title, author, post type, and date. The derived Total column drives sort, and a Cache freshness column reads swp_cache_timestamp so editorial knows whether the count is current or twelve hours stale.

Inline edits route through Social Warfare's own meta-update hooks where possible, so a custom Pinterest description set in the grid updates the same key the plugin's metabox writes. Bulk edits on editorial-owned columns (review status, refresh-by date) are SleekView-managed meta and never collide with the swp_* namespace the plugin owns.

Social Warfare Pro already collects per-post share counts per network and writes them to wp_postmeta as _shared_count_* keys, refreshed on the plugin's configured cache cycle. The default UI shows those numbers inside individual post metaboxes, which is fine for spot checks and useless for editorial planning at scale. Sorting by Pinterest alone, filtering by author and date, separating zero-share posts from low-share ones, exporting a 30-day cohort for the monthly report, none of those flows are first-class in the default admin even though the data is right there in postmeta.

SleekView turns the meta keys into a grid: one column per network, a derived Total, a freshness flag, and the standard post columns alongside. Editorial gets the 'what worked this month' view, marketing gets the network-mix narrative, and site auditors get the underperformer cohort all from the same screen. The same data Social Warfare already collects becomes queryable as a sortable, filterable, exportable view, which is the difference between knowing a post did well and knowing what to do next about it.

That gap is what closes when share-count meta moves from per-post metaboxes into a real table.