xAPI Sequence Captivate

***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 Captivate yet?
For files released April 2019 and older, watch this video»
For files released May 2019 and later, watch this video»

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

In addition to the standard Captivate statements that fire in an xAPI publish, we've added a number of custom statements to give you some deep tracking on your interaction.

There are two types of custom statements in this file: 1 type fires when each dragger is placed in the correct dropzone.
It looks like this.

The second type fires when the interaction is complete, and looks like this.
If you review the full JSON, you'll see that we've added some detail about the correct response pattern, and how the user actually responded.

Each of these statements are contextually related to some values you enter for the course identifier.
This makes them easy to sort and filter, and provides some nice visualization in the analytics dashboard of your LRS.
Since they're structured differently, each type can be filtered and reported on differently.
Each can also be disabled or edited quickly and easily.

To use our statements, navigate to the "advanced actions" tab.
On the check answer action, you'll see a number of tabs labeled 1-6 - on each of these, you'll see several xAPI variables and an Execute JS trigger.
Enter the details for your slide in the variables here, then press OK to update the action.
Make sure to check out our xAPI overview video for more details on these details.

The "answered" statement is on its own tab in this same action group. It's called xAPI-Answered.

Once you edit the values you're going to edit, 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

This article last reviewed Dec, 2018. The software may have changed since the last review.