Tin Can activity IDs: Storyline 2 and Watershed LRS

Apr 10, 2015

What is the current status for Storyline 2 being able to pass useful activity IDs to our LMS/LRS for Tin Can?

We are only getting long strings of activity ID #s with no clear tie to the activity name, which makes it very difficult to use the data we are getting in our LRS.



Renee Haran

8 Replies
Ashley Terwilliger-Pollard

Hi Renee, 

Tin Can API lets an activity be defined in a statement or in the tincan.xml file. We've chosen to define all activities in the tincan.xml file to improve LMS reporting. As a result, learners' responses must be cross-referenced with the tincan.xml file to be readable.

To be specific, the tincan.xml file gives the LMS all the metadata about the content (question text, answer choices, etc.), then we send statements to the LMS with unique identifiers that are defined in the tincan.xml file. To generate meaningful descriptors for learners' responses, the LMS needs to cross-reference the unique identifiers with the tincan.xml file.

This architecture is part of the Tin Can API specification defined here.

Here's an excerpt that describes what we're talking about:

"What TinCan.xml should have is: Any activity details (such as activity descriptions) that should be available to reporting systems, but will not be (or may not be) sent by the activity provider when reporting statements. That is, TinCan.xml may be used to describe activities to the LRS, as an alternative to doing that description at runtime."

The reason we exclude meaningful descriptors from our statements to the LMS in favor of collecting them in the tincan.xml file is so the LMS will know about all answer choices and not just those the learner selected.

You can find more technical information to help LMS developers implement Tin Can API for Articulate content here.

Please let us know if you need anything else!

Leslie McKerchie

Sorry that we misunderstood Philippe :) Addressing your question to Renee is why I missed that.

I'm not sure that I'm following your question fully.

Our documentation on Tin Can API can be found here, and the data should be shared with your appropriate reporting option if that's what you meant.

Just let me know what issue you are having with your project/course if needed along with what version of Storyline you are using.

Tanmay Ghosh


I am publishing my Articulate Storyline 360 course in LMS: TinCan API standards. The course has custom xAPI statement using javascript, that sends data to Watershed LRS. If I publish the course in SCORM 1.2, everything works. If I publish to TinCan API, then there is no connectivity to the LRS. On debugging, it shows bad request server error (400). I am testing the course in SCORM Cloud. Has anyone used custom TinCan statement in Storyline course (to an LRS) and published the course in TinCan API standards with success?

This discussion is closed. You can start a new discussion or contact Articulate Support.