The default WooCommerce Recently Viewed widget shows a small per-visitor strip on the storefront. It does its job for shoppers but gives the merchant almost no visibility: the view history sits in cookies, sessions, or wp_usermeta under a per-user key, and there is no admin screen that lists who viewed what across the store. SleekView reads those records directly and turns them into a table you can sort, filter, and export.

For logged-in customers the data is stored against the user (commonly under a key like _recently_viewed_products in wp_usermeta), so a view scoped to wp_users joined with the product post type by ID gives you a row per customer with the products they last looked at. For guests, recently-viewed entries often live in wp_woocommerce_sessions and can be aggregated by session ID for short-window analysis.

SleekView does not invent new tracking, it just exposes what the plugin already stores. Edits to the underlying records go through WordPress core APIs (update_user_meta, session updates) so any hooks attached to those keys still fire. Marketing can build re-engagement segments and support can answer "what was this customer looking at before they bounced" without writing custom queries.

Recently-viewed widgets are a default ecommerce nicety, almost every WooCommerce site has one, but the data behind them is one of the most under-used assets in WP admin. The information sits in wp_usermeta and wp_woocommerce_sessions already, written by the storefront every time someone browses a product. The plugin's job is to render a strip on the product page; it has no obligation to give the merchant a list view, so the data stays effectively invisible.

That is fine for a hobby shop with twenty products and ten customers. It is not fine for a brand running paid traffic that wants to know which customers viewed the new collection but bounced, or a support team trying to recover abandoned interest mid-chat, or a merchandiser trying to spot a popular-but-low-converting product before the buying season ends. SleekView turns the existing data into a workspace: per-customer view history for support, per-product viewer segments for marketing, per-session guest patterns for merchandising.

Same database, same storage, dramatically more leverage from data the store was already collecting.