LTI 1.3 / LTI Advantage Engagement Analytics

In short

LTI 1.3 / LTI Advantage 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 LTI 1.3 / LTI Advantage already gives you

LTI 1.3 handles secure launch, roles, context and — through Assignment and Grade Services — grade passback.

What it does not

LTI defines how a tool is launched and identified, not what it measures. It gives you a trustworthy learner and course context, which is exactly the foundation engagement analytics needs, and no engagement data of its own.

This is not a criticism of LTI specifically — it is true of essentially every standard 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

Emotuit registers as an LTI 1.3 tool. Launch provides the course and user context; engagement data is collected in the content and reported against LTI resource link IDs.

The SDK is under 50KB, adds one script tag, and requires no migration or infrastructure change. It runs alongside LTI's own reporting rather than replacing it.

Details

Why LTI is the cleanest route

It avoids platform-specific script injection entirely, works identically across Canvas, Moodle, Blackboard and Brightspace, and survives platform upgrades that break theme-level customisation.

Works with

Any LTI 1.3 certified platform. LTI Advantage services supported where the platform offers them.

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 standard 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 LTI's built-in reporting?

No. It runs alongside it. LTI continues to handle completion, grades and compliance evidence exactly as before — Emotuit adds the content-level attention layer underneath, answering which sections held people rather than who finished.

Does it need a webcam?

Not in Signals configuration, which is what we recommend for standard deployments. It uses browser events only — visibility state, window focus, dwell, scroll and interaction timing. There is no camera permission prompt because there is nothing to permit.

How long does integration take?

Typically a day or two. Most of that is mapping your content structure so engagement data lands against the right sections and modules rather than an arbitrary timeline. The script itself is one line.

Will it slow the platform down?

No measurable effect. The SDK is under 50KB, listens to native browser events rather than polling, and batches its reporting. It does not touch the rendering path.

See it on your own LTI content

We'll instrument one module and show you the engagement data before you commit to anything.

Request a demo

Engagement analytics for LTI 1.3 / LTI Advantage