Overview
Proserva is video-platform-agnostic — any video file or embed link works. This article covers the recommended approaches for different use cases, platform-specific considerations, and what analytics are available depending on how and where your video is hosted.
Video in Proserva Lessons (Direct Embedding)
When you want video to live directly in a Proserva lesson (not inside a SCORM package), these are the supported embed sources:
YouTube: paste the video URL or embed code. Unlisted videos work — students don't need a YouTube account.
Vimeo: paste the video URL or embed code. Privacy settings (domain-restricted, password-protected) are respected.
Google Drive: share the video from Drive, then paste the link. Students need view permissions on the Drive file.
Direct upload: upload video files directly to Proserva. All major formats supported, up to 2GB per file. Proserva hosts and streams the video natively — no external platform needed.
Direct Upload vs. Embedding
Consideration | Direct Upload | Embed (YouTube/Vimeo) |
File size limit | 2GB | No limit (platform handles it) |
Viewer analytics | Proserva lesson completion only | Platform analytics (watch time, retention) |
Access control | Course enrollment controls access | Platform privacy settings + course enrollment |
Bandwidth | Proserva serves the video | Platform (YouTube/Vimeo) serves the video |
Best for | Short videos, observations, internal content | Long lectures, public-facing content, analytics needs |
Video Inside Rise/SCORM Modules
When building courses in Articulate Rise 360 (or other SCORM authoring tools), video can be included inside the SCORM package before export:
Rise native video blocks: upload video directly into Rise, or embed from YouTube/Vimeo. This is the simplest path.
Recording tools: Loom, Screencastify, Camtasia, OBS — record your lecture or demo, export as MP4, then upload to Rise or to YouTube (unlisted) and embed the link in Rise.
Common pattern: record → upload to YouTube as unlisted → embed the YouTube link in Rise. This keeps the SCORM package lightweight (video is streamed from YouTube, not bundled in the SCORM zip) and gives you access to YouTube's viewer analytics.
Platform-Specific Notes
Panopto
Panopto works well for recording and hosting lecture videos. To use Panopto content in Proserva:
In Proserva lessons: embed the Panopto share link directly in a lesson.
In Rise modules: embed the Panopto share link as a multimedia block in Rise before SCORM export.
Analytics: all viewing analytics (who watched, how much, engagement heatmaps) stay in Panopto's dashboard. SCORM does not carry video engagement data. Module completion is tracked by Proserva; video engagement is tracked by Panopto.
VideoAsk
VideoAsk is an asynchronous video communication and engagement tool, not a lecture recording platform. It's well-suited for:
Learner check-ins and reflections
Asynchronous Q&A between instructors and students
Interactive video prompts where learners respond with their own video
When embedded in Rise:
VideoAsk appears as an interactive element inside the Rise module.
VideoAsk's own analytics (responses, view counts, watch time) stay in VideoAsk's platform — they do not flow through SCORM to Proserva.
The SCORM package only knows if the module was marked complete. Detailed interaction data stays in VideoAsk.
If learner interaction with VideoAsk is required to progress, the progression logic lives in Rise (e.g., a "continue" block after the embed), not in the SCORM tracking.
GoReact
Used by several Proserva partners (including UNLV) for video-based observations:
Students record or upload teaching videos in GoReact for timestamped feedback.
GoReact videos can be shared as public links and embedded in Proserva portfolios or course lessons.
This is primarily an observation/coaching workflow, not general instructional video delivery.
SCORM Analytics — What Proserva Tracks
When video is delivered inside a SCORM package (Rise, Storyline, etc.), the tracking data that flows back to Proserva is limited to the SCORM standard data model:
Data Point | Tracked? | Notes |
Completion status | ✅ Yes | Complete / incomplete |
Score | ✅ Yes | If assessment is included in the SCORM package |
Total time in course | ✅ Yes | Aggregate time across all sessions |
Session time | ✅ Yes | Per-session duration |
Pass/fail | ✅ Yes |
|
Individual question answers | ❌ No | SCORM doesn't transmit per-question detail |
Time per page/slide | ❌ No |
|
Clicks, navigation paths | ❌ No |
|
Video watch percentage | ❌ No | Analytics live in the video platform |
Video play/pause events | ❌ No | Analytics live in the video platform |
External link clicks | ❌ No |
|
Key takeaway: SCORM is a completion-and-score handshake, not a full analytics pipeline. Proserva reports on whether the learner completed the module and what score they earned — not what happened inside it.
SCORM vs. xAPI for Video Tracking
Proserva supports xAPI, which in theory enables richer activity-level tracking than SCORM (including video interaction data). However:
Rise xAPI exports have known inconsistent completion reporting — some courses report as all-or-nothing with no partial progress.
SCORM 2004 4th Edition is the recommended export format for Rise content in Proserva.
While xAPI could technically carry video engagement data, the practical reliability trade-off with Rise makes SCORM the safer choice for most deployments.
Bottom Line
Proserva + SCORM tracks that learners completed the training. Detailed video engagement analytics (who watched, for how long, retention curves, heatmaps) live in the video platform's own dashboard — YouTube Studio, Vimeo Analytics, Panopto, VideoAsk, etc. This is a SCORM limitation, not a Proserva limitation. For organizations that need granular video analytics, choose a video platform with robust analytics and use Proserva for course structure, progress tracking, and credentialing.