- Quick Win Tutorials
- Getting Started
- Modular Development (ModDev)
- Quick Guides
- Best Practices
- Navigating the Workplace
- Building a Title
- Importing Content
- Working With Text
- Working with Images
- Working With Objects
- Actions and Variables
- Tests, Surveys, and Questions
- Working with Web Windows or HTML Extensions
- Publishing a Title
- Creating Web-based, Accessible Content (Section 508/WCAG)
- Lectora Layouts
- Managing Titles
- Managing your Assignments
- Managing Your Notifications
- Admin Guide
- Lectora Player Skins
- Lectora Interactions and Scenarios
- Using Tracking for Progress, Status, etc
- Working with BranchTrack
- Trouble Shooting
- Working with Audio and Video
The Training Arcade®
Rockstar Learning Platform
Can't find the answer? Ask our Customer Solutions team.
On all Course Starter interaction slides, we include custom xAPI statements that track object-level learner actions.
Currently, Captivate only sends an "experienced" statement when a learner visits a slide.
No other data is really being sent about what they did on that slide.
We added to that by including custom statements on each of the objects in an interaction.
So if a user clicks a tab on slide 3, you'll see that in your LRS.
If they answered a text entry or chose option 2 in your scenario from slide 9, you'll see that too.
And we add context to our statements to map them back to the slide level and course-level for deeper analytics and better data display in your LRS.
Setup and approach is largely the same for all interactions.
- Where elements use an advanced action for their behavior, you can access the full xAPI setup (similarly on the base versions of each of the shared actions we leave in a starter file).
- Where elements use a shared action, you can access and edit the labels for the verb ID and verb display values via the shared actions parameters pane. You will not see the actions for the remaining steps in the xAPI sequence; other actions have been de-parameterized.
There are a few exceptions, however.
Any interaction that includes a mastered/passed/failed interaction will include a bit more detail than a standard statement. In addition to the standard statement, we include a result element that indicates if they successfully completed the interaction or not.
This response element should be fairly easy to chart in any LRS with an analytics package.
Anywhere there are bigger changes to approach with xAPI, we'll note it in the interaction's instructions block at the left side of the stage.