Both work. SleekView Charts reads the yasr_log, yasr_log_multi_set, yasr_multi_set, and yasr_multi_values tables that the free YASR plugin creates. YASR Pro adds extra features, but the underlying log tables stay the same and the cards keep working when you upgrade.

Yes. A Pie or Bar card groups yasr_log rows by the vote column and counts them. The result is a five-slice donut or a five-bar chart that shows whether the site-wide rating is a clean consensus or a polarized split.

Group yasr_log by post_id and aggregate with Count for most-rated or Average over vote for highest-rated. The post titles resolve through a join to wp_posts, so the bar legend reads as real titles.

Yes. yasr_log_multi_set stores one row per criterion with field_id referencing yasr_multi_values. A Bar card grouped by field_id and averaging the score returns one bar per criterion, with names resolved from yasr_multi_values.name.

Overall Rating from the reviewer is stored as a postmeta yasr_overall_rating on each post. SleekView reads postmeta as a chart source too, so cards can aggregate across the editor scores and compare them to the visitor votes from yasr_log.

Cards run against the live YASR tables every time the dashboard loads or a card refreshes. There is no nightly export step, so a vote saved one minute ago appears on the next card refresh without any extra work.

Cards use indexed queries against the same columns YASR itself reads, so a busy site loads cards in roughly the same time the standard YASR admin takes. For very large logs, scope cards to a date range like last 30 or 90 days to keep aggregations responsive.

Yes. Save a dashboard, gate it by capability or role, and each persona lands on the right view. Editors open the site-wide ratings view, authors open the per-post leaderboard scoped to their own posts, all from one SleekView install.