WP Content Pilot Pro is the Pro extension of the WP Content Pilot auto-blogging plugin. Each campaign is stored as a custom post type (typically wp-content-pilot on most installs) with its source, frequency, and template kept in wp_postmeta. Run logs, counters, and global settings live in wp_options. The default campaign screen lists configurations clearly, but the relationship between a campaign and the posts it has created, the runs that succeeded or failed, and the sources that still produce content sits across multiple post-meta keys and option payloads.

SleekView reads the campaign post type, joins wp_postmeta for source, frequency, and template, and pulls run logs from wp_options. Each campaign becomes a row with its source URL, last-run timestamp, last-run status, total posts created, and template as first-class columns. Posts created by a campaign are also linkable through their author, parent, or a custom meta key the plugin sets at publish time, so reviewers can drill into the content the campaign produced.

Inline edits route through the campaign post type's standard update path. Changing a frequency or pausing a campaign updates wp_postmeta in the structure the plugin expects on the next cron tick. Reviewer columns and notes live in a separate SleekView annotation table so the campaign record itself stays intact.

Auto-publishing setups quietly accumulate failures unless someone watches the run log carefully. Sources get rate-limited, API tokens expire, templates drift, and a campaign that produced ten posts a week silently drops to zero. WP Content Pilot Pro keeps the data needed to spot those failures, but the campaign screen and the run log live in different places, and the relationship between a campaign and the posts it produced sits behind a meta key that the default UI does not promote as a column.

SleekView turns that relationship into a single grid. Each campaign row shows the source, the frequency, the last-run status, and the post count, with run-log highlights joined in from wp_options. Saved views capture the operator workflows that matter: failing campaigns by source, top performers by post count, and rescheduled or paused campaigns from the last week.

Inline edits flow through the plugin's standard post-type update path so the next cron tick reads the updated state correctly. The result is a content-operations control panel built on top of the data the plugin already records, with no new tables and no behavioural changes to the campaigns themselves.