Track meeting quality and statistics

Meet quality tool

This feature requires having the Admin quality dashboard access privilege.

Use the Meet quality tool (MQT) to troubleshoot your organization’s Google Meet meetings and identify the root cause of issues. For example, you can see an overview of meeting metrics, find and debug meetings, view network statistics (jitter, packet loss, and congestion), network connection delay (RTT), microphone level and received audio level, or view system (CPU) statistics. The MQT is a troubleshooting tool, not a real-time monitoring tool, so some metrics may be delayed.

The MQT saves data for 30 days. For more information, go to Data retention and lag times.

Open the Meet quality tool

You must be signed in to an admin account with the appropriate privileges to access the Meet quality tool.

Open the Meet quality tool

To access the tool from the Google Admin console, go to AppsGoogle WorkspaceGoogle Meet and click Meet quality tool. If you are already logged in, you can also search for a meeting code, organizer or participant in the search bar on any admin page.

Filter information & grant access to the tool

Expand all | Collapse all

See information and filter data

Views

Meetings view

Shows the meetings organized or joined by users in your organization.

Participants view

Shows the users in your organization that joined meetings.

Google meeting room hardware

Shows the Google meeting room hardware in your organization that joined a meeting.

Filter and sort

You can filter and sort the data to:

Find a meeting.
See data for one room over a period of time.
See data for a specific location.
Find problematic meetings or devices.
Find meetings on a specific day.
Find meetings where more than 50 participants joined.

To filter data:

Click Add a filter.
From the list, select a filter.
Set the filter values and click Apply.
(Optional) To sort the filtered data, click a column header.

Summary bar

Depending on which view you select, the summary bar shows statistics for meetings, participants, or devices.

Meeting, participant, and device statistics

Statistic	Description
Duration	Average meeting time.
Meetings	Total number of meetings.
Participant connections	Total number of connection endpoints.
Device connections	Total number of Google meeting room hardware devices that joined meetings.
Network congestion	Percentage of time that network constraints prevented a device from sending higher-quality video.
Packet loss	Percentage of packets lost on the network. This includes packets sent from a client to Google and received by the client from Google.
Jitter	Variation in latency on packets flowing between a client and Google.
Feedback score	User rating submitted at the end of a meeting.

Review meeting statistics and details

To review statistics about an event:

On the left, click Meetings view .
From the list, click a meeting to view detailed meeting information including a timeline of events.

View

Description

Meeting Information View

Information about the meeting. This includes the meeting code, date, status, start and end times, duration, and organizer’s email.

If the meeting was recorded, the recording status also appears in this section:

Started—The meeting is ongoing.
Stopped—Shows the duration of the meeting.
Uploaded—The recording is saved to the organizer’s Meet Recordings folder in My Drive.

If given or used, the average rating feedback from participants and information about live streaming appears in this section as well. Live stream views are counted anytime someone joins the meeting to watch. For example, a single user who joins and leaves multiple times has multiple views.

Note: When people connect from 3rd-party devices (interop gateways), their screen sharing feeds don't look like standard screen sharing feeds. They look like regular video feeds to other participants.

Meeting Participants View

List of meeting participants. For meetings that are in progress, details are updated during the meeting as they become available.

For large meetings, add a filter to locate specific participants. Each telephone endpoint for the same phone number is listed as a separate participant.

To view additional details, click a participant's name. The Meet quality tool captures the following information:

The participant's actions, such as turning the microphone or camera off or on
Screen sharing details, including the length of time the participant shared their screen
Network protocol changes (UDP, TCP)
The network connection type (wired, Wi-Fi, cellular connections)
If the participant was admitted after knocking, who admitted them
If the participant was ejected from the meeting, who ejected them
Audio and video transmission details
Screen sharing transmission details

Timeline View

Timeline that visualizes how the meeting developed over time.

Up to six participants are shown by default and you can sort by name or join time. Hover your mouse over the icons to view more information.

Participants section shows:

When participants joined and the devices they used.
Multiple devices are displayed if the participant joined with different devices during the meeting. For example, if they join the meeting on a computer but use a mobile device for audio.
Mute and unmute actions

Click an endpoint icon to view a more detailed timeline of a single participant's activities and the system events that occurred during a meeting. Use these to visualize the quality of the meeting as experienced by a user and troubleshoot the cause of any issues.

These timelines show:

Audio, video and network events that show how a participant’s endpoint behaved throughout a meeting. For example, when the meeting participant muted their audio or video, or changed their network type (for example, from wifi to mobile).
System metric charts that allow you to correlate system and network events with a participant’s meeting experience over time. These charts show:
- Audio energy captured—the audio energy captured by the microphone on the local client’s side.
- Audio energy played out—the audio energy played out on the local client’s speaker.
- Connection delay—round trip time (RTT) based on the STUN ping round-trip time between the local client and the nearest datacenter.
- Video packet loss sent—the packet loss for video sent from the local client to the nearest Google data center.
- Video packet loss received—the packet loss for video received by the local client sent from the nearest Google data center originating from remote clients participating in the meeting.
- CPU usage—the system CPU usage measured as averages between logged data points (typically ~10 second intervals).

Activities section shows:

Screen sharing beginning and end times
Recording beginning and ending times
Live streaming beginning and ending times

Technical Statistics View

Information on the network and system, audio and video, and any presentations (details below).

Explanations of meeting details key statistics

Network Congestion	Percentage of time when network constraints prevented a Meet client from sending higher-quality video.
Round-trip time	Length of time for a packet to travel to Google and come back.
Jitter	Variation of the network latency for packets flowing between a client and Google.
CPU Load	Average CPU load on the user’s device.
Type	Shows if a participant joined from: Meet hardware Jamboard Phone Phone used for audio with a video stream Computer Android iOS Interop gateway Unknown device
Bitrate	Amount of audio or video information received or sent, in bits per second (bps) Available bitrate over time Actual bitrate over time
Packet loss	Percentage of packets lost on the network, including packets sent and received between a client and Google.
Captured energy	Audio captured by the microphone. None—The microphone isn’t capturing audio or cannot be detected. Low—The microphone is capturing energy but it’s low, possibly due to the participant being quiet or far from the device or the microphone’s gain setting being too low. Good—Microphone is in the acceptable volume range.
Played out energy	Audio volume received and sent to the audio card. This number doesn’t reflect the peripheral selection or muted speakers. None—The received audio had no volume, which can be due to no one speaking (expected behavior) or an issue with the microphone (unexpected behavior). Low—The audio received had very low volume, which can indicate that participants were inaudible or rarely speaking. Good—The received audio was in an acceptable volume range.
Frame rate	Number of video frames per second sent or received by a client.

Give users access to the Meet quality tool

You can grant access to the Meet quality tool by creating a custom admin role and assigning it to users. This is useful when you want to let users troubleshoot meeting quality without giving them other Admin console privileges. After you assign the custom role, users can access the tool only with the direct link and not through the Admin console.

You need to be a super administrator to give users access to the Meet quality tool. For details, go to Grant access to manage Meet settings.