In a custom table named wp_pum_subscribers. Columns include ID, email, name, fname, lname, popup_id, consent, consent_args, user_id, and created. SleekView reads it directly without going through any plugin abstractions, which keeps queries fast and lets you compose cohorts that the default admin can't render.

Yes. The view joins to wp_posts on popup_id so the column shows a readable popup name instead of an integer. The join is a config option in the agent UI, not custom SQL. If a popup has been deleted, SleekView shows the popup_id and a deleted indicator so you can still recognize the row in compliance exports.

Popup Maker uses several supporting tables for analytics and conditions. Each can become its own SleekView view if it adds value, for example an analytics-events table for funnel debugging or a conditions table for auditing rule overlap. The agent UI lists every wp_pum_* table on your install so you can pick the ones worth surfacing.

Yes. SleekView writes through the plugin's data-access layer, PUM_DB_Subscribers, when available, so any registered actions on subscriber updates fire normally. ESP integrations and consent-tracking webhooks downstream of those actions behave the same as if you'd edited from Popup Maker's own admin.

Source-page tracking depends on whether your install captures it. Some setups store referrer in subscriber meta, others in consent_args, and some don't capture it at all. If the data is present in any field, SleekView pivots it into a column. If the install doesn't record source pages, no view can invent that data.

No. SleekView is a queryable view of what's already in your WordPress database. ESP integrations still happen through Popup Maker's standard sync. SleekView's role is the audit, cohort, and export layer over the local store, not the live capture or send path.

Yes. Inline edit lets you blank out email, name, and consent_args fields directly. Combine with a saved filter for 'right-to-be-forgotten requests this month' and the workflow collapses into a single screen. The write path uses Popup Maker's data layer where exposed, otherwise direct table writes with an audit log entry.

Group the subscriber view by email. Rows that match across multiple popups surface together with a popup-list column showing every popup that captured them. Useful before pushing to an ESP that doesn't tolerate duplicates and useful for understanding which popups overlap in audience.