✨ 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 Revue Newsletter for WordPress: subscribers & issues as tables

Revue Newsletter for WordPress stores issue configuration as a CPT with wp_postmeta and embed settings in wp_options. SleekView reads them so issues, sign-ups, and embed performance live in one filterable workspace.

♾️ Lifetime License available

SleekView table view for Revue Newsletter for WordPress

Issue audits without opening each post

Revue Newsletter for WordPress wraps the Revue service inside WordPress. Issues are stored as a custom post type with their schedule, audience, and external Revue ID in wp_postmeta, and the embed/sign-up shortcode configuration lives in wp_options. Local sign-up logging is optional, and when enabled writes to a separate log CPT. The authoritative subscriber list lives on Revue's upstream service.

The default admin screens edit one issue at a time and surface a fixed list of recent sign-ups (if logging is on). Cross-cutting questions like "which issues were scheduled but never sent" or "which embed produced the most confirmed sign-ups last month" don't appear as default views. Editing the audience selection on a batch of issues requires opening each one. Per-embed performance comparison and referrer attribution need either external analytics or manual SQL against wp_postmeta.

SleekView reads the issue CPT, the log CPT, and the wp_options keys, joins their related wp_postmeta rows into named columns, and exposes saved views per issue status, per embed, and per referrer. Issue audits become a filter on send status; sign-up cleanup becomes inline editing; referrer attribution becomes a saved view that the next campaign can target.

Workflow

Revue issues and logs as a workspace

1

Map the issue and log CPTs

Point SleekView at the revue_issue CPT and the optional revue_log CPT. Each becomes a navigable workspace with the plugin's stored columns.
2

Pivot postmeta and options

Promote audience, scheduled_at, external_id, and embed-config keys from wp_options into named columns. Filters and sorts run on those values directly.
3

Save the audits

Build saved views for stuck drafts, upcoming sends, per-audience performance, and per-embed attribution. Each saved view is a workspace the team revisits each week.
4

Edit and bulk-reschedule

Update audience or schedule inline. Bulk actions route through the plugin's save_post hook so cron-based dispatchers continue to pick up changes correctly.

Sample columns

A typical Revue issues view

Issues with audience, schedule, and send status pulled from wp_postmeta.
Source: wp_posts (post_type=revue_issue, post_type=revue_log) + wp_postmeta + wp_options
Issue Status Audience Scheduled Sent Sign-ups
Spring digest Sent All subscribers Apr 22 Apr 22 412
Founder note Sent Paid only Apr 18 Apr 18 118
Product launch Scheduled All subscribers May 02 (pending) 0
Draft brief Draft (none) (none) (none) 0

Comparison

Default Revue Newsletter for WordPress admin vs SleekView

Default Revue Newsletter admin

  • Issues list lacks an audience column from wp_postmeta
  • No bulk reschedule or audience update across issues
  • Embed/shortcode configuration sits in wp_options without per-embed analytics
  • Sign-up log (if enabled) renders as a fixed list with no referrer filter
  • Per-issue performance comparison requires opening each issue individually

SleekView

  • Joined issue + audience + status + sign-up-count view
  • Filter by scheduled vs sent vs draft with one toggle
  • Pivot embed config from wp_options into a comparison table
  • Bulk reschedule or change audience on selected issues
  • Save per-embed and per-referrer attribution views

Features

What SleekView gives you for Revue Newsletter for WordPress

Issue audit

Filter by send status, audience, and scheduled date in one view. Spot stuck drafts and missed sends without clicking through the issue list one row at a time.

Bulk reschedule

Select rows and update scheduled_at or audience in one action. Writes route through the plugin's save_post filters so any registered hooks fire normally.

Embed attribution

Join the log CPT with referrer postmeta to compare per-page sign-ups. Saved views surface which content keeps producing the most verified subscribers.

Audience

Who uses SleekView for Revue Newsletter for WordPress

Editors

Issue audit workspace with audience and schedule visible inline. Catch stuck drafts and audience mismatches before the next send window closes.

Newsletter operators

Bulk reschedule or shift audience targeting across upcoming issues in one pass. The same workspace handles cleanup of cancelled or duplicate issues.

Growth marketers

Per-embed and per-referrer cohorts joining the sign-up log with the issue performance data. Compare conversion across paid and organic placements.

The bigger picture

Why issue audits deserve a workspace

Newsletter operations live on cadence: scheduled sends, audience updates, draft reviews, post-send attribution. Revue Newsletter for WordPress handles the local side of those concerns with a CPT and postmeta, but the default admin renders each issue as a separate edit screen rather than as a workspace of rows. Operators end up clicking through the issue list to verify scheduling, opening each issue to check the audience, or running SQL to compare per-embed sign-up performance.

The data is all there in wp_postmeta and the optional log CPT, well-structured and queryable. SleekView's joined view surfaces it as filterable columns. Editors get a daily standup workspace with status and audience inline.

Newsletter operators get bulk reschedule and audience-shift workflows. Growth marketers get per-embed and per-referrer attribution joined to the local sign-up log. The plugin keeps doing what it does best (talking to Revue's service); the WP Admin side becomes operationally usable for teams running more than a few issues a month.

Questions

Common questions about SleekView for Revue Newsletter for WordPress

Yes, exactly as before. SleekView only changes how the plugin's locally stored data renders in WP Admin. The upstream sync, scheduled sends, and authoritative subscriber list remain on Revue's service. SleekView never calls external APIs on behalf of the plugin.

 

Yes. Audience changes write through the plugin's save_post hook, so any registered observers fire normally. Direct wp_postmeta writes are available for bulk corrections that should skip hooks, typically large audience reassignments during a list migration.

 

SleekView writes the scheduled_at postmeta and the plugin's cron handler picks it up on the next run. Bulk reschedules update the meta and let the plugin's existing scheduler do the actual dispatch. SleekView does not run its own send queue.

 

Yes, when local logging is enabled. The log CPT is a first-class workspace with referrer, embed id, and timestamp pivoted out of wp_postmeta into named columns. Filtering and sorting work directly on those values.

 

No. Queries paginate and rely on the indexes WordPress maintains on wp_postmeta by post_id and meta_key. Issue lists in the low thousands render smoothly because the joins use those indexes rather than scanning meta.

 

Yes. Whatever the plugin writes to wp_postmeta as the audience selection (segment id, tag, or boolean flags) becomes a first-class filterable column. Build saved views per audience to see which segments get hit most often.

 

If the plugin still writes the imported issue records to its CPT, SleekView reads them. Older plugin versions that stored issues only as transients are not covered because there is no persistent local data to expose.

 

Yes. Any saved view can be exported to CSV including the joined postmeta columns. Use this for board reports, content audits, or to feed historical issue performance into an external analytics tool.

 

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