Thrive Leads Pro maintains its own custom tables. tve_leads_form_types stores form variations, tve_leads_event_log stores impression, conversion, and click events, and tve_leads_contacts holds the captured subscriber records. Lead groups and the form variations within them are normal CPTs with extensive wp_postmeta backing them. The schema is well-indexed for the analytics dashboards Thrive Leads ships.

The default Thrive Leads dashboard renders aggregate conversion rates per lead group and per form, with drill-down screens for A/B test variants. Cross-cutting questions like "which variant converted best on long-form blog posts last quarter" or "which contacts came from the exit-intent variant on the pricing page" require chaining the dashboard with manual SQL. Inline editing of conversion goals, bulk-pausing variants, and auditing the event log row by row sit outside the default screens.

SleekView reads the tve_leads_* tables directly, joins the event log with form variants and lead groups, and pivots conversion-event metadata into named columns. Variant audits become saved views; per-page attribution becomes a join with the referrer column on tve_leads_event_log; bulk-pause becomes inline.

Conversion-rate optimisation on Thrive Leads Pro lives on the variant level: which form converts best on which page, which one to pause, which one to roll out, which to keep testing. Thrive Leads' default dashboard handles the aggregate view well, but optimisation teams need a row-level workspace where every variant from every lead group sits in one filterable table with impressions, conversions, and conversion rate inline. The data is all there in the tve_leads_* custom tables, well-indexed for the dashboard's own queries.

SleekView's joined view turns it into a workspace. Optimisation leads can sort by rate to see the spread, filter by lead group to audit a single campaign, and pause underperformers in bulk through the plugin's variant API. Growth marketers can filter tve_leads_event_log by referrer to see which page each variant performs best on.

Email ops can pull per-source contact lists from tve_leads_contacts to feed downstream segmentation. The optimisation cycle gets shorter because every variant decision lives in one place rather than across half a dozen drill-down screens.