Can You Report Out On Button Use?

Apr 18, 2024

My team is having a blast learning how to use Storyline and all its features. We were successfully able to create courses that provide our learners with a "test out" option.

Leadership now wants to run analytics on this feature. They would like to know how many people are taking the "test out" option vs. completing the full course. The questions in the "test out" option are the same as in the "final test" therefore there is no way to know using the test questions. This is also not a feature that our LMS provides.

Is there a way to report "button" use to the LMS?

6 Replies

Joe Hauglie

13 days ago04/18/24 at 10:03 pm (UTC)

Yes - if you are publishing to xAPI and your LMS can manage that output.

13 days ago04/19/24 at 12:33 pm (UTC)

Yes, we are publishing using xAPI. However, I haven't figured out how to get articulate to report on the use of a single button.

Nedim Ramic

12 days ago04/19/24 at 5:13 pm (UTC)

Here is an example:

Then it's normally reported to LMS like this:

I suggest using a strong naming convention to make it easy to identify when more statements are reported. For example, name your button as "Take Course Button" so that the LMS will read it as "User000 Experienced Take Course Button," indicating that the user has clicked this button.

LXD Learning Experience Design

11 days ago04/21/24 at 8:39 am (UTC)

Hey, you could easily connect this module to Google Analytics and create events to track how each of your buttons is performing. Follow this simple tutorial, the best part is that it links Google Analytics dynamically, so you won't need to add this code each time you replubish. This option won't send the data to the LMS (you will see this from your GA account), but works well for sending the data from the LMS.

Jürgen Schoenemeyer

10 days ago04/21/24 at 5:48 pm (UTC)

google analystics is for eTraining not a good option - every add blocker will block tracking complete

10 days ago04/22/24 at 2:22 pm (UTC)

Thank you for this. I've created the triggers as you suggested.

However, when we ran our typical report in our LMS it did not pick up any of these interactions and only showed us the test responses. We've submitted a ticket with Workday, our LMS, to see what we are missing.