An LRS is a data store that receives, holds and serves xAPI statements. It is the backend component of the xAPI specification and can operate standalone or inside an LMS.
What it is
An LRS accepts statements over a REST API, validates them against the xAPI spec, stores them, and exposes a query interface. Common implementations include Learning Locker, Watershed, Veracity and SCORM Cloud.
Because statements can come from any source, an LRS often ends up holding data from an LMS, a simulator, a mobile app and a physical training environment simultaneously.
Why it matters
An LRS is where engagement data can join the rest of the learning record. Sending engagement statements to an existing LRS rather than a separate analytics tool means the data is queryable alongside completions and assessments.
A common confusion
An LRS is a store, not an analytics tool. Most provide basic reporting; deriving insight generally requires something on top.
Related
See also xapi (experience api), learning analytics and scorm. See the full glossary for the rest, or the xAPI integration page for the wider context.
See where your content loses people
Book a walkthrough and we will show you the engagement data on your own content.