All the wp_acym_* tables: user, list, user_has_list, mail, queue, history, field, and user_has_field. Build views that join across them as needed. The schema is rich enough to support segmentation, queue health and per-recipient audits, all from one query layer.

Where AcyMailing exposes a class method (subscribe, unsubscribe, confirm, save_field), SleekView calls it. Plain attribute edits write directly to the table. That separation keeps custom integrations sitting on top of AcyMailing's hook layer working when audit edits fire from inside SleekView.

Yes. wp_acym_history stores per-recipient send results. Build a side panel or tab that filters history rows by user_id; the result is a per-subscriber timeline with status, open and click events. For a GDPR export, that is the data-subject record in one screen.

AcyMailing's automation rules are stored as JSON in wp_acym_automation. SleekView surfaces the rule rows so an audit can see which automations are active and when each last ran. Deep editing of the JSON rule tree still happens in the AcyMailing UI, since the structured editor there is built for the rule shape.

External-sending settings live in wp_options. SleekView reads them as a separate config view, which is useful when migrating between sending services or when a team needs to confirm the active provider before a launch. The send results themselves still land in wp_acym_history, regardless of which provider sent them.

Yes. The flow stores its state in wp_acym_* tables alongside cart references. SleekView reads them, but the cart itself is on the WooCommerce side. A complete audit usually combines the abandoned-cart view with WooCommerce's own cart tables, joined on customer email or user ID.

Yes. Filter subscribers by any criteria, then bulk-add or bulk-remove them from a list. SleekView writes to wp_acym_user_has_list through AcyMailing's subscribe and unsubscribe methods so any related hooks fire. Bulk operations are the main reason teams move from the default admin to SleekView.

Confirmation tokens live in wp_acym_user with the user's pending state. Filter for confirmed=0 to surface every pending subscriber, sort by joined date, and bulk-resend confirmation emails through AcyMailing's resend method. The token itself stays masked unless an admin opts into showing it, which keeps screenshots safe.