Yes. yith_wcmap_endpoint is a serialized PHP array stored in wp_options. SleekView Charts unpacks the serialization on read, expands each endpoint entry into a separate row, and exposes the keys (slug, role, content_type, position) as chartable columns so the dashboard renders without writing a custom parser.

Yes. The plugin exposes a hook fired on each endpoint render. Combined with a SleekView data source on WordPress request logs or a lightweight visit-tracking integration, a Bar chart ranks endpoints by render count and reveals which custom tabs customers actually use.

Yes. WooCommerce core endpoints (dashboard, orders, downloads, addresses, account-details, logout) live in their own woocommerce_myaccount_*_endpoint options. SleekView Charts reads both YITH custom endpoints and the WooCommerce core endpoints so the full My Account tab inventory shows up on one card.

Yes. Each chart exports aggregated rows to CSV. The audit dashboard becomes shareable documentation for compliance reviews, client handoffs, or pre-migration inventories where leadership needs evidence of the My Account configuration without database access.

Yes. Each subsite stores its own yith_wcmap_endpoint option. SleekView Charts can union across subsite tables for a multi-site My Account inventory dashboard, useful for agencies managing a network of WooCommerce storefronts with consistent custom tabs.

Yes. YITH Role Based Prices and other YITH role plugins register roles that the My Account plugin uses for gating. The Donut groups by the role key on each endpoint, so combined-plugin role mixes still chart correctly without any extra configuration.

If the store logs YITH option changes (via WP Activity Log or similar), SleekView Charts can read the audit log table alongside the YITH option. An Area chart of position changes per day reveals who's been reorganizing My Account tabs and when, which often answers handoff questions.

Yes. YITH stores endpoint labels per language but keeps the slug, role, and content_type stable across translations. Cards group by language-neutral keys so the dashboard counts unique endpoints once, regardless of how many translation strings exist.