How to export per-Content engagement data for a Learning Track — when Track-level completion isn't detailed enough to see which content is actually working.
The Status Report tells you who completed a Track. The Content-level Analytics download tells you which specific pieces of Content inside that Track learners engaged with — and which they skipped, struggled with, or never opened. Use this when Track-level numbers look fine but you suspect something inside is broken or unused.
Use this for content audits: identifying which pieces drive completion, which get abandoned, and which never get touched by anyone. The .csv export makes the data analyzable outside Continu when stakeholders need their own view.
For the strategic frame on Track tracking and reporting overall, see Tracks and Journeys: Designing Learning Paths.
How to Download Content-level Analytics
1. Open Content. From the left-hand navigation, click Create, then Content.
2. Open the Track's Info view. Find the Learning Track you want analytics for, then click the info icon next to it.
3. Download the User List. Click Download User List. Choose All Filtered Users to export everyone in the current view, or Selected Users to export only the users you've checked. The .csv file downloads to your computer.
What the Download Shows
Each row in the .csv represents one learner's engagement with the Content inside the Track — completion status, dates, and per-Content interaction data. This is the only export view that surfaces engagement at the Content level rather than the Track level.
Use the download when you need to answer questions like:
Which pieces of Content are driving Track completion? Look for Content with high completion rates across learners who finished the Track. That's the proven material.
Which pieces are stalling learners? Look for Content with low completion rates relative to its position in the Track. If most learners pause at the same step, that step may need rework.
Which pieces is no one touching? Content that almost no one starts is dead weight in the Track. Either move it earlier, replace it, or remove it from the sequence.
Configuration Pitfalls
Filtering the View, Then Forgetting It. "All Filtered Users" exports whoever is in the current view, not every learner. If you applied a filter (department, segment, date range) and forgot, the .csv only contains the filtered subset. Clear filters before exporting if you want the full picture.
Using This Instead of the Status Report for Coverage. The Content-level download is for analyzing what's happening inside a Track, not for tracking overall progress. For who-completed-the-Track-and-when, use Learning Track Status Report instead.
Treating Low Engagement on Optional Content as a Problem. If a Track has both required and supplementary Content, low engagement on the supplementary pieces may be by design. Decide what counts as a problem signal before reading the data.
Reading a Single Download as a Trend. A one-time export shows a snapshot. To see whether your Content edits actually improved engagement, pull the same export before and after the change and compare.
Where This Fits
You're here because you want per-Content engagement detail inside a Learning Track. For Track-level completion and progress, use Learning Track Status Report instead. The broader reports index lives in Admin Reports in Continu.
See Also
- Tracks and Journeys: Designing Learning Paths — the strategic anchor.
- What is a Learning Track? — the gateway article.
- Add a Learning Track — building the Track this report analyzes.
- Learning Track Status Report — the Track-level progress view.
- Admin Reports in Continu — the broader report index.
Per-Content data for content audits. Pair it with the Status Report — one shows what's happening inside a Track, the other shows whether learners are getting through it.