SleekView for Newsletter Glue
SleekView reads the Newsletter Glue newsletter custom post type and the postmeta that records ESP, list target, send date and status. Every newsletter renders as a sortable, filterable row with real columns instead of values buried behind the editor.
♾️ Lifetime License available
Newsletter Glue stores every newsletter as a post. The editorial table is what's missing.
Newsletter Glue treats each newsletter as a Gutenberg-authored post. Newsletters live as a custom post type (newsletterglue or as standard posts with newsletter blocks, depending on the install). Send metadata, the chosen ESP, the target list ID, the send date and the post-send status, lives in postmeta on each newsletter post.
The plugin's UI focuses on authoring and sending. Reporting on send activity, which lists are receiving the most sends, which ESP is in use most, when the editorial team last shipped a newsletter, depends on the connected ESP's dashboard. The WordPress-side picture, the editorial cadence and routing audit, isn't surfaced as a list.
SleekView reads the newsletter post type and its postmeta directly. Title, ESP, list target, send date and status sit as real columns. Sort by send date for the recent cadence, filter to send_status=failed for a quick retry pass, bulk-flip drafts to scheduled without opening each editor.
Workflow
How SleekView reads Newsletter Glue data
Pick the newsletter post type
Pull the ESP routing meta
Save and scope the view
Edit inline or export
Sample columns
A typical Newsletter Glue newsletter table
post_type = newsletterglue + postmeta (esp, list_id, send_date, send_status)
| Newsletter | ESP | List target | Send date | Status | Author |
|---|---|---|---|---|---|
| Weekly digest #214 | Mailchimp | Main list | May 15 | Sent | alex |
| Product launch alert | ConvertKit | Customers | May 13 | Sent | ria |
| Pricing update | ActiveCampaign | Pro segment | May 12 | Failed | tom |
| Onboarding series 3 | Mailchimp | New signups | — | Scheduled | mia |
| Quarterly roundup | Mailchimp | Main list | — | Draft | leo |
Comparison
Default Newsletter Glue admin vs SleekView
Default Newsletter Glue admin
- Plugin UI is authoring-first, no cross-newsletter list view
- Send routing (ESP, list target) is visible per-post only
- No filter for send_status=failed across the full archive
- Bulk actions on newsletters are limited to standard WP operations
- No saved per-role view for editors, ops or growth
SleekView
- Read directly from the newsletter post type joined with its postmeta
- ESP, list target and send status as sortable, filterable columns
- Inline-edit status and target across many rows in one pass
- Save filtered views ("Failed sends", "This month's cadence")
- Same workspace covers single-ESP and multi-ESP setups
Features
What SleekView gives you for Newsletter Glue
Sends as real columns
Surface ESP, list target and send status alongside title and date. The newsletter archive moves from a post-list scan into a sortable send table.
Filter to failed sends
Filter to send_status=failed and the table lists every send that didn't make it through. Bulk-retry from the table or open the row in the editor for an inline fix.
Edit routing inline
Flip a list target or ESP without opening the editor. Standard CRUD ensures Newsletter Glue's hooks fire on save so the send pipeline picks up the change.
Audience
Who uses SleekView for Newsletter Glue
Editorial leads
Audit the editorial cadence in one screen. Sort by send_date and confirm the weekly newsletter is actually shipping and that authors are picking the right list.
Operations
Audit ESP routing across the full send history. The table reveals whether the migration to a new ESP actually happened or whether old sends still go to the previous tool.
Growth leads
Cross-reference list targets with ESP-side open rates to plan list consolidation. The WP-side audit gives the inventory, the ESP gives the engagement signal.
The bigger picture
Why Newsletter Glue needs a real send table
Newsletter Glue is honest about its scope, it ships newsletters from Gutenberg to the ESPs that own delivery and engagement reporting. That leaves a real WordPress-side surface uncharted: the editorial cadence, the ESP routing audit and the list-target coverage. The default plugin admin is authoring-first by design, so the strategic question, are we actually shipping the weekly newsletter and is it going where we said, becomes a manual sweep through the post list.
SleekView reads the newsletter post type and its postmeta and renders the answer as a sortable, filterable table. Failed sends become a saved filter, ESP routing becomes a sortable column and editorial cadence becomes a date sort. The plugin keeps shipping newsletters, the table layer adds the editorial workspace authoring tools cannot produce.
Questions
Common questions about SleekView for Newsletter Glue
The Newsletter Glue plugin's own storage: the newsletter post type (or posts flagged as newsletters) and the postmeta that records ESP, list ID, send date and post-send status. No call to the connected ESP is required for the table layer.
No. Open and click rates live in the connected ESP (Mailchimp, ActiveCampaign, ConvertKit, Campaign Monitor, others) and stay there. SleekView focuses on the WordPress footprint: which newsletters shipped, when and to which list.
Yes. Newsletter Glue supports per-newsletter ESP selection, and the chosen ESP lives in postmeta. The table column surfaces every ESP in use so a multi-ESP setup produces one clean routing audit.
Yes. WordPress core indexes the post type by status and post_date, and SleekView reuses those indexes for the group-by queries. Sites with thousands of newsletters render the table within seconds.
Yes. Each multisite blog has its own Newsletter Glue posts and meta. SleekView reads the dataset on each blog, and a network rollup is possible by joining across blogs.
Yes. Bulk-retry routes through the plugin's send flow so any post-send hooks fire. Useful for clearing a batch of failures after a temporary ESP outage.
No. The table layer is read-mostly against the newsletter posts and meta. Newsletter Glue continues to route sends to the connected ESP through its own send flow on its own schedule.
Yes. The current filter set exports to CSV. Useful for sharing the editorial cadence with leadership or archiving a snapshot before an ESP migration.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout