The Gravity Forms Mailchimp add-on syncs entries to Mailchimp audiences (lists) based on per-form feed rules. Each feed under gf_form_meta defines the audience, the conditional logic and the field mapping for the sync. When an entry matches the rules, the add-on calls the Mailchimp API and records the subscriber ID, audience ID and sync outcome onto the entry as meta.

The default Gravity Forms admin shows the per-form Mailchimp feed configuration and surfaces individual sync notes inside each entry's detail view. It does not list signups across forms as a single table, filter by audience or sync outcome, or surface entries that should have synced but did not. Marketing teams that depend on Mailchimp as the lifecycle hub end up running CSV exports to figure out which audiences absorbed last week's signups.

SleekView reads gf_entry, gf_form_meta and the Mailchimp sync meta. Audience name, sync status, subscriber ID, tags and the sync timestamp sit as real columns next to entry ID and form. Sort by audience, filter to failed syncs across every form, bulk-export an audience-mix audit for the lifecycle team.

Mailchimp remains a default lifecycle hub for huge numbers of small and mid-sized WordPress businesses, and the Gravity Forms Mailchimp add-on is the most common bridge between site forms and the audience list. The data is captured cleanly, gf_entry holds the submission, gf_form_meta holds the feed configuration and gf_entry_meta holds the resulting subscriber ID and audience ID. What is missing is the table view.

Marketers should not be exporting CSVs every week to figure out which audience grew. Operations should not be paging through entries one at a time to confirm sync state. Growth leads should not be hopping between Mailchimp and WordPress to attribute list growth to the form that produced it.

SleekView reads what Gravity Forms already writes and renders it as the table the workflow always needed. Same Mailchimp integration data, finally surfaced as a single screen in WP Admin.