The Ninja Popups custom post type, its postmeta stats keys and the local subscribers table where the plugin stores opt-ins for local lists. SleekView does not call any external service to render the dashboard.

Yes. Group a Pie or Bar card by post_title or post ID and SleekView shows the conversion share or ranking by popup. Names come from the CPT, no manual mapping.

Yes. Group an Area or Line card by capture date or post_modified with a Count aggregation. Daily, weekly and monthly buckets are all available for campaign reviews.

If Ninja Popups stores a local row for each conversion, yes. If a popup is configured to push only to a third-party ESP with no local trace, those conversions live with the ESP and SleekView does not fabricate them.

Yes. The ESP target is stored as meta on each popup CPT row. A Pie or Bar grouped by that meta gives a one-glance ESP routing audit, useful for GDPR documentation and migrations.

Yes. Any filtered set behind a chart exports as CSV with the same columns the Table view would show. ESP imports and quarterly briefings draw from that filtered set.

Yes. The Table view edits the popup CPT through wp_update_post and update_post_meta, so registered actions on those rows fire normally. Chart cards refresh against the updated rows on the next view.

Yes. Add a filter on the popup or on a campaign tag stored in meta. Every chart card narrows to that campaign, and the saved view becomes the team's reporting page for it.