Skip to main content

Tracking learner progress in your LMS

When a Story counts as completed, what each integration sends to your LMS, how resume works, and how to test and troubleshoot tracking.

When your Stories run through a learning management system (LMS), the LMS can record who started and completed them, and with some integrations, what learners chose and answered along the way. This article explains exactly what We Are sends to your LMS, when a Story counts as completed, how learners pick up where they left off, and how to test and troubleshoot your setup.

Let me show you how it works.

What gets sent to your LMS

What your LMS receives depends on how the Story is connected:

Connection

Started and completed

Quiz answers and choices

Passed or failed

Story link or embed

No

No

No

SCORM 1.2

Yes

No

No

SCORM 2004

Yes

Yes, as interactions

No

Custom xAPI / cmi5, Palms, Learning Center

Yes

Yes, as xAPI statements

Per quiz, when the quiz has a pass/fail result

Motimate

Completed

No

No

We Are doesn't send an overall score for the Story, and a Story never shows as Passed or Failed in a SCORM report. Set up the activity in your LMS with completion as the requirement, not a score or pass mark.

An LMS report row for a learner who completed a We Are Story, for example a SCORM Cloud registration or a Moodle activity report, with the status Completed highlighted.

When does a Story count as completed?

By default, a Story is completed when the learner reaches a last node in your nodemap and presses Continue. This makes sure the learner has seen the ending before it counts.

If you'd rather count the Story as completed as soon as the learner arrives at a last node, you can change this per Story:

1) Open the Story and go to Story Settings → Other.

2) Turn on Complete story when the learner reaches the last node.

The Story Settings panel open on the Other tab, with the Complete story when the learner reaches the last node toggle switched on and highlighted.

The setting applies to SCORM, xAPI/cmi5 and the built-in integrations alike. Completion is sent once per playthrough, so a learner who replays the Story is reported as completed again only when they finish again.

🦸🏽‍♀️ Pro tip: If your Story has several endings, every last node counts. Make sure each ending is a place where you're happy for the Story to be marked as completed.

How learners pick up where they left off

When a learner returns to a Story they've already started, they can choose to continue where they left off or start from the beginning.

The resume dialog a returning learner sees in the player, showing both options: continue where they left off, and start from the beginning.

Where the saved progress is kept depends on the connection:

  • SCORM: in your LMS, so the learner can continue on any device.

  • Links, embeds, xAPI/cmi5 and the built-in integrations: in the learner's browser, so they can continue on the same device and browser. Private browsing or clearing browser data removes it.

Any change to a published Story resets learners' saved progress. Saved progress belongs to the version of the Story the learner was playing, so after an edit, learners start from the beginning. If learners are partway through a Story, consider waiting with edits until they're done.

Testing your integration

Before you roll a Story out to learners, run through it once the way a learner would. This takes about ten minutes and catches almost every setup problem.

1) Publish the Story, and for xAPI/cmi5 or a built-in integration, select your integration under Share → Connect LMS for tracking.

2) Launch the Story from the LMS, signed in as a test learner. A plain Story link or the preview in We Are never sends tracking data, so they can't be used to test it.

3) Play to a last node and press Continue. If the Story has quizzes or response nodes you want to report on, answer at least one of each on the way.

4) Check the result in the LMS:

  • SCORM: the test learner's attempt shows as Completed. With SCORM 2004, their answers appear as interactions.

  • xAPI/cmi5: the LMS or LRS shows an initialized and a completed statement for the test learner, with your activity ID as the object.

5) Open the Story again from the LMS, leave halfway, and open it once more to check that you're offered to continue where you left off.

AnLMS statement listing the statements from one test playthrough: initialized, a few answered or responded, and completed.

🦸🏽‍♀️ Pro tip: Testing a SCORM package without access to the customer's LMS? Upload it to a free SCORM Cloud account. If it works there but not in the customer's LMS, the difference is in the LMS settings.

Your integration is ready when the test learner shows as completed, the answers you expect are there, and resuming works.

Troubleshooting

Nothing is tracked

  • Check that the Story was launched from the LMS, not from a copied link, an embed or the preview in We Are.

  • For xAPI/cmi5: the LMS must pass the learner as the actor launch parameter. Without it, no statements are sent. Also check that the integration is enabled and selected under Connect LMS for tracking.

  • For xAPI/cmi5: your LMS's xAPI endpoint must be reachable from the internet. We never send statements to internal or private network addresses.

The Story isn't marked as completed

  • By default, the learner must press Continue on a last node. Learners who close the Story on the last scene aren't completed. Turn on Complete story when the learner reaches the last node if that suits your Story better.

  • Check that the LMS activity uses completion, not a score or pass mark, as its requirement.

The Story is marked as completed too early

  • Check whether Complete story when the learner reaches the last node is turned on, and whether your nodemap has a last node the learner can reach earlier than you intended.

The Story starts from the beginning when the learner returns

  • Check whether the Story was edited since the learner's last visit, since edits reset saved progress.

  • With links and xAPI/cmi5, progress is saved in the learner's browser, so it doesn't follow them to another device or browser.

  • Some LMSs with strict SCORM settings restart the activity when a learner leaves and comes back. If this happens without any edits to the Story, contact us with the name of your LMS.

There's no sound when the Story starts

The Story doesn't load inside the organisation's network

  • Stories play from play.wearelearning.com, also when they're started from a SCORM package. Ask the IT team to allow this address. If the Story still doesn't load, contact us and we'll help you find what's being blocked.

Still stuck? Reach out via the chat and include the name of your LMS, how the Story is connected, and a screenshot of what the LMS shows.

Related Articles

Did this answer your question?