Skip to main content
Question

Tracking Storyline SCORM Clicks

  • July 31, 2025
  • 3 replies
  • 84 views

Forum|alt.badge.img

Hi,

 

Our team is creating training on processes in a system. We plan to build a click through practice activity in Storyline. We are brainstorming different ideas to measure success rather than just using quizzes. Does anyone here have experience with building practice “click-through” and getting data on the learner’s click accuracy? If yes, do you have tips on how to do this using storyline SCORM 1.2 or 2004 and the correct settings in Docebo to get the data?

 

Thanks

3 replies

gstager
Hero III
Forum|alt.badge.img+8
  • Hero III
  • August 1, 2025

Well…

I am not a Storyline user but I have made “click-thru” activities designed to track the number of mistakes made in the process. Perhaps you can find a satisfactory solution based on the approach that I used.

In my case, the process was navigation through the programming menu of a device involving pressing buttons.

  1. I identified every step in the process and created a custom variable called “step” and one called “mistake”.
  2. I created a clickable area for each button over the image of my device.
  3. I used a ton of conditional logic with following type of check on each button
    IF (this is the right step) {
        DO STUFF;
        Increment the
    step variable;
    }
    ELSE {
        DO OTHER STUFF IF NECESSARY;
        Increment the
    mistake variable;
    }
  4. At the completion of the task, I present to the learner the number of mistakes they made during the task. 

Now… I have simplified this greatly but hopefully the concept helps you with your approach. I have created some projects with as many as 50+ steps.

Each button gets used many times so eventually it has multiple steps for which it checks so there are many IF statements for each one.

I chose to use JavaScript over a bloated series of advanced actions/triggers.
Hopefully this helps in some way.


Forum|alt.badge.img
  • Author
  • Novice III
  • August 1, 2025

Well…

I am not a Storyline user but I have made “click-thru” activities designed to track the number of mistakes made in the process. Perhaps you can find a satisfactory solution based on the approach that I used.

In my case, the process was navigation through the programming menu of a device involving pressing buttons.

  1. I identified every step in the process and created a custom variable called “step” and one called “mistake”.
  2. I created a clickable area for each button over the image of my device.
  3. I used a ton of conditional logic with following type of check on each button
    IF (this is the right step) {
        DO STUFF;
        Increment the
    step variable;
    }
    ELSE {
        DO OTHER STUFF IF NECESSARY;
        Increment the
    mistake variable;
    }
  4. At the completion of the task, I present to the learner the number of mistakes they made during the task. 

Now… I have simplified this greatly but hopefully the concept helps you with your approach. I have created some projects with as many as 50+ steps.

Each button gets used many times so eventually it has multiple steps for which it checks so there are many IF statements for each one.

I chose to use JavaScript over a bloated series of advanced actions/triggers.
Hopefully this helps in some way.

 

 

This is helpful - does the data show up in Docebo? If yes, what settings do you need to place in the course and where can you find the results/data of the users accuracy? 


gstager
Hero III
Forum|alt.badge.img+8
  • Hero III
  • August 1, 2025

I admit that I have not tried to actually capture the learners number of mistakes in Docebo.

Mostly - these sorts of activities for us is a matter of practice and building proficiency.

Learners are presented on screen with their number of mistakes and can perform the activity as often as they wish - hopefully reducing the number of mistakes along the way.

In the few cases where the number of mistakes is used as the basis of whether or not the activity is marked complete - I use a little more conditional logic at the end to jump them to an extra slide for presentation of the results and an activity complete message. They can still perform the activity again for practice but they get the completion credit. I just set the criteria for completion in my SCORM export to be viewed all slides knowing they cannot get to the last slide unless they have met the criteria within the module itself.

I never use built-in navigation controls - only my own so scrubbing ahead is not possible.