LRS - Article

Business Context

Eurekos includes comprehensive built-in tracking and reporting capabilities that meet the needs of most organizations. In many cases, there is no requirement to integrate with an external Learning Record Store (LRS). However, if you want to import xAPI content, such as courses created in a 3rd party authoring tool, an LRS is required to operate appropriately with data.

Organizations may require:

• Cross-platform learning tracking
• Integration with external learning ecosystems
• Custom learning analytics beyond standard LMS reporting
• Support for xAPI-based content and learning experiences

This is where an LRS becomes relevant.

An LRS allows organizations to collect detailed, standardized learning activity data across multiple systems—not just Eurekos—making it possible to track learning beyond the LMS itself.

Typical use cases include:

• Advanced analytics and BI integration
• Tracking learning across multiple platforms
• Using external authoring tools that rely on xAPI
• Capturing granular learning interactions beyond what is supported by Eurekos charts and reports

For learning tools already integrated into Eurekos—such as H5P, which can be created and managed natively—the platform supports access to key interaction data directly within its built-in analytics. This means that, for most use cases, no LRS connection is required to gain meaningful insights.

An LRS integration becomes relevant only in more advanced scenarios, where an organization requires access to a broader or more granular set of data points than what is available within Eurekos. This typically applies when there is a clear business need for full data extraction, cross-system tracking, or custom analytics beyond standard reporting capabilities.

xAPI (Experience API) and Learning Record Store (LRS)

xAPI (Experience API) is a modern standard for tracking learning experiences across systems. Instead of being limited to traditional events such as course completion, xAPI captures learning as structured statements—often described as “Actor – Verb – Object” (for example, “User completed Course A”). This approach enables much more flexible tracking of learning activities, including interactions with content, video engagement, simulations, and learning that happens outside the LMS.

A Learning Record Store (LRS) is the system designed to receive and manage these xAPI statements. It acts as a centralized repository where learning data can be stored, queried, and analyzed independently of the platform where the learning took place. This makes it possible to track learning across multiple systems and environments, supporting more advanced analytics and integration scenarios.

While Eurekos supports xAPI through LRS integration, it is important to note that the standard itself—and how it is implemented—can vary depending on your chosen tools and setup. For this reason, we recommend consulting official xAPI and LRS documentation when designing your tracking strategy:

• https://xapi.com (xAPI overview and specification guidance)
• https://adlnet.gov/projects/xapi/ (official ADL xAPI documentation)

These resources provide deeper guidance on how to structure statements, design learning experiences, and ensure compatibility across systems.

When an LRS Is Required

An LRS integration is typically required when:

• Using xAPI-based content from external tools
• Tracking learning outside Eurekos
• Exporting raw learning data to external systems
• Performing advanced or custom analytics

It is not required for standard Eurekos usage.

Feature Overview

The LRS integration enables Eurekos to communicate with an external LRS using the xAPI standard.

How the Integration Works

The integration operates as a data flow from Eurekos to the LRS.

1. Platform-Level Configuration

• LRS endpoint and credentials are configured
• Integration is enabled

2. Learning Activity Occurs in Eurekos → users interact with content that generates xAPI statements, such as:

• Course pages
• Videos
• Interactive content (e.g. H5P)

3. Data Is Sent to the LRS

• Eurekos transmits statements to the configured LRS
• Data is sent at regular intervals (asynchronous processing) 
• Data Is Stored and Processed in the LRS → The LRS:
  • Stores statements
  • Makes data available for reporting
  • Enables external analytics

What Data Is Sent

The following activities generate xAPI statements in Eurekos:

These statements are sent to the configured LRS, where they are stored and made available for analysis. Certain learning tools, such as H5P, generate rich and detailed xAPI statements based on the specific interactions within each content type. The structure and scope of these statements are defined by the tool itself and can be explored in the official xAPI documentation provided by H5P.

For third-party or externally authored content, xAPI statements may be custom-designed within the respective authoring tools. These statements are transmitted through Eurekos but are defined and controlled outside of the platform, meaning their structure and level of detail depend on the originating tool rather than Eurekos.

Important Behavior

There are important technical considerations when working with xAPI:

• Progress is not continuously updated in real time
• A trigger (e.g. page reload or navigation) is required for updates to be sent
• Updates are processed in intervals and temporary delays may occur

External Content Behavior → If xAPI content links to another system:

• Data may be stored in that external system
• Eurekos may not receive or display that data

This depends on how the xAPI package is configured.

What the Integration Does NOT Do

It is important to clearly define scope:

When to Use an LRS (Guidance)

Use an LRS when:

• You need cross-system tracking
• You use external xAPI content tools
• You require advanced analytics and e.g., business intelligence requirements (align with your LRS of choice)

Configuration

To connect Eurekos with an external LRS, you must configure connection details provided by your LRS provider.

Step 1: Navigate to LRS Settings

Go to: Settings → Third Party Integrations → LRS.

Step 2: Enable LRS Integration

Enable LRS integration. This activates the configuration fields.

Step 3: Enter LRS Connection Details

You must provide the following:

• Endpoint Format → The endpoint is typically a REST API endpoint following the xAPI specification.
  • Example format: https://lrs.example.com/xAPI/statements
• Authentication Model → The integration uses basic authentication:
  • User = API key or client ID
  • Password = secret or token
  • These credentials are provided by your LRS system. 

Step 4: Save Configuration

Click Save → Once saved:

• Eurekos begins sending xAPI statements
• Data is transmitted at regular intervals
• Integration becomes active immediately

Step 5: Validate Integration

After configuration:

• Perform test activity (e.g. view course, play video)
• Verify statements are received in the LRS
• Confirm correct structure and timestamps

The validation is best explored in details with reference to the connected service.

Key Considerations

• The LRS must support xAPI specification
• Endpoint must accept statements from Eurekos
• Credentials must be valid and active
• Domain and endpoint formatting must be correct