Yes. YITH Popup increments _ywpop_impressions for every render regardless of user state, and SleekView Charts reads the meta directly. Filters can scope cards to authenticated, guest, or all visitors when the question requires that distinction for a specific campaign analysis.

Yes. Popup display rules in postmeta include the page or template scope. SleekView Charts groups on rule scope so marketing sees CTR on product pages versus archives versus the cart page as separate Bar segments on the same chart.

Yes. Popups configured with form submission or coupon redemption goals store the goal type and event count in additional postmeta keys. The Bar of top performers groups on goal type so newsletter-signup popups compare against coupon-claim popups fairly.

Yes. The tracking events are timestamped in the popup history table so cards inherit any dashboard-level date range. Marketing scopes the ranking to last week, last month, or the duration of a specific campaign without reconfiguring each card.

Yes. Multistep popups track step-level engagement in postmeta alongside the overall impression and click counters. The dashboard can include per-step funnel cards or stay at the popup level depending on whether the question is about overall reach or step drop-off.

Yes. Device metadata stores alongside the tracking events when device targeting is enabled. The Bar of top popups by CTR groups on device segments so a mobile-only configuration compares fairly against the desktop variant of the same campaign.

By default, tracking events from known bot user agents filter out at the plugin level. SleekView Charts inherits the same filtering so the impression count matches what marketing would expect to see in any reputable analytics platform without manual bot exclusion lists.

Yes. Every chart card pairs with a SleekView table view containing the underlying popup records. Sort by CTR ascending, filter to popups below a threshold, and export to CSV for the marketing review where retirement decisions happen each cycle.