✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for WP Content Pilot

SleekView reads wpcp_campaigns, wpcp_logs and the wp_posts rows WP Content Pilot generates, then exposes campaign, source type, status and post_date as columns you can sort, filter and edit inline.

♾️ Lifetime License available

SleekView table view for WP Content Pilot

Per-campaign log pages are fine. A unified table is what ops needs.

WP Content Pilot runs campaigns that pull from feeds, YouTube, Amazon, Envato and similar sources, optionally rewrites the result with an AI provider and writes the post into wp_posts. The plugin maintains campaign rows in wpcp_campaigns and per-run rows in wpcp_logs. The admin shows a campaign list and a per-campaign log page.

That works for inspecting one campaign at a time. It does not work for the operational view where ops needs all generated posts across all campaigns in one filterable table, with campaign name, source type, run status and post_status as real columns.

SleekView reads the campaign rows, the log rows and the generated wp_posts together. A single table lists every generated post with its campaign and source, plus the run status from the matching log row. Filter by campaign, by status, by date range, by source type. Edit post_status inline. Export the filtered set to CSV for a monthly review without leaving WP admin.

Workflow

How SleekView reads WP Content Pilot data

1

Pick the source tables

Choose wp_posts as the row source and join wpcp_campaigns plus wpcp_logs (or current equivalents) on the campaign id stored in postmeta on each generated post.
2

Compose the column set

Pick post_title, post_status, post_date, campaign name, source type, log status and any custom column the campaign stores. The agent UI surfaces keys actually present in the install.
3

Save and scope the view

Name it ("Pending posts", "Failing campaigns", "This week's output") and gate by capability so editors, ops and the site owner each get a tailored column set.
4

Edit inline and export

Move posts to publish in bulk, push selected drafts to trash, export the filtered table to CSV. All edits flow through the standard WordPress post hooks.

Sample columns

A typical WP Content Pilot output view

SleekView joins generated posts with their campaign and the most recent run log, so source type and log status sit next to post_status and post_date.
Source: wp_wpcp_campaigns + wp_wpcp_logs + wp_posts
Post Campaign Source Post status Run status Date
10 budget DSLR cameras Camera deals amazon Publish Success May 14
Latest from YouTube travel Travel videos youtube Draft Success May 14
Weekly tech RSS roundup Tech feeds feed Publish Success May 13
Envato themes envato Error May 13
5 podcast mic picks Audio gear amazon Pending Success May 12

Comparison

Default WP Content Pilot admin vs SleekView

Default WP Content Pilot admin

  • Per-campaign log pages, no unified table across campaigns
  • Campaign name and source type not visible on the standard Posts screen
  • Run status hidden behind log pages, not joined onto post rows
  • Bulk edits require switching to the WordPress Posts screen and losing context
  • No saved per-role view for editors, ops and ownership

SleekView

  • Read wpcp_campaigns, wpcp_logs and generated wp_posts as one dataset
  • Surface campaign name, source type and run status as real columns
  • Inline bulk-publish or trash generated posts through regular post hooks
  • Save filtered views per role ("Pending posts", "Failing campaigns")
  • Export the filtered table to CSV for a monthly campaign review

Features

What SleekView gives you for WP Content Pilot

Posts joined to their campaign

Generated posts arrive with campaign name, source type and the matching run-log status. No more switching tabs to learn where a post came from.

Cross-campaign filtering

Filter by source type, by run status or by date range across every campaign at once. Failing feeds and over-producing campaigns show up in the same view.

Inline edits without losing context

Bulk-flip post_status, trash low-quality runs and update tracking meta without leaving the table. WP hooks and email triggers fire as usual.

Audience

Who uses SleekView for WP Content Pilot

Affiliate site operators

One filtered table for every campaign, sorted by date, grouped by source. Bulk-publish the keepers, trash the misses, never leave WP admin to do it.

Aggregator sites

Watch the Run status column for errors. A failing feed surfaces immediately instead of after a week of empty daily runs.

Agency content ops

Each client install gets its own saved view for the monthly review. Filter by date, export to CSV, hand the result to the account manager.

The bigger picture

Why aggregator campaigns need a unified output table

WP Content Pilot's value is volume across many sources, and volume is what makes the default per-campaign log pages fall over operationally. Ops cannot answer "what did we ship last week" by opening five log pages in turn. A unified table joining wp_posts to wpcp_campaigns and wpcp_logs makes campaign name, source type and run status first-class columns, which is what filtering and bulk actions actually need.

Inline post_status edits run through wp_update_post so scheduled publish, sitemap regeneration and SEO plugin hooks all behave normally. Same campaign rows, same log rows, completely different operating posture toward the channel.

Questions

Common questions about SleekView for WP Content Pilot

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

 

Yes. SleekView writes through wp_update_post and wp_trash_post so transition_post_status, save_post and the usual SEO and sitemap hooks fire normally. Bulk operations iterate through the same path.

 

Yes. Filter the table by run status equals error. Failing campaigns surface immediately, usually pointing to a deprecated feed, a rate-limited API or a changed rewrite endpoint.

 

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

 

Yes. Filter by campaign id and save the result as a named view ("Camera deals only"). Useful when an affiliate manager focuses on one campaign during a launch week.

 

Yes. Any filtered set exports to CSV with the columns currently shown, including campaign, source, post_status and run_status. Useful for monthly reviews and for handing samples to feed maintainers.

 

Yes if you add post_content as a column. Most editorial teams keep that off the default table for performance and add it on a per-row detail view instead. The plugin's rewrite step is unchanged by SleekView.

 

No. WP Content Pilot keeps running campaigns on its own schedule. SleekView reads its tables and presents them as a unified, sortable, editable table. The plugin remains the source of truth for fetching, rewriting and scheduling.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView