Troubleshoot meeting quality

To use this feature, you must be signed in as a G Suite super admin or as an admin with the Admin quality dashboard access privilege.

Use the Meet quality tool to troubleshoot your organization’s Hangouts Meet video meetings in real time 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), or view system (CPU) statistics.

Open all  |  Close all

Use the Meet quality tool

Step 1: Open the Meet quality tool

Open the Meet quality tool using one of the following methods:

  • In the Google Admin console, go to Apps and then G Suite and then Google Hangouts and click Meet quality tool.
  • Go to
  • Go to and click View quality View quality.


Step 2: See overview information and filter data


Meetings view

Meetings view

Shows all of the meetings that were organized or joined by a user in your organization.

Participants view

Participants view 

Shows the users in your organization that joined a meeting.

Google meeting room hardware

Google meeting room hardware 

Shows the Google meeting room hardware 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 the data:

  1. Click Add a filter.
  2. From the list, select a filter.
  3. Set the filter values and click Apply.
  4. (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 participants.
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.


Step 3: Review meeting statistics and details

To review statistics about an event:

  1. On the left, click Meetings view Meetings view.
  2. From the list, click a meeting.

View Description

Meeting Information View 

Information about the meeting, such as the meeting code, duration, and organizer’s email.

If given or used, you can also see the average rating feedback from participants and information about recording and live streaming. Live stream views are counted anytime someone joins the meeting to watch. A single user can have multiple views.

Meeting Participants View 

List of meeting participants and, if given, the media-quality rating they submitted.

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.

Shows if a participant joined from:

  • Meet hardware Meet hardware
  • Jamboard Jamboard
  • Phone Phone
  • Computer Computer
  • Android Android device
  • iOS iOS device
  • Interop gateway Interop gateway
  • Other device Other device
Bitrate Amount of audio or video information received or sent, in bits per second (bps).
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.
Grant access to the Meet quality tool

You need to be a super administrator to give a user access to the Meet quality tool. You create a custom admin role with the Admin quality dashboard access privilege and then assign the role to the user.

Create a custom Admin role

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in

  2. From the Admin console Home page, go to Admin roles.

    To see Admin roles, you might have to click More controls at the bottom. 

  3. Click Create A New Role.
  4. Enter a role name and description and click Create.
  5. On the Privileges tab, go to Google Hangouts and then Settings and check the Admin quality dashboard access box.
  6. Click Save.

Assign the custom role to a user

  1. From the Admin console Home page, click Users.
  2. Click the user’s name to open their account page. If you can't find the user in the list, see Find a user account.
  3. Click Admin roles and privileges.
  4. Next to the role name you created, click Turn on Turn on.
  5. Click Save.

Related topics

Hangouts Meet audit log

Was this helpful?
How can we improve it?