The Gravity Forms Mailchimp add-on subscribes form submitters to a Mailchimp audience on entry creation. Subscription results land in wp_gf_entry_meta with keys for the Mailchimp subscriber hash, the audience ID, the subscription status (subscribed, unsubscribed, pending, cleaned, archived), and any feed delivery error if the API call failed. The default Gravity entries grid shows none of this without diving into each entry.

SleekView reads wp_gf_entry directly, joins to wp_gf_entry_meta, and surfaces every Mailchimp meta key as a groupable field. The natural one is the Mailchimp subscription status, which gives instant visibility into who actually subscribed versus who errored out of the feed. You can also group by destination audience for multi-audience forms, by Mailchimp tag applied, or by a custom Onboarding stage field your team adds.

Dragging a card writes the new value through GFAPI::update_entry and fires gform_post_update_entry. The Mailchimp add-on can be configured to retry feeds on entry update, so dragging from Errored back to Pending triggers a fresh subscription attempt. Unsubscribed and cleaned addresses are filtered out of active boards by default but can be exposed on a churn or hygiene board so the email team can see unsubscribe velocity and bounce rates.

The Gravity Forms Mailchimp add-on is excellent at subscribing form submitters to audiences, but its admin treats every signup as a row in the standard Gravity entries grid with no visibility into how the Mailchimp feed performed. That works when subscriptions rarely fail. It stops working the moment Mailchimp throttles for spam complaints, an audience is hitting bounce rate thresholds, or role-address signups are being silently rejected by the audience.

A kanban board fixes the part the add-on was never designed to fix: subscription health visibility. Each column shows how many entries are in each Mailchimp state per audience, so the email team can spot problems before they affect engagement rates. Status changes happen with a drag instead of opening each entry, and dragging from Errored back to Pending triggers a retry through the standard gform_post_update_entry hook the add-on already listens to.

Because every column maps back to real Mailchimp feed meta on the entry, the board is not a parallel system that drifts from Mailchimp. The end result is a Gravity admin that finally matches how email teams actually monitor and recover from delivery problems.