Yes. The Mailchimp action writes its result to postmeta on every nf_sub entry, using keys like _mailchimp_list_id, _mailchimp_status, and _mailchimp_email. SleekView discovers those keys and exposes them as group-by and aggregation options without per-action setup.

Yes. _mailchimp_status stores subscribed, pending, unsubscribed, and error states returned by the Mailchimp API. Build a Pie or filter to error and put a count card next to it so the team sees and chases broken syncs.

Yes. Group by _mailchimp_list_id to see distribution across audiences. Add a tag filter if your action also writes Mailchimp tags as separate meta keys, since SleekView discovers those at query time.

Aggregations run as SELECT ... GROUP BY queries against indexed columns on nf3_submissions and the related postmeta. Card render time depends on the index on the group-by column more than raw row count, so high-volume signup forms stay responsive.

Cards re-query on view load and filter change. Set a refresh interval per view if a campaign dashboard needs near-live counts. Idle dashboards don't poll the database, so a closed view doesn't add load.

Yes. Save views and scope them per WordPress role or capability. Newsletter team gets a per-list signup dashboard, form admins get a sync-error view, sales ops get attribution charts. Personal filters stay scoped to the user.

Entries without Mailchimp meta keys are excluded from cards filtered to _mailchimp_list_id. To see total submissions versus synced submissions side by side, pair a Number card on all entries with another scoped to entries carrying the Mailchimp meta.

Each card exports aggregated rows as CSV with the group-by labels and the counts. Useful for handing the newsletter lead the per-list breakdown behind a Pie or archiving the campaign-window snapshot of signups by form.