As an administrator, you can use the audit and investigation page to run searches related to Meet log events. There you can review meeting activity in your organization. For example, you can find out when a user starts a meeting, where they’re joining meetings from, and who was in a meeting.
For a full list of services and activities that you can investigate, such as Google Drive or user activity, read through the data sources for the audit and investigation page.
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 audit and investigation page
- On the left, click ReportingAudit and investigationMeet log events.
Filter the data
- Open the log events as described above in Access Google Meet log event data.
- Click Add a filter, and then select an attribute.
- In the pop-up window, select an operatorselect a valueclick Apply.
(Optional) To create multiple filters for your search:
- Click Add a filter and repeat step 3.
- (Optional) To add a search operator, above Add a filter, select AND or OR.
- Click Search.
Note: Using the Filter tab, you can include simple parameter and value pairs to filter the search results. You can also use the Condition builder tab, where the filters are represented as conditions with AND/OR operators.
For this data source, you can use the following attributes when searching log event data:
|Action description||User's description when reporting abuse in a meeting|
|Action reason||User's reason when reporting abuse in a meeting|
|Action time||The actual time of an action|
|Actor||The actor's email address or phone number, or the Meet hardware's device ID, from which the actor joined the meeting|
|Actor group name||
Group name of the actor. For more information, see Filtering results by Google Group.
To add a group to your filtering groups allowlist:
|Actor identifier type||Identifier type of the user who joined the meeting, such as Email Address or Phone Number|
|Actor name||Name of the participant who joined the meeting|
|Actor organizational unit||Organizational unit of the actor|
|Calendar event ID||ID of the calendar event associated with the meeting, if it exists|
|Call rating out of 5||Rating of the Meet meeting from 1 to 5|
|City||City from which the participant joined a meeting|
|Client type||Type of the meet client, such as Android, iOS, or Web browser|
|Conference ID||ID of the conference, which is an instance of a meeting. For example, in an ongoing weekly meeting, each meeting has a unique conference ID.|
|Country||Country/region code of the country/region from which a participant joined the meeting|
|Date||Date and time of the event (displayed in your browser's default time zone)|
|Duration (seconds)||Amount of time a participant stayed in the meeting|
|Endpoint ID||Unique identifier for each participant|
|Event||The logged event action, such as Abuse report submitted or Livestreamwatched|
|IP address||IP address of the participant who joined the meeting|
|Live stream view page ID||The ID for the Meet conference live stream view page. Recurrent meetings have the same live stream view page ID|
|Meeting code||Code for the meeting. Recurrent meetings have the same meeting code.|
|Organizer email||Email address of the meeting organizer|
|Participant outside organization||Whether or not the participant is from within the organization|
|Product type||The product used to join the meeting, such as Google Meet|
|Streaming session state||The status of a streaming session (recording, broadcasting, transcription, etc.)|
|Target||Email address of the reported participant|
|Target display names||Display names of reported users|
|Target phone number||Phone number of the reported device|
|Target user count||The number of users affected by the action|
Some log event attributes described above, such as Actor, Actor Name, and Country, can help you understand who joined meetings inside and outside your organization (internal and external meetings). Depending on the participant and meeting type, information in the log event data might be:
- Shown as clear text—Displayed as unmasked, readable text.
- Obscured—Displayed with asterisks (*) to mask the information. For example, an obscured email address might include these characters: li***@s***.com.
- Not shown—Information that's not displayed in the log.
The following table shows participant identifiers available in log event data. This table also helps you understand what's available to other organizations when people from your organization join their meetings.
|Participant identifier||Available information|
Country and IP address
Email & device ID
|Name||Shown as clear text for all participants|
|Phone number||Obscured for all participants|
Note: When the participant is an anonymous user, the Actor identifier type field is blank and the Actor Name field is the name submitted by the user.
Get other Meet data
- For exact meeting times, 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.
Manage log event data
Manage search results column data
You can control which data columns appear in your search results.
- At the top-right of the search results table, click Manage columns .
- (Optional) To remove current columns, click Remove .
- (Optional) To add columns, next to Add new column, click the Down arrow and select the data column.
Repeat as needed.
- (Optional) To change the order of the columns, drag the data column names.
- Click Save.
Export search result data
- At the top of the search results table, click Export all.
- Enter a name click Export.
The export displays below the search results table under Export action results.
- To view the data, click the name of your export.
The export opens in Google Sheets.
Create reporting rules
When and how long is data available?
Go to Data retention and lag times.