Google Analytics Pro fires enhanced ecommerce events to GA4 and stamps UTM and source meta onto the WooCommerce order at capture. The events live in GA4. The orders themselves live in wc_orders with the channel meta attached. The default surface is the GA4 console for analytics and the WooCommerce order list for orders, which leaves the in-admin question ("which paid orders came through email this week?") on neither screen.

SleekView reads wc_orders directly and joins the source meta Google Analytics Pro writes. Filter to orders from a UTM source in the last 30 days to brief a channel review. Sort by total to find the largest paid orders. Group rows by status to see where the channel mix sits in processing versus completed. The same dataset the chart view aggregates becomes a row-level surface for finance, marketing and support.

The plugin keeps owning the GA4 event stream and the attribution capture. The table view owns the audit surface, so the channel-tagged orders Google Analytics Pro already produces stop hiding behind a GA4 tab and become something WP admin can actually query.

Google Analytics Pro is excellent at funnel reporting, but the attribution it captures lives twice: once as an event in GA4 and once as meta on the WooCommerce order itself. The local copy is the ground truth that survives GA4 sampling and outages, and it is the only one finance can reconcile against the bank. SleekView reads wc_orders with the source meta joined and renders the rows as a queryable audit table.

Filters stack so the paid-traffic audit, the email-attributed cohort and the refunded-by-channel triage become saved views rather than GA4 plus spreadsheet exercises. The plugin keeps owning the event stream and the GA4 reports, while WP admin gets the per-row surface the order data always deserved.