Articulate Storyline 360 Announces New Custom xAPI Functionality

Articulate has announced new custom xAPI statement functionality in their Storyline 360 product. So why does that matter and what does it mean for you? This blog post explores some of the highlights of the update, and considers why this is important for Storyline 360 users, and our industry as a whole.

What’s the update?

Articulate Storyline is one of the most popular rapid eLearning authoring tools used by our customers. Storyline has supported xAPI since before the release of xAPI 1.0.0, tracking SCORM-parity data—such as course completions, slide views, question responses, and assessment results. The new updates allow for further insights to be gained across the learner journey.

Instructional designers and other Storyline 360 users can now generate custom xAPI statements that are sent based on custom triggers within their courses. This new functionality offers greater tracking of learner choices, pathways and completions of custom content features that were previously not trackable.

You can read more about the update on Articulate’s help site, or check out this LinkedIn post from Megan Torrance and Matt Kliewer.

Wasn’t this already possible?

Previously, you could send custom xAPI statements from Storyline triggers; however, doing so could be technical and complex. The method required either coding the statements yourself using JavaScript or using a third-party tool, such as

In fact, that’s exactly what the team at Nebraska Medicine has done! They used to create an eLearning course that used custom xAPI tracking to facilitate and track an adaptive learning experience. Learners were presented with tailored content based on their feedback during the course, ensuring they only completed relevant content, saving time in the process.

Watch the webinar "Using xAPI with SCORM in Instructional Design" to find out more!

Why is this feature important?

This new feature is important for the L&D industry and xAPI adoption for two reasons:

  1. For Storyline users: This new functionality unlocks possibilities for tracking with xAPI beyond what was possible with SCORM—especially if you are building more creative courses than the traditional ‘next-next-next-quiz’ format. You now have additional flexibility to track learner choices and pathways through your content. And if you’re looking for somewhere to store that new data, a free Essentials LRS account might be a good place to start.
  2. For the wider L&D industry: A big player such as Articulate taking xAPI seriously sends a message that xAPI is not going away and there is demand for xAPI support in products beyond SCORM parity. Lectora has had support for custom xAPI statements for a number of years now, and Storyline now offering similar functionality puts even more pressure on other authoring tools to do the same.

What does this mean for your data governance?

As Spider-Man says: “With great power comes great responsibility.” The ability to send custom xAPI statements from Storyline courses empowers you to generate some really valuable data. Interactions on custom content (think games, puzzles, and simulations) and branching scenarios can now all have their learner behavior fully tracked.

Of course, you should take care not to accidentally use those powers for evil and generate bad data that will confuse and complicate your reporting! Good xAPI governance rules and processes are the way to avoid this. And as luck would have it, we’ve created an xAPI Governance guide to take you through the process! Enjoy!

Subscribe to our blog

Rules Help Control the Fun!

We’ve compiled everything from our xAPI Governance blog series into this handy guide—including best practices, tools, and technology for cleaning up and maintaining good data.

This website stores cookies on your computer to improve your experience and the services we provide. To learn more, see our Privacy Policy