xAPI & Storyline

Creating xAPI Statements in Storyline 360 [Part 2]

In my last video, I talked about the basics of Articulate Storyline 360's new xAPI trigger feature. This new update allows you to trigger custom xAPI statements within Storyline's simple user interface without adding any custom code.

You then needed to upload the course into an xAPI (or cmi5) capable LMS to know who was taking the course. So that is great if your course is inside your learning system, but what about courses outside of the learning management system? How can you track those courses? In this new update from Articulate, you can also export content to an external learning record store (LRS). This means you have two options; if your LMS supports xAPI, it will track the custom xAPI courses right within your LMS without you having to publish to SCORM at all. Or, if your LMS does not track xAPI, you can still send data to another LRS even if your course is inside of your old SCORM enabled LMS.

The other option is to bypass the LMS altogether and track content no matter where your content is. To do this, you need to capture who the person is through a query string in the URL. This video will walk you through publishing to just an external LRS and capturing who the person is via a query string. This could depend on your single sign-on.