xAPI & Storyline

Creating xAPI Statements in Storyline 360 [Part 1]

Articulate recently released a new update to Storyline 360 that allows you to trigger custom xAPI statements to Storyline 360. This new feature works very similarly to other triggers in Storyline. You select a button or page you want to track and add the xAPI trigger.

Here, you can select the verb (action) you want to track and add an object that describes the action. This trigger can pull from page titles, variables, or custom text to help define the action. So, you can track when a page loads, when a page completes, when the users click on tabs or when they don't click on a tab on the page. This level of reporting gives you a lot more detail into how the learner interacts with your page than you ever could get with SCORM.

Implementing custom xAPI inside of Articulate Storyline 360 is far from perfect, but it is a tremendous step forward, and I think it will only get better with time.

After you have added your triggers inside your course, you then publish them to the xAPI or cmi5 capable LMS and ensure the course resides inside the LMS. Having the course in the LMS is how the course knows who is taking the course. We will explore in the following video how to do this when your content is outside the LMS.