The Metric report is designed to provide a detailed overview of your Collaborate with the Ultra experience usage. Information includes the frequency and scale your institution is using so you can make informed decisions about the service.
This report uses the UTC/GMT (00:00) time zone to calculate session metrics daily.
Download the Metric report
The Metric report is available as a CSV download only. Only managers can download the Metric report.
iPhone and iPad users should have Microsoft Excel installed on their device to view the report properly.
- Log into the Scheduler as a manager, select Reports and Institution reports.
- Select Metric report.
- Choose the Date range for the report. The date range can't be longer than 6 months. Uses the UTC/GMT (00:00) time zone.
- Select View Report.
The Metric report includes several columns, and each column is aggregated per day. For example, if you would like this report run for a week there will be 7 rows in the CSV. Each row represents a single day.
Metric CSV export column names
- SessionsCreated: Number of total unique sessions created during the date range. These sessions may or may not be launched during the date range.
- SessionInstancesLaunched: Number of unique session instances launched in the date range. Sessions launched may include existing and new sessions.
Sessions launched counts the first person to join. All other attendees who join aren't counted. For example, if you had 1 session and 10 people joined it ,the number of sessions launched is 1.
- SessionTime: Total room time across all sessions, regardless of the number of users that attended each session (HH:MM:ss). This time different than the minutes entitlement metric that is in customer contracts.
For example, if there are 5 attendees in a 30-minute Collaborate session. The SessionTime is 30 minutes, however the total minutes for entitlement purposes is 150 minutes.
- Attendees: Number of attendees (in all sessions)
- AttendeesUnique: AttendeesUnique shows how many attendees joined a session each day of the report. It doesn't count if the attendee joined more than one session. But it does count attendees as new each day. For example, an institution has 50 students and teaches 20 sessions in a day. All 50 students attend those 20 sessions. Attendees would be 1,000 but AttendeesUnique would only be 50. Do this for two days and the AttendeesUnique is 100.
AttendeesUnique for each day is counted as the sum of two measures:
- Integration (LMS) and logged in attendees: The number of attendees that accessed sessions in Collaborate from the LMS or logged into the Collaborate session server directly. For these attendees, the attendee name that appears in the session isn't relevant. Even in the case where there are two different students with the same name, we are able to count the number of unique users from the information available to the Collaborate server.
- Guest attendees: The number of guest attendees with unique names across sessions, as follows:
- If an attendee with the same name reconnects to a session, we don't count the second instance of this attendee. For example, Peter joined the session Bio 101. Peter's status shows reconnecting. Peter is not counted again after he reconnects.
- If the same or another attendee joins from a different browser using the same name, this name enters the session as “Peter #2” and is counted.
- If another attendee with the same name joins a different session, this attendee is also counted. For example, if a different Peter joins the History of Arts session, this new Peter is counted.
Names are provided by guest attendees when they join the session. Guest attendees are only double counted when there’s no way to determine whether a user is the same or a different person based on the information provided.
- AttendeesSessionPeak: Highest number of concurrent attendees in a single session (peak number of attendees in a session, at any point in time)
- AttendeesPeak: Highest number of attendees in a login group that were in sessions for that day
- SessionInstancesPeak: Highest number of concurrent sessions (unique instances of a session), highest number of unique sessions running at the same time
- Session20: Number of sessions with at least 20 attendees
- Session50: Number of sessions with at least 50 attendees
- Session100: Number of sessions with at least 100 attendees
- Recordings: Number of recordings made
- RecordingDuration: Number of recorded minutes