No. Subscribers, segments, and audience analytics live in the OneSignal cloud — that's where they belong, since they're managed across the entire delivery system. SleekView only reads the per-post send metadata that the WP plugin writes locally to postmeta. If you need subscriber data in WP, you'd need a sync layer using OneSignal's API, and SleekView would tabulate whatever that layer writes.

No. SleekView edits WordPress data; triggering a push uses OneSignal's send-on-publish flow which is configured per-post or via their API. The cleanest workflow is to fix the underlying issue (missing icon, draft status, etc.) inline in the post, then republish or use OneSignal's resend feature. SleekView gives you visibility into why something didn't push, not a manual trigger.

The OneSignal plugin writes a reason string to postmeta when it skips sending — common reasons include missing icon, draft status, post type not configured for push, or per-post override disabled. SleekView surfaces that reason as a column directly. No more guessing or opening each post to check the OneSignal section. The reasons are exactly what the plugin records.

Yes. Each site in a multisite network has its own postmeta and its own OneSignal config (with separate app IDs, typically). SleekView builds per-site views naturally, since it queries the active site's tables. For network-wide auditing, you'd switch sites and load the equivalent saved view on each — the view definitions can be exported and reused.

Yes. Any saved view exports to CSV directly with the columns and filters you've configured. Useful for monthly reporting, post-incident reviews after a delivery issue, or sharing data with stakeholders who don't have WP admin access. The CSV includes the same data visible in the table — what you see is what you get, no transformation in between.

Aggregate metrics — opens, clicks, conversions — live in OneSignal's app where they're computed across the entire subscriber base. SleekView shows the per-post send/skip/fail status from WordPress, which is the editorial signal. The two are complementary: SleekView answers 'did the push go out and to whom', and the OneSignal dashboard answers 'how did subscribers respond to it'.

Yes. Filter by sent timestamp within a range, group by author or category, and you have a per-period publishing report. Useful for editorial retrospectives, growth reviews, or reconciling a content calendar against actual push deliveries. Saved views make recurring reports a one-click load.

No. SleekView reads postmeta; if a different push plugin writes its own metadata keys, you can build a separate view scoped to that plugin's keys. Many sites run a backup notification system alongside OneSignal — surfacing both as parallel views lets ops compare delivery success rates and spot patterns where one channel routinely outperforms the other.