Articulate Rise 360 reports completion, progress and assessment results, but has no visibility into attention within a piece of content. Emotuit adds content-level engagement data — dwell, focus, tab-switching and drop-off position — through a sub-50KB script, alongside existing reporting rather than replacing it.
What Articulate Rise 360 already gives you
Rise 360 reports what it sends to the LMS — completion status and quiz results via SCORM or xAPI.
What it does not
Rise produces long scrolling lessons, which is exactly the format where completion data is least informative. A learner can reach the bottom of a scrolling lesson in seconds. Scroll depth without dwell tells you almost nothing.
This is not a criticism of Rise 360 specifically — it is true of essentially every authoring tool on the market. Completion and navigation data is what these systems were built to record, and they record it well. Attention is a different measurement problem, solved in the content layer rather than the platform layer.
How Emotuit fits
Export as SCORM or xAPI and add the SDK to the published package, or use an embed block. Content positions map to Rise block IDs, giving per-block engagement within the lesson.
The SDK is under 50KB, adds one script tag, and requires no migration or infrastructure change. It runs alongside Rise 360's own reporting rather than replacing it.
Details
Why Rise specifically benefits
The scrolling format makes it trivially easy to reach the end without reading. Per-block dwell data is the only way to distinguish a completed lesson from a scrolled-past one.
Works with
All Rise block types including interactive blocks, embedded video and knowledge checks.
What you get
| Metric | Detail |
|---|---|
| Content-level engagement | A score for every section, not one per course |
| Drop-off position | Where sessions actually end |
| Focus-adjusted dwell | Real attention, discounting background tabs |
| Tab-switch rate | The strongest single predictor of disengagement |
| Replay behaviour | Where learners went back — a confusion signal |
| Cohort comparison | A/B test content versions on real attention |
Deployment options
Emotuit runs in two configurations, and for authoring tool deployments in the EU the choice matters.
Signals uses behavioural telemetry only — no camera, no biometric data, no emotion inference. It sits outside the EU AI Act Article 5(1)(f) prohibition on inferring emotions in workplace and education contexts, which makes it the default recommendation for corporate L&D and education.
Learn adds a client-side facial expression layer. It should not be deployed to EU employees or students, and is intended for market research, UX and media testing contexts.
Frequently asked questions
Does this replace Rise 360's built-in reporting?
Does it need a webcam?
How long does integration take?
Will it slow the platform down?
See it on your own Rise 360 content
We'll instrument one module and show you the engagement data before you commit to anything.