No. The Metrilo console remains the right place for retention cohorts, behavioral segments, and the email automation tied to Metrilo's tracking. SleekView Charts adds an in-WordPress dashboard that lives alongside the WooCommerce screens, so the team has one less tab switch when the question only needs the source-of-truth WooCommerce data.

Directly from the WooCommerce tables in your WordPress database. Customers come from wp_users and wp_usermeta, orders from wp_wc_orders (HPOS) or shop_order posts, and line items from woocommerce_order_items joined to order_itemmeta. SleekView reads the same WooCommerce data Metrilo's plugin forwards upstream.

Yes. Any wp_usermeta key, whether added by Metrilo, WooCommerce, or a custom plugin, can be pivoted into a named column at the SleekView dataset layer and then used as the groupBy dimension on any chart card. Country, city, last order id, and any client-defined attribute all become valid chart axes without writing SQL by hand.

Both. SleekView's dataset layer reads from wp_wc_orders when HPOS is enabled and from wp_posts plus wp_postmeta with post_type equal to shop_order when it is not. The same chart configuration covers either storage model, so a store mid-migration does not need to rebuild the dashboard after switching.

Yes if the source is captured in wp_usermeta or wp_postmeta. Metrilo tracks source for its own dashboards, and most stores also store a copy locally via UTM-capture plugins or custom signup forms. Wherever the value lives in WordPress, SleekView can use it as a groupBy dimension for a Bar card or as a filter on a Number card.

Live. SleekView Charts queries the WooCommerce tables on render, so every new order and every new customer registration shows up on the next dashboard load. Cache windows are configurable per dataset for very large stores, but the default is fresh data on every visit to the board, matching how WooCommerce admins expect their reports to behave.

By default, SleekView reads every row in wp_wc_orders, and each chart card declares its own status filter. Most teams exclude refunded and failed from revenue cards while keeping them on the status-mix Donut, which is exactly the behavior the chart configuration supports out of the box without code.

Each chart card can be exported as CSV via the SleekView dataset layer, so the underlying numbers travel cleanly into a deck or a board pack. The dashboard itself lives in the WordPress admin, gated by capability, so the live view stays internal to the team that already has WooCommerce access.