- ELB Learning Knowledge Base
- xAPI
- Storyline
-
Lectora®
- 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
- Communicating
- Admin Guide
- Lectora Player Skins
- Lectora Interactions and Scenarios
- Games
- Misc.
- Programming
- General
- Using Tracking for Progress, Status, etc
- Working with BranchTrack
- Trouble Shooting
- Working with Audio and Video
-
CenarioVR®
-
MicroBuilder™
-
The Training Arcade®
-
Asset Libraries
-
Rockstar Learning Platform
-
Rehearsal
-
Off-the-Shelf Training
-
ReviewLink®
-
The Learning Creation Studio
-
CourseMill®
-
General Topics
-
xAPI
-
Template Styles
-
Misc.
-
Articulate Storyline
-
Customizable Courseware
-
Course Starters
-
Camtasia
-
Group Administration
-
General
-
Can't find the answer? Ask our Customer Solutions team.
Storyline xAPI Tablet Scenario
***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»
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 Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
When the user scrolls trough the messages shown on the device in this interaction, they will be shown 4 buttons.
Each of these buttons has a statement tied to it, that indicates the user "reviewed tablet (or mobile) scenario #"
As it is currently built, these statements fire each time a button is clicked - the user can select multiple buttons after the first is chosen, firing additional statements about their selections.
If you'd like to limit this to only a single selection, consider adding a blocker by way of a transparent shape, or hotspot with triggers removed, on top of the buttons after intiial selection.
Alternatively, apply triggers to the content layers to disable each button on the base layer to prevent additional selections.
Each of these statements are contextually related to some values you enter for the slide identifier.
This makes them 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.
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.
This article last reviewed Nov, 2018. The software may have changed since the last review.