H5P captures interaction data on every attempt: scores, completion times, branching-scenario choices, locally stored xAPI statements when enabled. The default H5P admin shows that data per content item with limited filtering, and cross-content reports usually require an external learning record store or hand-rolled SQL.

SleekView Charts reads the same h5p_results and h5p_contents_user_data tables the SleekView table reads, then renders the aggregates as cards. Score distribution as a bar histogram. Attempts per day as an area chart. Content-type mix as a donut. Active learners as a single-number KPI. Each card respects the dashboard filter set, so instructors can scope every chart to one cohort or to the last term without rebuilding queries.

For sites running H5P inside an LMS (LearnDash, LifterLMS, Tutor LMS), the H5P chart dashboard sits alongside the LMS chart dashboards. End-to-end progress combines both data sources. External LRS users keep their LRS; this dashboard is for sites that prefer the data to live in WordPress.

H5P is the interactive-content layer of choice for a lot of WordPress LMS deployments, with quizzes, branching scenarios, interactive video, and drag-and-drop all in one toolset. The interaction data it generates is rich: per-attempt scores, per-step branching choices, completion times, locally stored xAPI statements when enabled. The default H5P admin presents a slice of that data per content item; the rest is meant for an external LRS that most installations do not run.

SleekView Charts treats H5P's storage tables as the analytical source they are. Score distribution histograms surface calibration issues across the catalogue. Engagement velocity curves expose campaign effects.

Content-type donuts show what learners actually use. Active-learner KPIs condense program health into one figure. The interaction data was always there; the chart dashboard just makes it operationally legible without standing up an LRS.