Yes. The aggregation runs against the same table SleekView's view tool reads, with no plugin abstraction in between. Queries hit indexed columns, joins resolve popup_id to wp_posts for readable labels, and consent_args expands into a filter chip on the dashboard.

Yes. A consent filter chip with granted, pending, and denied scopes every card to that state. Compliance dashboards typically show granted-only; acquisition dashboards typically show the full mix to read collection effectiveness.

Pro features add fields and integrations but the subscriber schema stays the same. Any additional columns from Pro extensions become available as group-by options. The free plugin's wp_pum_subscribers carries everything the dashboard needs.

Yes if the install captures them in known fields or meta. SleekView Charts exposes any column from the joined data as a group-by option, so plan tier, country, or referral code can each become a chart dimension.

Yes by default. If you anonymize a subscriber via SleekView's inline edits (blanking email and consent_args), the row still counts in totals because the database row remains. To exclude anonymized rows, filter to non-empty email before charting.

Deleted popups appear in the Bar card with a deleted indicator and their ID. The captures they collected still count in totals because the subscriber rows persist. Filter to non-deleted popups when the ranking should only reflect live ones.

The Area card groups by the created column with Count aggregation, producing one point per day. The trend shape surfaces campaign spikes, content-driven baselines, and quiet periods on the same canvas.

No. SleekView Charts reads existing rows in wp_pum_subscribers; it does not inject scripts, fire pixels, or send data anywhere. Popup Maker continues to handle capture, and the dashboard is purely a read layer over the resulting data.