Directly from wp_posts, the _eael_widget_elements postmeta the plugin maintains to scope its asset bundles, and the eael_global_settings option that holds the enabled/disabled state for each widget. No exports, no extra tracking.

Yes. The per-post _eael_widget_elements meta lists the widget slugs in use on that page. SleekView normalises that list so a Bar card grouped by widget slug renders the usage ranking directly, no SQL gymnastics required.

Join the widget toggle state from eael_global_settings with the usage count from _eael_widget_elements. SleekView exposes both as columns, so a Bar card sorted ascending immediately surfaces enabled widgets with zero page usage, the cleanest disable candidates.

Yes. Essential Addons writes its meta on the same posts Pro and core Elementor live on, so SleekView can chart Essential Addons widgets, Pro widgets and core widgets from the same wp_posts source. Pro template types and Essential Addons widget slugs can both show up as group-by columns.

Yes. Group an Area or Line card by post_modified on the set of posts whose _eael_widget_elements is non-empty. The curve shows whether usage of the addons is growing, plateauing or shrinking week to week.

Queries hit indexed columns on wp_posts and the indexed meta_key column for postmeta. The widget-slug normalisation pass can be backed by a lightweight cache so dashboards render fast on sites with thousands of pages.

Charts are read-only summaries. To act on an insight (disable a widget, refactor a page) switch to the audit table filtered to the same slice. Edits route through the standard WordPress update path, so Essential Addons' caches invalidate exactly as they would after a save in the editor.

No. The settings screen still owns toggling individual widgets on or off. SleekView Charts adds a reporting surface on top of the meta Essential Addons already writes, so the plugin keeps owning configuration and the chart view owns the audit.