{{baseUrl}}/meetings/:meetingId/recordings/analytics_details?page_size=30&next_page_token=&from=&to=&type=by_view
Is not giving correct duration.
{{baseUrl}}/meetings/:meetingId/recordings/analytics_details?page_size=30&next_page_token=&from=&to=&type=by_view
Is not giving correct duration.
Hi @Nitesh what are you expecting to see?
[quote=“Nitesh, post:1, topic:133602, full:true, username:Nitesh”]
{{baseUrl}}/meetings/:meetingId/recordings/analytics_details?page_size=30&next_page_token=&from=&to=&type=by_view
Faculty Requirement: Viewing Accurate Student Watch Duration for Recorded Meetings
As a faculty member, I need the ability to view the accurate duration each student has spent watching an archived or recorded meeting. This information is critical for identifying students who may not have fully engaged with the recorded session, so appropriate follow-up actions can be taken.
We are currently using the Zoom API endpoint:
GET /meetings/{meetingId}/recordings/analytics_details
This is used to retrieve analytics details for a meeting recording using the meeting UUID.
Issues Observed:
Duration Recorded as Zero for Short Views
If a user watches the recording for less than 60 seconds, the viewing duration is returned as 0, even though the user did access the recording.
Inaccurate Duration for Longer Views
When a user watches the recording for more than 60 seconds, the returned viewing duration does not reflect the actual time watched. It often underreports or provides inconsistent values.
Request:
We need a reliable method or endpoint that returns the actual number of seconds each student viewed the recording, regardless of how short or long the session was.
Please guide us on:
Whether there is a more accurate API endpoint available
If this is a known issue with Zoom analytics
Any recommended workaround or solution to obtain accurate viewing durations per student
@gianni.zoom please see my observation.
Hi @gianni.zoom I updated my observations and expectations, please take a look asap.
Thank you @Nitesh , I am taking a look.
Hi @Nitesh has this been resolved? This is definitely unexpected. If you’re still seeing this, please send me an updated zm-tracking-id.
It still not resolved yet.
Please provide your email, I will share request Id.
Please check your notifications for the private message!