WP Content Pilot's campaign and log tables (wpcp_campaigns, wpcp_logs or their current equivalents), plus standard wp_posts columns and the campaign id stored in postmeta on generated posts. No external service is required.

Yes. A filter for a single campaign or a single date range in the table view applies to the chart view on the same dataset. Editors can pivot between row-level inspection and aggregate reporting without rebuilding filters.

Yes. Group log rows by campaign and status with a Stacked Bar card. Campaigns with high error counts stand out immediately, which is much faster than scrolling per-campaign log pages.

Yes for the standard wp_posts and campaign meta. Some pro-only sources (Envato, Amazon affiliate, premium AI integrations) record richer metadata that gives more columns to chart on, but the core campaign and post-status reporting works on the free build.

Yes. Group by post_date or run_date with an Area or Line card and pick a Count aggregation to see posts or runs per day or per week. Quarterly trend cards make growth or regression obvious.

Yes. Any filtered set behind a chart card exports to CSV with the same columns the table view would show, including campaign id, source, post_status and timestamps.

Indirectly. The plugin logs whether a rewrite endpoint returned a result, which becomes the success/failure split in the bar card. SleekView does not score rewrite text itself, that remains an editorial review step.

No. WP Content Pilot keeps running campaigns on its own schedule. SleekView Charts reads the resulting tables and renders them as a dashboard, so the plugin remains the source of truth for fetching, rewriting and scheduling.