Reporting overview
The Reporting section gives you one place to see how users engage with all of your content – labs and tracks together. You no longer need to check separate reports per content type: every report covers everything you’ve shared, and a content filter narrows it down when you need to.
The reports
Section titled “The reports”Activity – engagement over time for your content: how many sessions were started and completed, and how many people they reached. Use it to see which content performs and how engagement develops.
Users – everything from the perspective of the user: who played your content and what they did across all of it.
Sessions – every individual session, with the details of what happened inside it. Open a session to see the user’s step-by-step activity log.
Logs – the live and historical operational view: sandboxes provisioning, setup scripts, warnings, and errors. Use this for troubleshooting rather than engagement reporting.
Filtering by content
Section titled “Filtering by content”When you open a report, everything is selected by default – all your tracks and all your labs in one table. Use the content filter to narrow down to specific content, or to one content type. Your filter choices stay in place while you move between content types, and they carry over into your exports.
All other filters apply to both content types equally, including session types.
The Authors filter matches tracks by their developers, and labs by who created or last edited them.
Exporting
Section titled “Exporting”Each report can be exported to CSV. An export from a merged report includes both content types in one file, using the same content terminology as the UI.
- Some details apply to one content type only – for example, time paused or Hot Start details for tracks. Where a session doesn’t have that information, the field simply stays empty.
- If your team doesn’t use labs yet, you’ll see your tracks only, and the lab options in the content filter are hidden.