Per-learner activity across the platform — views, likes, shares, comments, ratings, and tracks started. The first report most admins run when a new program goes live.
The User Engagement Report tells you whether learners are actually using the platform. Use this when a program just launched and you need to know if learners showed up, or when you're investigating a drop in overall activity. Less useful for diagnosing specific content performance — use the Content Engagement Report for that.
For the strategic frame on which report fits which question, see Reporting: Which Report Should I Use?. For the mechanics of running reports, see Admin Reports in Continu.
When to Use This Report
Program launch — first 2-4 weeks. Catch low engagement early. If most assigned learners aren't logging in, the issue is rollout (communication, onboarding) before it's content quality.
Activity drop investigation. If overall platform usage drops, the User Engagement Report shows whether the drop is broad (most learners less active) or concentrated (specific cohort or department disengaged).
Identifying power users. Learners with high views, ratings, and content completion can be early adopters, beta testers, or champions for new programs. The high-activity tail is often worth recognizing.
Column Reference
User Internal ID — Unique ID within Continu.
User External ID — Matches Internal ID unless your instance is configured to use a different ID (e.g., HRIS employee ID).
Total Views — Total views across all content the learner has touched.
Total Likes — Total likes the learner has given on content.
Total Shares — Total times the learner shared content.
Total Comments — Total comments the learner posted.
Ratings Submitted — Total ratings the learner submitted.
Tracks Started — Learning Tracks the learner has started.
Plus standard learner profile columns — name, email, role, location, department, manager, hire date, last login.
How to Use This Report Effectively
Pair with assignment data. High view counts without assignment context aren't actionable. Cross-reference with Assignment Summary to see whether the views correspond to assigned content or organic exploration.
Scope to a cohort or time window. Org-wide pulls dilute signal. A program-specific date range against a specific Smart Segment surfaces patterns much faster.
Look at the distribution, not just averages. Average views per user can hide a wide spread. The bottom 20% of engagement is usually more actionable than the average.
Configuration Pitfalls
Treating Total Views as Total Engagement. A view is an open. It doesn't measure time spent, completion, or comprehension. For real engagement signal, pair with completion data from the Content Completion Report.
Drawing Conclusions Too Early. The first week of a program isn't statistically meaningful. Wait 2-3 weeks for behavior to stabilize before treating activity drops as a problem.
Ignoring Inactive Users. Users with zero activity are often the most actionable — they're the ones who haven't engaged at all. Filter for "0 views" to surface this list.
Comparing Across Date Ranges Without Adjusting for Workdays. A 30-day range with two long weekends or a major holiday week has less working time than a typical 30 days. Account for this before declaring a trend.
Where This Fits
You're here because you need per-learner engagement data. For per-content engagement, see Content Engagement Report. For completion (not just engagement), see Content Completion Report.
See Also
- Reporting: Which Report Should I Use? — the strategic anchor.
- Admin Reports in Continu — running and filtering reports.
- Content Engagement Report — engagement by content piece.
- Assignment Summary Report — assignment-level data.
- Content Completion Report — completion-focused view.
First report at program launch. Pair with assignment data. Look at the distribution, not the average. A view is an open, not a completion.