No. SleekView reads from wp_postmeta on the nf_sub post, which the Ninja Forms Mailchimp add-on writes after it completes (or fails) a sync attempt. SleekView is the WordPress-side visibility and annotation layer, not a Mailchimp client. Retrying a failed sync still uses the add-on's own mechanism.

Whatever the add-on writes. Typically _mailchimp_list_id, _mailchimp_status, _mailchimp_error, and sometimes interest-group IDs and merge field maps. The column picker lists every meta key actually present, so updates to the add-on's storage surface without configuration changes.

SleekView doesn't push to Mailchimp directly. The supported retry path is the add-on's own mechanism: open the submission and trigger the action again, or use a hook to re-fire the sync. SleekView's role is to identify which rows need that treatment, with the error message visible so you don't spend time on signups that are unrecoverable (e.g. genuinely invalid email).

If the add-on stores the resolved interest group IDs and merge field values in postmeta for each submission, yes. The pattern varies by add-on version. The column picker shows what's actually there. For configuration data that lives on the form (not the submission), SleekView's view layer doesn't expose it; that's a form-builder concern.

Yes, via the _mailchimp_list_id column on the submission. For a per-form audit (which form is configured to which list), the list ID is typically the same value across all submissions from a given form, so grouping by _form_id and showing the distinct _mailchimp_list_id answers that question directly.

Tags written to subscribers in Mailchimp aren't stored back in WordPress by the add-on, so SleekView can't display them. If you assign tags conditionally during form submission and the add-on writes the tag list to postmeta, that's surfaceable. Otherwise, tag auditing happens on the Mailchimp side, and SleekView is the upstream visibility layer for signup attempts only.

Double-opt-in means the add-on's first sync attempt sets the subscriber to pending until they click the confirmation link. SleekView shows pending as a column value, distinguishing it from real errors and from confirmed subscribers. The status only updates back to WP if the add-on subscribes to the relevant Mailchimp webhook; otherwise SleekView's pending is a point-in-time reflection.

WordPress's personal-data export tool exports rows from postmeta linked to a user's data subject identifier, which includes the Mailchimp keys. SleekView's filter UI helps you locate the right nf_sub rows by email; the WordPress core tools handle the export and erasure. SleekView doesn't replicate that pipeline, it complements it with discovery.