SleekView for Campaign Monitor Pro: API send logs as tables
Campaign Monitor Pro relays mail through the Campaign Monitor v3 API and syncs subscriber lists locally. SleekView turns the send log and list-sync cache into a sortable workspace inside WP Admin.
♾️ Lifetime License available
Send logs and list sync without a dashboard detour
Campaign Monitor Pro sends transactional mail through the Campaign Monitor v3 API and mirrors subscriber lists in a local cache table. API key and client ID sit in wp_options under campaignmonitor_pro_options, the send log lands in wp_campaignmonitor_pro_log with status and API response, and the subscriber cache lives in wp_campaignmonitor_pro_subscribers with list ID, custom fields, and sync timestamps.
The default admin separates the credentials tab, the list-sync tab, and the log viewer. Saved views are not part of the plugin; per-row retry only. Joining a recipient's send history to their subscriber-list state requires cross-tab navigation, and bulk re-subscribe / unsubscribe is hidden behind dropdown actions rather than as inline operations on a filtered cohort.
SleekView reads the log and the subscriber cache directly, joins recipient email to subscriber state, and exposes API code, list membership, and custom-field values as filterable columns. Bulk subscribe/unsubscribe routes through the plugin's API calls so upstream state stays in sync.
Workflow
Campaign Monitor cache and log as a workspace
Map the cache and log
wp_campaignmonitor_pro_subscribers and wp_campaignmonitor_pro_log. List memberships, custom fields, and API responses become first-class columns.
Join sends to subscribers
Save the segments
Bulk list operations
Sample columns
A typical Campaign Monitor Pro view
wp_options (campaignmonitor_pro_options) + wp_campaignmonitor_pro_log + wp_campaignmonitor_pro_subscribers
| Recipient | Subject | Status | API code | Lists | Sent |
|---|---|---|---|---|---|
| alex@studio.co | Order #1042 confirmation | Accepted | 201 | Customers, VIP | Apr 24 |
| ria@design.io | Newsletter Apr | Accepted | 201 | Newsletter | Apr 24 |
| tom@hello.dev | Welcome | Pending sync | 202 | Trial | Apr 23 |
| mia@brew.coop | Re-engagement | Unsubscribed | 400 | Newsletter | Apr 22 |
Comparison
Default Campaign Monitor Pro admin vs SleekView
Default Campaign Monitor Pro admin
- Credentials, sync, and log split across tabs
- No saved-view layer on the local log
- Subscriber state join with sends requires cross-tab work
- Bulk subscribe/unsubscribe lives behind dropdown actions
- Per-source attribution requires the Campaign Monitor dashboard
SleekView
- Send + subscriber join in one workspace
- Filter by list, API code, and custom-field value
- Bulk subscribe/unsubscribe through the plugin's API
- Saved cohorts for re-engagement and high-LTV segments
- Sync timestamp surfaced as a column for staleness checks
Features
What SleekView gives you for Campaign Monitor Pro
Send + subscriber join
Each send-log row carries the recipient's current list memberships and custom-field values from the local cache. The join makes per-recipient targeting and audit a same-screen operation.
List + field filtering
Filter subscribers by list, by custom-field value, and by API send history together. Build re-engagement and VIP segments without leaving the workspace.
Bulk list operations
Select rows and add or remove list memberships through Campaign Monitor's API. Upstream state stays in sync; the plugin's subscribe hooks fire on each change.
Audience
Who uses SleekView for Campaign Monitor Pro
Email marketers
Build segments by combining list membership, custom-field values, and API send history. Save segments as named views and target them from the next Campaign Monitor send.
List managers
Bulk re-list or unsubscribe across thousands of subscribers in one action. Post-event cleanup and import reconciliation happen inline rather than per-row through dropdowns.
Growth ops
Per-source attribution by joining the subscriber cache with WooCommerce orders or WPForms entries. Compare engagement and lifetime conversion across capture sources.
The bigger picture
Why API-based senders need a joined workspace
Campaign Monitor's plugin is a respectable API client, but the WP-side data it mirrors is split across a subscriber cache and a send log that the default UI keeps in separate tabs. Most of the operational work an email team does sits at the intersection of those two tables: cleaning up after an offline event, building a re-engagement segment from low-recent-send recipients, auditing per-source attribution by joining capture data to engagement history. The data is local, well-indexed, and queryable, but the default plugin does not expose the join.
SleekView reads both tables, joins them on recipient email, and exposes list, custom-field, API code, and source as filterable columns. Email marketers build segments without leaving the workspace. List managers run bulk subscribe and unsubscribe operations inline.
Growth ops compare engagement across capture sources to see which channels deserve more budget. The plugin keeps owning the API calls, the sync handler, and the retention policy. SleekView gives the resulting data the workspace it has lacked.
Questions
Common questions about SleekView for Campaign Monitor Pro
No. Campaign Monitor's segment builder stays in place and continues to power campaigns. SleekView gives the row-level workspace for triage, ad-hoc segmentation, and bulk operations the default plugin UI does not surface as easily.
 Yes. SleekView writes through the Campaign Monitor API where supported, so registered subscribe and update hooks fire as expected. Direct cache writes use conflict detection for cases where the upstream sync should be skipped.
 Both. Transactional sends land in the send log; broadcast sends from Campaign Monitor surface in the same row format when the plugin records them locally. Filter by source field to split the two cohorts.
 No. The plugin's sync handler trims stale rows on its configured retention setting. SleekView respects the limit and does not extend retention or duplicate rows.
 Yes. Saved views export to CSV with the filtered cohort. Useful for documenting list-cleanup operations or sharing a segment with the campaign team for review.
 When the local cache and the Campaign Monitor list disagree, SleekView surfaces the conflict as a flag column. Resolution routes through the plugin's sync handler so upstream state owns the canonical record.
 Deletes and PII redaction route through the plugin's own retention and erasure hooks where available. Redaction status surfaces as a column so audits stay truthful about what data remains in the cache.
 Yes. The source field on the subscriber cache, when set by the originating plugin (WPForms, WooCommerce, manual import), becomes a first-class filter. Per-source cohorts become saved views.
 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 checkoutBrowse more
- Edd Software Licenses
- Woocommerce Shipping Usps
- Cartflows
- Stripe For Woocommerce
- Checkoutwc
- Wholesale Suite
- Woocommerce Multilingual Currency
- Woocommerce Bol Com
- Woocommerce Order Status Control
- Givewp
- Woocommerce Gift Registry
- Woocommerce Klarna Checkout
- Woocommerce Stock Notifier
- Aelia Prices By Country
- Shipstation Woocommerce