Social Locker by OnePress records unlock events per post in postmeta keys such as opanda_locker_views, opanda_locker_unlocks, plus per-network keys like opanda_unlocks_facebook. The stats screen exposes a raw count per locker, but offers no historical trend, no network ranking across all lockers, and no comparison between the locker variants you actually use on the site.

SleekView Charts reads wp_postmeta directly. Filter on the opanda_-prefixed keys, join to wp_posts by post_id for titles and publish dates, and every card type becomes possible. A Number KPI sums total unlocks, a Donut splits the network mix that visitors use to unlock content, a Horizontal Bar ranks lockers by performance, and an Area chart trends unlock activity against post publish dates.

Social Locker keeps gating content exactly as configured in its settings, and the unlock recording side stays untouched. The chart dashboard sits on top as a reading layer, so marketers and content teams finally see which gated content actually moves readers to share or follow, and which lockers should be retired or rebuilt.

Social Locker promises clear: hide content behind a share or follow gate and earn social distribution in return. The plugin records unlock events on each locker faithfully, but the stats screen shows them as raw per-locker numbers that do not answer the questions a marketing team actually has. Which lockers earn the most unlocks across the entire site? Which gating action (Facebook share vs Twitter share vs email subscribe) actually moves readers? Are unlocks trending up or down across publishing months, and which categories deserve more gated content? SleekView Charts treats the opanda_ postmeta keys as the dataset they already are.

A KPI for total unlocks, a donut for the action mix, a ranked bar of the top lockers, and a publish-date trend all sit on one saved dashboard. The gating stays untouched; what changes is that the data finally guides which lockers to keep, retire, or rebuild.