WooCommerce Referrals persists referrers in wp_wc_referrals_referrers, codes in wp_wc_referrals_codes, and individual conversion rows in wp_wc_referrals_conversions with the originating order_id. The default admin separates referrer profiles from conversion logs and gives no straightforward way to ask "which referrer drove the most revenue last 30 days".

SleekView reads the three tables and joins them on referrer_id with conversion aggregates rolled up per referrer: total conversions, total referred revenue, and the date of the most recent referred order. Filter the grid by code_status to see active versus disabled codes, sort by referred revenue to find the top affiliates, or filter conversions per the last 30 days for a recent-performance snapshot.

Bulk operations let you disable a code that is being abused, approve pending conversions in a batch when a fraud review concludes, or adjust commission rates per referrer. Each edit routes through the plugin's wc_referrals_update_* filters where present, so payout calculations and notification emails still fire correctly downstream.

A referral program is only worth running if the small group of top referrers stays engaged. The 80-20 rule applies aggressively: the top ten percent of referrers drive almost all the revenue, and once they go quiet the program flatlines. WooCommerce Referrals tracks the necessary data in clean relational tables, with referrer profiles, codes, and conversions joined by foreign keys.

But the default admin separates the three concepts into different screens with no rollup, which forces the affiliate manager to alternate between tabs or wait on an analyst for a weekly spreadsheet. SleekView joins the source tables and exposes the rollups that the manager actually thinks in, with saved views for the top performers, the paused codes, and the pending conversions awaiting fraud review. The result is a referral surface that scales with the program's success: as the referrer count grows, the operator's daily workflow gets shorter, not longer.