Engagement Analytics

Engagement analytics answers the question that grades alone cannot: is the student actually turning up? For every student and subject pair, OpenEduCat collects the last Moodle login, how far through the course the student has progressed, and whether the course has been completed.

The data supports early intervention — spotting a student who has not logged in for weeks, long before a failed exam makes it obvious.

Enabling It

1. Open the Moodle instance and go to the Sync Configuration tab.

2. Enable Pull Engagement Analytics in the pull column.

3. Go to the Settings tab and set the Engagement Window (days) — the number of days within which a login still counts as active. Default 30.

4. Save.

The daily Moodle: Engagement Analytics Pull job now refreshes the data. To fetch it immediately, click Pull Engagement Now in the instance header — the button appears once the toggle is enabled.

The Dashboard

Go to Moodle Integration ‣ Reporting ‣ Engagement Analytics. The view opens filtered on inactive students, because that is the list worth acting on.

Field	Description
Student, Subject	The pair the snapshot describes.
Program / Course, Batch	Context for grouping and filtering.
Last Login	The student’s most recent login to Moodle.
Days Since Login	Calendar days since that login. Shown as 999 when the student has never logged in.
Active in Window	Whether the last login falls inside the engagement window.
Completion %	Share of the course completion criteria met.
Course Completed	Whether Moodle considers all completion criteria met.
Activities Completed / Total Activities	Progress through the course activities. Hidden by default.
Last Synced	When this row was last refreshed.

Rows are colour-coded: green for active students, amber for inactive ones, red once a student has been away for 90 days or more.

Filters

Filter	Shows
Active in Window / Inactive	Students inside or outside the engagement window.
Never Logged In	Students with a Moodle account who have never signed in — often an onboarding or communication problem rather than an academic one.
Dormant (90+ days)	Students absent for a full term.
Course Completed / Not Yet Complete	Progress against the Moodle completion criteria.

Results can be grouped by program, subject, batch, active status or instance.

Other Views

1. Kanban :- Cards grouped into active and inactive columns, showing completion and the last login for each student.

2. Pivot :- Completion percentage and days since login, broken down by program and subject against the active status — useful for comparing cohorts.

3. Graph :- Average completion per program, for a quick overview at management level.

Reading the Data

• A batch with high completion and low logins usually means content was finished early in the term and the group has since drifted away.

• Never logged in concentrated in one program points at an enrollment or credentials problem rather than disengagement.

• Rows only exist for students whose Moodle account and course enrollment are mapped, so a student missing from the dashboard is a mapping issue, not an engagement one.