The Ninja Forms Mailchimp add-on takes a form submission and pushes the subscriber into a Mailchimp audience as part of the submit flow. The add-on writes the API result back into the entry meta of the Ninja Forms entry: whether the subscriber call succeeded, what subscriber status Mailchimp returned, and any merge field IDs. Under Ninja Forms > Submissions you only see the form fields. The Mailchimp result is buried in entry meta.

SleekView reads from wp_nf3_submissions and the postmeta keys the Mailchimp add-on writes for each entry, including _mailchimp_status, _mailchimp_list_id, _mailchimp_email_id, and _mailchimp_tags. The subscriber status field is the natural grouping axis since Mailchimp uses a small set of clear states: pending, subscribed, unsubscribed, cleaned, and archived. Each card shows submitter name, email address, audience name, and the relative time since signup.

Dragging a card writes the new subscriber status back to the entry meta and fires the standard Ninja Forms entry update hook. Marketing teams use this as a visual signal of list health, while still relying on Mailchimp itself as the source of truth for the actual subscription state. Cleaned and unsubscribed cards stay in their own lanes instead of mixing with active subscribers, so the marketing review surface stays clean and scannable.

The Ninja Forms Mailchimp add-on does its job cleanly at the submit step. The form submits, the add-on calls Mailchimp, the API responds, and the result gets written back to entry meta on the Ninja Forms entry. The problem is everything that happens after that.

The Ninja Forms submissions screen treats every entry as just one row in a list, even though the entries that ran through Mailchimp carry a totally different lifecycle: pending double opt-in, subscribed, unsubscribed, cleaned, archived. A flat list buries the Mailchimp result in meta keys you only see when you click into an individual entry, which means marketing ends up logging into Mailchimp itself just to check whether yesterday's signups confirmed their double opt-in or whether the latest paid campaign is generating clean leads. A kanban board fixes the visibility gap by treating Mailchimp subscriber status as the primary axis and per-audience totals as first-class information.

The pending column shows yesterday's signups that have not yet confirmed, the subscribed column shows the active list growth, the cleaned column shows list hygiene problems, and the unsubscribed column shows opt-out volume. Because the board writes back to the same Ninja Forms entry meta, downstream Ninja Forms actions and internal automations keep firing exactly as they did before, but the marketing team finally has a list health surface inside WordPress itself.