Google Meet audit log

Understand users' video-meeting activity

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

  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 Reports.
  3. On the left, under Audit, click Google Meet.
  4. (Optional) To customize what you review, on the right, click Manage columns "", select the columns that you want to see or hide, and click Save.

Data you can view

Data type Description
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.

Details on event names and descriptions

The audit report shows log entries for each time an event occurred. Most event names are self-explanatory. For example, Organizer Email shows the email address of the meeting organizer. However, you might see more detailed log data, 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.
  • Round trip time—Length of time it takes for a packet to travel to Google servers and come back.
  • Bit rate—Amount of audio or video information received or sent, in bits per second (bps).
  • Estimated download or upload bandwidth—Approximate amount of network bandwidth used to send and receive audio, video, and presentation data.

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 G Suite Admin SDK.

Related topics

Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue