Storyline

Storyline xAPI 4-Button Multiple Choice Knowledge Check

***All template files are tested using modern browsers, such as Chrome and Firefox. We do not support or test using Internet Explorer.***

Have you watched the xAPI Overview/Setup video for Storyline yet?
For files released April 2019 and older, watch this video»
For files released May 2019 and later, watch this video»

Today, we're going to take a quick look at how to use the xAPI features in this file.

There are two ways to get this file reporting the xAPI data you'd like!

First, since we've set this template up as a Storyline quiz question, you can always use Storyline's built-in xAPI reporting features to get some deep insights into your users' responses.
To do so, you'll need to have a results slide tied to this interaction.
This can be anywhere in the file, and, in fact, you could use a blank results screen, dressed up as a standard content screen if you didn't want to show any formal results to your users.
However you do it, the default statements look something like the following [SCREENSHOT of REPORTING & ANALYTICS].
Aside from the usual "experienced" statement, you'll also see an "Answered" statement coming out of SL.
This statement contains a lot of detail, including the correct answer pattern, what the user's answer was, and success, to name a few bits.
It's not super-readable though.
You can certainly create reports through your LRS or with the help of a developer.

We've included an additional option that's a little less compact, but more readable too.
When the user presses the submit button, we throw a single statement indicating which button they selected.
This statement is contextually related to some values you enter for the slide identifier.
This makes it easy to sort and filter, and provides some nice visualization in the analytics dashboard of your LRS.

To use our statements, make sure DISABLE_xAPI is set to FALSE.
Then, enter the details for your slide.

Make sure to check out our xAPI overview video for more details on these details.


If you look closely at the triggers pane, you'll note that the actual statement only occurs once on this template.
It fires when the submit button is clicked, and sends whatever the last updated variable values were, prior to clicking that button.

Once you edit those values, your file is set up and ready to go.

From here, you'll need to publish and launch your files to see statements.
Check out our "publishing to xAPI" video for more detail.