Forum Discussion
RESOURCE: Full Guide to xAPI and Storyline
Hello lovely Articulate Storyline users!
I've been working on an in-depth guide to sending custom xAPI statements from Articulate Storyline courses for over a year now, and the full guide is final...
Hiya, I'm dipping my toes into xAPI as we're looking at different LMS/LXP.
Looking at your guide has me a little bit worried as it seems so much additional work. With xAPI do you have to build a JSON object for every interaction?
As a minimum we don't want to lose any reporting function we currently have with SCORM 2004, (report on what questions people have answered and if they've got it right or not.) I know xAPI can record so much more, but do you have to manually build that in the JSON file even when using storyline?
Any help would be great
Hi Helen,
Storyline does have default xAPI output, but you will get a TON of statements (“User experienced Slide Name” every time the user views a slide, for example).
The custom approach gives you full control over which statements you send and how to send them. It takes a bit of up-front work to build the JavaScript function(s), but once you do that, you just need to add execute JavaScript triggers with one line of JavaScript in them that tell the function which elements to include.
So no, you only need to build the JSON objects once (or a few times if you need to structure your statements differently depending on the use case). When it comes to sending the statements from Storyline, it’s as simple as an execute JavaScript trigger that passes the correct elements into the function.
That might sound confusing if you’re brand new to JavaScript, but I’m happy to answer any other questions to clear things up!
