Google Meet: Configuring the Experience Monitoring UCaaS Connector

Overview

Experience Monitoring provides enhanced context, such as packet loss or tunnel age, to give you the information you need to determine if the issues are related to your ISP, the Cato Cloud, or other sources.

You can also configure a connector with UCaaS applications to display application-specific metrics in the CMA to monitor the user experience when using the application.

To configure the Experience Monitoring UCaaS Connector, you need to:

Configure the integration within the SaaS application
Create the API connector in the CMA

Benefits of Connecting Google Meet

Experience Monitoring analyzes the Experience record per participant session. For each participant it reports call-quality metrics across up to six streams — Audio, Video, and Screen sharing, each in the Upstream and Downstream direction:

Latency (round-trip time)
Jitter
Packet loss
Bitrate
Frame rate (video / screen sharing)
MOS (Mean Opinion Score, computed from latency, jitter, and packet loss)

Configuring the Google Meet Integration

To configure the Google Cloud integration, create the required configurations in your Google Cloud account, then configure the connector within the CMA.

Prerequisites

A Google Workspace subscription that includes Google Meet, with the Admin SDK Reports API available
A Google Workspace Super Admin account

Step 1: Configure the Integration in the Google Cloud Console

To configure the Google Meet integration:

In your Google Cloud Console, click Select a Project.
Click New project.
Choose a Name, Organization, and Parent resource and click Create.
Navigate to APIs & Services > Library.
Search for Admin SDK.
Click on Admin SDK API and click Enable.
Navigate to IAM & Admin > Service Accounts.
Select the project you created in step two, and click Create service account.
Add a Service account ID and click Create and continue.
Click Done.
In the new service account copy and save the numeric OAuth 2.0 Client ID to be used later in the procedure.
Click on the service account you created and navigate to the Keys tab.
Click Add key > Create new key.
Choose the JSON key type and click Create.
A JSON file containing the private key is downloaded.
Copy and save the Private key so it can be added to the CMA.
In the Google Admin console, navigate to Security > Access and Data Control > API control.
Under Domain wide delegation, select Manage Domain Wide Delegation.
Click Add new.
In the Client ID field, paste the numeric OAuth 2.0 Client ID you saved above.
In the OAuth scopes field, paste the following as a single comma-separated line:
http://www.googleapis.com/auth/admin.reports.audit.readonly
Click Authorize.

Step 2: Create the API Connector in the CMA

After you have set up an integration with the required application, add the details in the CMA.

To create the API connector in the CMA:

From the navigation menu, click Resources > Integrations.
Click the Configured Integrations tab.
Click New.
The New Integration panel opens.
Select the SaaS Application you want to add.
Note: Enter the Private Key in JSON format.
In the Capability drop-down select Experience Monitoring.
Add the details , during step one:
- Service Account Key: The full contents of the JSON key file downloaded in Step 1
- Admin Email: The email of a Google Workspace admin user that the service account can impersonate when reading reports
Click Save.

The app is visible on the Integrated Apps table with a Connected status.

Known Limitations

Google Meet reports whole-session aggregates only (mean/max per call). Per-minute time series are not available. The connector expands each session's aggregate into 1-minute buckets spanning the participant's session.
Metrics Google Meet does not expose are omitted or left empty (for example internal IP, MAC address, CPU usage, Wi-Fi signal, and disconnection reason).
Streams are only reported for media that was actually used, so a call without video or screen sharing will not show those streams.