Vimeo videos shared as assets - not showing in reports

This is a known behavior rather than a bug, and it ties directly into a tension that comes up often — wanting frictionless video access without enrollment, while still getting reliable tracking and discoverability.

On the Channel reports side: Link-type assets (like Vimeo URLs) generate far fewer trackable events than natively uploaded videos. When a learner clicks a Vimeo link, playback happens in Vimeo's player — so Docebo can only record that the asset was accessed, not watch time or meaningful completion data. This is why those assets appear thin or missing in the Channel Statistics and Asset Statistics reports. More detail here: Discover, Coach & Share Reports.

On the Harmony search side: Harmony indexes titles, descriptions, tags, and — critically — audio transcripts. For natively uploaded videos, Docebo's AI processes the audio and auto-generates searchable content. For external Vimeo links, there's no audio to process, so Harmony only has whatever title and description you manually added. Thin metadata = invisible to search.

The deeper issue — and a thread worth reading: This is actually the same challenge explored in this community discussion, where the conclusion was that channels alone can't provide the tracking most organizations actually need. What one organization I've worked with landed on is using micro-courses with Focus Mode — courses configured to open directly into full-screen video playback, bypassing the enrollment feel entirely. You get proper completion tracking (Docebo tracks actual watch progress at 90% for short videos), full Harmony indexability, and an experience that feels no heavier than browsing a channel. The "course" wrapper becomes invisible to the learner.

If switching off Vimeo links isn't possible, at minimum enrich every asset with a detailed description and manual tags — that gives Harmony something to work with. But if the goal is true reporting and discoverability, the micro-course approach is worth seriously evaluating.

Hello!

Appreciate the super detailed reply. I understand tracking in channels is limited and made the choice of using them as we are not chasing completion metrics. 

However, we thought at least asset access was going to be recorded, just to understand what content is being accessed more. Quoting your reply, “When a learner clicks a Vimeo link, playback happens in Vimeo's player — so Docebo can only record that the asset was accessed,” - however, currently, not even the user accessing the asset is getting recorded - so that’s what I’m wondering if it’s also a known behaviour or something that I could do something to fix.

Thanks again for taking the time to answer.

Good question, and worth being precise about where to look — because it's not the channel-level report.

The report that tracks per-user asset access is called Viewer – Asset Details, found under Admin Menu → Reporting → Reports → Discover, Coach & Share → Viewer - Asset Details. It shows, per user, which assets they accessed, the first access date, last access date, and access count. This is the closest thing Docebo has to "who watched what" in channels.

If you run that report and see zero data for your Vimeo assets, it points to a specific issue: Docebo only registers a view when the content loads inside the Docebo environment. If your Vimeo videos are opening in a new tab or redirecting to Vimeo's site rather than embedding inside the channel player, no access event is fired — which would explain why even basic access isn't being recorded.

Two things worth checking on the Vimeo side:

• Go to the video settings in Vimeo → Privacy → confirm that embedding is allowed, and specifically that your Docebo domain is whitelisted
• Check how the assets were added to the channel — videos added as proper video-type assets should embed inline in Docebo's player; assets added as generic links may not

If the videos are embedding correctly and the Viewer – Asset Details report still shows nothing, that's worth a support ticket to Docebo, as it would indicate a tracking issue specific to your instance.

Reference: Discover, Coach & Share Reports

Thank you, Moshe - really useful information. I will try with the options you listed. Appreciate the support!