- User Types
- Any user with access to the report builder (Global Admins, Area Admins, and some Users) can create reports looking at xapi.ly data.
- Available on paid plans (Analyst, CLO, and Enterprise).
- Anybody can use this feature.
Why would I use xapi.ly?
Articulate Storyline already has a good xAPI implementation and is a Watershed Certified Data Source. So why do you need xapi.ly? There are three scenarios where xapi.ly might help.
- You want to add extra tracking. If your course contains custom interactions or anything else beyond the basics, it's helpful to add additional tracking to those elements. xapi.ly provides a much easier way to add that tracking than coding it yourself.
- Your LMS does not support xAPI packages. In this scenario you can publish your Storyline course as a SCORM package and add xapi.ly tracking to send the data to Watershed. (You might also consider upgrading to a modern LMS that does support xAPI!)
- You want the course to stand alone outside the LMS. In this scenario, xapi.ly will ask the learner who they are and send all the data to Watershed. Alternatively, Watershed has created free example code in case you want to build a stand alone launcher yourself.
Connecting xapi.ly to Watershed
To connect xapi.ly to Watershed, you will need to configure Watershed as the LRS endpoint within xapi.ly. These settings, alongside helpful instructions are found on the xapi.ly publish page (You need to be logged into xapi.ly to access this page).
See How do I add an activity provider to Watershed? for where to get your endpoint, key and secret from Watershed.
Please note: This configuration advice applies for content published for SCORM or web. If you publish as an xAPI package, xapi.ly will use the same LRS details as Storyline, which are normally configured in the system launching the content (e.g. the LMS).
Configuring xAPI statements in xapi.ly
Details of how to create xAPI statements in xapi.ly are covered in the xapi.ly documentation. xapi.ly has a lot of flexibility in terms of the xAPI statements you can create. This gives you a lot of power to track a wide variety of interactions, but also gives you the power to create bad data that could adversely effect your reports. To avoid this, be sure to read up on xAPI Statement Design and xAPI Governance before you start creating statements.
Reporting on xapi.ly data
Since xapi.ly statements are so flexible, we can't provide specific guidance on configuring reports. The best reports for your data will depend on what that data is.