SCORM and xAPI analytics and tracking tools
Turning completion records into something worth reading.
Compiled and checked by the scorm-tools.com editor.
An LMS will tell you who completed a course. It is usually much less helpful about anything else: where people dropped out, which question everybody fails, whether the course is worth its production cost, or what happened across the six systems your organisation actually uses.
The tools here fill that gap from two directions. Statement analytics sit on top of an xAPI record store and turn a stream of statements into dashboards, cohorts and reports — the natural pairing if you have already adopted xAPI. Launch and delivery tracking works at the package level instead, recording when and where a course was opened and how far it got, which is the pragmatic option when the content is SCORM and always will be.
One thing to settle early, because it is a data-protection question and not just a technical one: how much of this is personally identifiable, how long it is kept, and who can see it. Learner-level analytics are genuinely useful and genuinely sensitive, and the answer should be written down before the dashboard is built rather than after someone asks.
0 tools · 0 open source · 0 support cmi5
Order is editorial and never for sale: standards coverage first, then maintenance state, then popularity, then alphabetical. How we list .
Tools in this category
No listings here yet
Questions people ask about analytics & tracking
Can I get analytics from SCORM without moving to xAPI?
Yes, within limits. SCORM reports completion, score, time and a small data model — enough for drop-off and pass rates, not enough for fine-grained interaction analysis. Launch-tracking tools add a layer of their own without requiring you to re-author anything.
Do I need a separate analytics tool if I have an LRS?
Often, yes. Most record stores are built to store and serve statements correctly rather than to visualise them well. Some ship a reporting layer; the rest expect you to bring one.
What should I measure?
Start with completion rate, time to complete, and per-question failure. They are cheap, comparable across courses, and answer the question that actually gets asked — is this course working?