Social Snap is a feature-dense social plugin: share buttons, click-to-tweet boxes, click-tracking, and a stats screen with per-post breakdowns. The data behind it (per-network share counts, click totals per network, click-to-tweet engagements) lives as postmeta keys (social_snap_shares, social_snap_clicks, and the click-to-tweet variant) on each post. The default Social Stats screen surfaces top performers and trends; cross-cutting analysis sliced by author, post type, or date range with all three signals attached lives as ad-hoc work outside the plugin.

SleekView reads those keys and pivots them into one sortable grid. One row per post; columns for per-network shares, click totals, click-to-tweet engagements, plus standard post fields. The combination is what makes this useful: a post with high shares and low clicks distributes but does not engage; a post with high click-to-tweet and low overall shares has one viral quote-pull moment. Both patterns matter for editorial follow-ups, both are invisible without the per-signal column view.

The Last refresh column is the honesty anchor. Social Snap refreshes counts on its configured cache duration. Tag stale-cache rows and a campaign-report number is either current or labeled as 12 hours old before it goes into a screenshot. Editorial reports stop quoting yesterday's numbers as today's by accident.

Social Snap collects three editorially distinct signals: share counts (how far did the headline travel), click totals (how much traffic did the buttons actually drive), and click-to-tweet engagements (which quote-pulls earned their own micro-distribution). Each signal answers a different editorial question, and the answers are most useful when read together: a post that scored high on shares but low on clicks is a different problem from one with the inverse pattern. The default Social Stats screen presents these signals in trend charts and top-N lists, which is fine for verification and incomplete for strategy.

Cross-cutting analysis (filter by author, sort by clicks, export the cohort) lives as ad-hoc work outside the plugin even though all three signals are right there in postmeta. SleekView reads social_snap_* meta directly and pivots it into a multi-signal grid. The same data the plugin's stats screen samples becomes a queryable, filterable, exportable editorial surface, which is the difference between a plugin that tracks three signals and a plugin whose tracking actually drives three editorial decisions.