OneSignal's WordPress plugin runs the send-on-publish flow, and every time it tries (whether the send succeeds, fails, or skips) it writes the outcome to postmeta on the originating post. The default WP post list shows nothing about that. OneSignal's own dashboard shows aggregate subscriber analytics but not per-post send history at the WordPress level. The send-on-publish workflow has been quietly opaque for editors and ops.

SleekView Charts reads the per-post postmeta the plugin writes (sent timestamp, status, recipient count, last error, skip reason) and turns it into a dashboard. A number card counts successful sends in the last 30 days. A donut splits posts by send status (sent, skipped, failed). A bar of skip reasons surfaces the most common failure mode, almost always a fixable config issue. An area chart of weekly send volume tracks the publishing-channel cadence.

The data was always there. The plugin's own admin doesn't expose it because per-post history is per-post, and the plugin shows one post at a time. SleekView Charts pivots across posts and turns the publishing channel into something observable, which is exactly what an editorial-and-ops team needs to keep push as a reliable channel rather than a magic black box.

Push notifications are a publishing channel. Like email and social, they deserve observability proportional to the impact they have on reach. The current default for WordPress sites running OneSignal is that publishing-channel observability is one step removed: the post might or might not have pushed, the editor might or might not have noticed, and the only signal of a workflow gap is a quarterly engagement drop.

The data exists, in postmeta, written by the plugin every time it runs. But postmeta is per-post, and the questions editorial and ops want answered are cross-post. Did this week's releases all push.

Which writer's posts get skipped most. Which skip reason needs a process fix this month. SleekView Charts pivots the postmeta into chart cards and answers those questions in the place where publishing actually happens, which is WordPress.

The OneSignal app continues to handle aggregate subscriber analytics; the WP-side dashboard handles the channel-health story that the app can't see from its side of the API.