Fresh Relevance is a personalisation platform that drops a JavaScript tag into your site and uses Slots, Recommends, and Segments to decide what each visitor sees. The WordPress side of that integration writes to option rows like freshrelevance_settings and freshrelevance_slots, plus per-post overrides in postmeta keys for slot mappings and disable flags. The personalisation itself runs in the Fresh Relevance cloud.

SleekView Charts reads the WordPress side and lets you build chart cards on top: a Number for posts with personalisation disabled, a Donut for slot type spread, a Bar for slot coverage by post type, an Area for the rate of new slot overrides added per month. Each card is a saved query against the live Fresh Relevance option rows and postmeta, so the dashboard reflects today's personalisation picture.

The personalisation engine keeps doing what it does. The Fresh Relevance tag still fires, Slots still render, and SleekView simply gives editorial, CRO, and ops teams a way to see how the integration is deployed across the site without scrolling through plugin settings.

Fresh Relevance is great at orchestrating personalisation, less great at telling editors where the personalisation is actually deployed inside their own site. Slots live in the Fresh Relevance UI, postmeta overrides live in WordPress, and the gap between the two slowly widens as teams experiment. SleekView Charts closes that gap by treating the Fresh Relevance plugin option rows and override postmeta as a real dataset.

CRO leads see slot coverage and override drift in one view, editors get a quick read of which post types carry personalisation, and agencies hand clients a saved coverage dashboard scoped to a client role. The personalisation engine keeps running in the Fresh Relevance cloud, and the WordPress side finally has a coverage map of its own.