This feature requires having the Admin quality dashboard access privilege. If you don't have this privilege, ask your IT administrator.
What's causing your meeting issues? You can find out using the Meet quality tool (MQT). For example, you can see:
- Network statistics (jitter, packet loss, and congestion)
- Network connection delay (RTT)
- Microphone level and received audio level
- 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
|
|
To access the MQT, you must be signed in to an administrator account that has the admin quality dashboard access privilege. |
Access the tool from the Google Admin console
-
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
-
In the Admin console, go to Menu
Apps
Google Workspace
-
Click Meet quality tool.
-
(Optional) If you're already logged in, you can search for a meeting code, organizer or participant by searching from any admin page.
Give users access to the MQT
As a super administrator, you can give users access to the MQT. Do this by creating a custom admin role and assigning it to those users. Users with that role can only access the tool with the direct link and not through the Admin console.
For more details about admin roles and granting access, go to:
Filter & sort meeting data with the MQT
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
- Data for one meeting room over a period of time
- Data for a specific real world location
- Problematic meetings or devices
- Meetings that happened on a specific day
- Meetings joined by more than 50 participants
- Live stream viewers don't count as participants
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
The summary bar shows info for the view you select.
Meeting, participant, & device statistics
| Statistic | Description |
|---|---|
| Meeting code | The meeting's joining code. |
| Starting time | Time the meeting started. |
| Duration | Average meeting time. |
| Location | Location of meetings. |
| Network congestion | Percentage of time that network issues kept 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. |
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 summary |
Information about the meeting. This includes:
Live stream views are counted anytime someone joins the meeting to watch. If a single user joins and leaves multiple times, they count as multiple views. When people connect from 3rd-party devices (interop gateways), their screen sharing feeds look like regular video feeds to other participants. |
|
Meeting participants |
List of meeting participants. For meetings in progress, details are updated as they become available. For large meetings, you can add a filter to locate specific participants. Each telephone endpoint for the same phone number is listed as a separate participant. To see more details, click a participant's name. The Meet quality tool captures the following info:
|
|
Meeting timeline |
Timeline that visualizes how the meeting developed over time. You can sort participants by name or join time. Hover your mouse over the icons to view more info. The Participants section shows:
Click an endpoint icon to see a more detailed timeline of a single participant's activities and the system events that happened during a meeting. Use these to visualize the meeting quality as experienced by a user, which could help with troubleshooting. |
|
Activities |
The activities section shows start and stop times for:
|
|
Technical statistics |
Info on the network and system, audio and video, and any presentations. |
Learn about meeting details statistics
| Network congestion | Percentage of time that network issues prevented a Meet client from sending higher-quality video. |
| Connection delay | The time it takes for a packet to travel to Google and come back. |
| Jitter | Variation of the network latency for packets flowing between a client and Google. |
| Client CPU usage | Average CPU load on the user’s device. |
| Type |
Shows if a participant joined from:
|
| Bitrate |
|
| Packet loss | Percentage of packets lost on the network, including packets sent and received between a client and Google. |
| Microphone audio level | Audio captured by the microphone. |
| Received audio level | Audio volume received and sent to the audio card. This number doesn’t reflect the peripheral selection or muted speakers. |
| Frame rate | Number of video frames per second sent or received by a client. |
You can see Meet eCDN data for your meeting streams. If a meeting is recurring, each session has its own data. Data is always grouped by network name and retained according to the Workspace data retention policy. The available metrics are:
- Enablement rate: The percentage of devices that can join a P2P network based on their network settings.
- Savings rate: The percentage of traffic that viewers get from peers instead of the original media server.
- Media fallback rate: The percentage of viewers that go back to the original media server because P2P media quality or availability isn't good enough.
Admins can also get more data from APIs. For details, go to Google Meet Audit Activity Events.
