As an administrator, you can track video-meeting activity in your organization using the Google Meet audit log. For example, you can see when a user starts a meeting, where they’re joining meetings from, and who was in a meeting.
Need help during a meeting or for a specific meeting?
You can troubleshoot meetings in real time using the Meet quality tool. Go to Track meeting quality and statistics.
Open the Meet audit log
From the Admin console Home page, go to Reports.
- On the left, under Audit log, click Google Meet.
(Optional) To customize what data you see, on the right, click Manage columns . Select the columns that you want to see or hideclick Save.
(Optional) Review ways to filter and export log data and create alerts.
Data you can view
The Google Meet audit log provides the following information:
|Date||Date and time of the event (displayed in your browser's default time zone)|
|Event name||The action that was logged, such as a device (endpoint) leaving a meeting|
|Event description||Details about the action|
|Meeting code||Code for the meeting, for example, abc-hexp-tqy. Recurrent meetings have the same meeting code.|
|Participant identifier||Participant email address, phone number, or device ID. This field is empty for anonymous and external users. Participants who use a phone for audio are listed twice in the activity logs: once for their video connection and once for their phone connection.|
At Add a filter, select an Activity name to filter data for that event. The audit log shows entries for each time that event occurred during the time range that you set. Most event names are self-explanatory. However, you might see more detailed entries, such as:
|Network congestion ratio||Percentage of time that the network prevented a device from sending higher-quality video due to insufficient or unstable bandwidth, such as high or unstable jitter. Watch this metric to detect network regression in your organization.|
|Jitter||Variation of the latency on packets flowing between Google servers and a device in a video meeting. In an ideal network, packets come at a constant interval. In reality, the network introduces a variety of delays, which cause the packets to come at irregular intervals.|
|Network round trip time||Length of time it takes for a packet to travel to Google servers and come back, in milliseconds (ms)|
|Bitrate||Amount of audio or video information received or sent, in kilobits per second (KBps)|
|Estimated download bandwidth or Estimated upload bandwidth||Approximate amount of network bandwidth used to send and receive audio, video, and presentation data, in kilobits per second (KBps)|
|Abuse report submitted||Details on participants who report abusive behavior or remove a participant, including a description of the abuse. You might also see the email address or phone number of removed and reported participants.|
When and how long is data available?
Go to Data retention and lag times.
Get other Meet data
- For details on phone calls, including cost, go to the Voice audit log.
- Review events and parameters for various types of Google Meet Audit activity events using APIs in the Google Workspace Admin SDK.