✨ 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 Carrd Newsletter: signups & list bridges as tables

Carrd Newsletter sits between embedded Carrd forms and your ESP, logging each signup locally and storing per-form list mappings in wp_options and wp_postmeta. SleekView turns those rows into a real auditable table.

♾️ Lifetime License available

SleekView table view for Carrd Newsletter for WordPress

Carrd embeds, real signup data in WordPress

Carrd Newsletter is a WordPress plugin that bridges embedded Carrd forms to whichever ESP the site uses. The plugin owns a small but operationally important slice of local state: API tokens and connection settings in wp_options as a serialized array, per-form list mappings in wp_postmeta, and a rolling signup log keyed by request ID that records the email, the source Carrd form and the ESP response code.

The default plugin UI presents the signup log as a paginated list with a fixed filter set, and the form mappings on a separate settings tab. There is no joined view that combines a signup row with the form that triggered it or the ESP response. There is no filter for signups that failed to deliver, no inventory of which forms still point at archived ESP lists, and no diff between staging and production capture configs. Operators end up SSHing in to grep the option row when something stops working.

SleekView reads each storage path directly and renders Carrd Newsletter as one workspace. Settings rows, form-bridge rows and signup-log rows live in the same table with joined columns for the source form, the ESP target, the consent text and a status pill. Edits route through the plugin's options API where supported so existing webhooks and WordPress hooks continue to fire on every change.

Workflow

Carrd Newsletter options, log and postmeta as a workspace

1

Pick the storage paths

Point SleekView at the Carrd Newsletter settings option, the signup-log option, and the _carrd_newsletter_* keys in wp_postmeta. All three render as one joined table.
2

Compose audit columns

Pivot the settings blob into named columns. Add per-form ESP target, payload shape, response code, retry count and consent text from postmeta and the log.
3

Save the views

Save filters for stale list targets, retry-queued signups, capture-script disabled on key pages, custom consent overrides. Each becomes a reusable operational audit.
4

Edit inline or bulk-update

Change a form's target list, repoint multiple forms to a new ESP list, or update consent copy across every form in one bulk edit. Hooks fire through the options API where supported.

Sample columns

A typical Carrd Newsletter signups view

Plugin settings live in wp_options. Per-form list IDs sit in wp_postmeta. The signup log lives in a dedicated option row.
Source: wp_options + wp_postmeta (Carrd Newsletter signup log, settings, per-form ESP mappings)
Source Email ESP target Consent When Status
carrd:landing-1 alex@studio.co mc:list-leads Default Apr 24 Synced
carrd:landing-2 ria@design.io ck:form-newsletter Custom Apr 23 Synced
carrd:webinar tom@hello.dev mc:list-webinar Default Apr 22 Retry queued
carrd:old-promo mia@brew.coop mc:list-archived Default Feb 11 List missing

Comparison

Default Carrd Newsletter UI vs SleekView

Default Carrd Newsletter UI

  • Signup log paginates with a fixed filter set
  • Per-form mappings live on a separate tab from the log
  • No filter for signups whose ESP target was archived
  • No diff between staging and production capture configs
  • No multisite roll-up for agency portfolios

SleekView

  • Signup log, form bridges and settings in one table
  • Filter signups by ESP target, consent override, or status
  • Surface retry-queued signups as a status pill
  • Inline-edit which list a Carrd form posts to
  • Multisite roll-up across every client in the network

Features

What SleekView gives you for Carrd Newsletter for WordPress

Unified signup log

Every signup row joins back to its source Carrd form and the ESP target list with the response code visible inline. Triaging a failed delivery becomes one filter instead of three tab switches.

Retry-queue visibility

Signups that fail on first ESP post are queued for retry with a counter and a next-attempt timestamp. SleekView surfaces both as a sortable column so ops can see what's still in flight.

Stale list detection

Filter signups by ESP list_id against the active list set in the connected ESP. Archived list rows surface as red so cleanup is one inline edit per form bridge.

Audience

Who uses SleekView for Carrd Newsletter

Growth marketers

Audit which Carrd landing pages produce the most signups and where the failed deliveries cluster. The signup log doubles as a top-of-funnel analytics table.

Integration engineers

Use the retry-queue and ESP response code columns to debug deliverability without parsing serialized option rows. Filter by status to find the rows that need attention.

Agencies

Multisite roll-up gives a portfolio-wide audit of every client's Carrd Newsletter wiring in one screen. Useful for compliance reviews and renewal kickoffs.

The bigger picture

Why a forwarding-receipt log earns a real table

Carrd Newsletter is the kind of bridge plugin that earns its place by quietly forwarding signups to the right ESP list, and it's exactly that quietness that hides the problems. When a signup fails to deliver, when an ESP archives a list that a Carrd form still points at, when legal rewrites consent copy in the ESP but the WP-side override carries the old wording, none of those failures surface in the default plugin UI because the UI is built for casual lookup not auditing. The data is all there in wp_options and wp_postmeta, the plugin's own forwarding receipts and form mappings, but it's stored as serialized blobs that the plugin's own screens never pivot into a workspace.

SleekView's contribution is the pivot. Once the log, the form bridges and the settings live in one table, every debugging question becomes a filter and every fix becomes a bulk edit. For growth marketers running multiple Carrd pages, the table doubles as a top-of-funnel analytics view.

For agencies running Carrd Newsletter across multisite networks, the network roll-up makes a portfolio-wide audit a screenshot rather than a project.

Questions

Common questions about SleekView for Carrd Newsletter for WordPress

Yes. The plugin's local signup log records each capture with the source Carrd form, the email, the ESP target and the response code. The log lives in wp_options as a paginated array keyed by request ID and rotates older rows out per the plugin's retention setting.

 

No. The signup log is a forwarding receipt, not a contact table. The contact record lives in the connected ESP (Mailchimp, ConvertKit, MailerLite, whichever is configured) once the post succeeds. SleekView audits the WP-side forwarding state, not the ESP-side contact record.

 

Yes. SleekView writes through the plugin's options API where supported so hooks fire as if the change came from the plugin's settings screen. Direct postmeta writes are available for bulk migrations.

 

Signups that fail on first send are flagged in the log row with a retry count and a next-attempt timestamp. SleekView renders that as an amber status pill and exposes the retry count as a sortable column.

 

Yes. If the site connects Carrd Newsletter to more than one ESP, every form's esp field shows on its row. Filter by ESP to scope the log to one provider, or leave the filter off for a unified deliverability view.

 

No. The log is paginated and indexed by request ID, form mappings live in wp_postmeta with normal indexes. Even sites with thousands of signups per day render in one paginated query.

 

Yes. SleekView reads each subsite's wp_{blog_id}_options and wp_{blog_id}_postmeta and renders a network roll-up. Agencies see every client's Carrd Newsletter state on one screen.

 

Contacts live in the connected ESP so subject-access requests run through that ESP's tooling. The local signup log is supporting evidence that shows when and from which Carrd page the contact opted in, which is useful for the export record.

 

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