Reports help you track and analyze the performance of Webex services in your organization. You can use these reports to see details for each meeting, how often users are messaging each other, details for Webex Calling calls and call queues, how often Webex devices are used, onboarding information, and more.
Reports, along with Analytics and Troubleshooting, is one part under the Monitoring section available in Control Hub that you can use to help track usage or solve issues with Webex services in your organization.

You can choose to generate a CSV formatted report immediately or to schedule reports to run automatically in a daily, weekly, or monthly format.
To generate these reports with an API, see the Reports API or Report Templates API developer page. You must be a Pro Pack customer in order to generate reports with an API.
The table below shows you what types of reports are are available for Control Hub, the earliest date range that you can view the data for each report, and the maximum date range that you can select for each report that you run.
Report | Standard License | Pro Pack License | Available Data Date Range | Standard—Date Range Limit Per Download | Pro Pack—Date Range Limit Per Download |
---|---|---|---|---|---|
Onboarding User Activation and License Details Report | ✔ | ✔ | 13 months from current date | 3 months | 13 months |
Meetings Usage Summary Report | ✔ | ✔ | 13 months from current date | 3 months | 13 months |
Meetings High CPU Report | ✔ | ✔ | 13 months from current date | 3 months | 13 months |
Meetings Active Hosts Report | ✔ | ✔ | 13 months from current date | 3 months | 13 months |
Meetings Inactive Users Report | ✔ | ✔ | 13 months from current date | 3 months | 13 months |
Meetings Active User Rolling Average Report | ✔ | ✔ | 13 months from current date | 3 months | 13 months |
Enterprise Agreement Report | ✔ | ✔ | 13 months from current date | 3 months | 13 months |
Meetings Detail Report | ✔ | 13 months from current date |
| 31 days | |
Meetings Attendees Report | ✔ | 13 months from current date |
| 31 days | |
Meetings Audio Usage Report | ✔ | 13 months from current date |
| 31 days | |
Meetings License Consumption Report* | ✔ | NA |
| NA | |
Webinar Report* | ✔ | ✔ | May 1, 2021 | 3 months | 13 months |
Messaging Bots Activity Report | ✔ | 13 months from current date |
| 31 days | |
Messaging User Activity Report | ✔ | 13 months from current date |
| 31 days | |
Messaging Bots Activity Summary Report | ✔ | 13 months from current date |
| 31 days | |
Messaging User Activity Summary Report | ✔ | 13 months from current date |
| 31 days | |
Messaging App Version Report | ✔ | 13 months from current date |
| NA | |
Meetings Future Schedules Report | ✔ | NA |
| 90 days | |
Calling Engagement Report | ✔ | ✔ | 13 months from current date | 3 months | 31 days |
Calling Quality Report | ✔ | ✔ | 13 months from current date | 3 months | 31 days |
Rooms and Desks Detail Report* | ✔ | ✔ | 13 months from current date | 3 months | 13 months |
VIMT License Report* | ✔ | ✔ | 13 months from current date | 3 months | 13 months |
VIMT Usage Report* | ✔ | ✔ | 13 months from current date | 3 months | 13 months |
Report templates
This tab shows a list of fixed templates that you can use to schedule reports, along with a brief description for each report.
To view more information about these reports, you can expand the following sections:
Data availability
Data is captured based on the UTC time zone. It takes approximately eight hours for the last-day data to show up for the following day, which is around 8:00 UTC. Different time zones may affect when certain reports are updated with new data.
For example, if you generate a report for the same day, the report may only include partial data. If you include the previous day and the same day in the time range, then the report may also include partial data, depending on your time zone.
We recommend that you generate same-day reports in your time zone's afternoon and include the previous day along with the same day if you find that your reports don't have all of the previous day's data.
Meetings Details
Provides information about meetings that were started within the selected date range. You can see who hosted the meeting, when the meeting started and ended, how many participants attended the meeting, if the meeting was recorded, and more.
Column Name | Description | ||
---|---|---|---|
MEETING_NUMBER | The 9-digit meeting access code used to join the meeting. | ||
MEETING_NAME | The subject of the meeting. | ||
CONFERENCE_ID | The unique ID of the meeting. | ||
MEETING_TYPE | The type of meeting that took place. The possible values are:
| ||
HOST_NAME | The name of the user who created or scheduled the meeting. | ||
HOST_USERID | The unique ID of the host. | ||
HOSTEMAIL | The email address of the host. | ||
START_TIME | When the meeting started (GMT). | ||
END_TIME | When the meeting ended (GMT). | ||
DURATION | The length of the meeting in minutes. | ||
TOTAL_ATTENDEE | The number of participants in the meeting. | ||
PEOPLE_MINS | The total number in minutes that all participants have been in the meeting. For example, if a meeting had 3 participants and they each joined for 10 minutes, then the total equals to 3 participants x 10 minutes each = 30 minutes. | ||
IS_VOIP | At least one participant called into the meeting using audio connection through a computer. | ||
IS_SHARING | At least one participant shared their screen in the meeting. | ||
IS_RECORD | If the meeting was recorded or not. | ||
VIDEO_USERS | The number of participants who joined with a Webex Meetings client and turned on their video during the meeting. | ||
VIDEO_MINS | The total number in minutes that participants were sending video. | ||
AUDIO_ONLY (PCN) | A meeting where all participants called in using PSTN. | ||
TRACKING_CODE_1-10 | The tracking code associated with a user.
| ||
INTEGRATION_USED | This field shows if a meeting was scheduled through the Microsoft Teams, Microsoft Outlook, Slack, or Google Calendar integration with the Cisco Webex Meetings app. | ||
WEBEX_ASSISTANT | This field shows if the Webex Assistant for Meetings was used in the meeting. The possible values are:
| ||
BREAKOUT_USED | This field shows if a breakout session was started during the meeting. The possible values are:
| ||
IS_E2EE | This field shows if the meeting was scheduled using end-to-end encryption (E2EE). The possible values are:
| ||
SI_USED | This field shows if a meeting had simultaneous interpretation enabled by the host. The possible values are:
| ||
Meetings Attendees
Provides information about every participant who attended a meeting within the selected date range. You can find out about a participant’s media quality data during the meeting and information about how they joined the meeting.
Media quality data and hardware information of participants are only available if the meeting's duration was more than two minutes. |
Column Name | Description | ||
---|---|---|---|
MEETING_NUMBER | The 9-digit meeting access code used to join the meeting. | ||
MEETING_NAME | The subject of the meeting. | ||
CONFERENCE_ID | The unique ID of the meeting. | ||
USER_NAME | The names of the participants who attended the meeting. | ||
| The email addresses of the participants who attended the meeting. | ||
LOCATION | The country of where the participants joined the meeting from. | ||
JOIN_DATE | The date of the meeting (GMT). | ||
START_TIME | The times that the participants joined the meeting (GMT). | ||
END_TIME | The times that the participants left the meeting (GMT). | ||
DURATION | How long the participant joined the meeting for in minutes. | ||
OS | The operating systems of the devices the participants used to join the meeting. | ||
BROWSER | The web browsers that participants used for the Webex Meetings for Web to join the meeting. | ||
LOCAL_IP | The IP addresses of the clients used to join the meeting. These IP addresses may not be externally routable addresses if they're behind a firewall. | ||
PUBLIC_IP | The IP addresses of the client that's externally routable. This can be the same as | ||
VOIP_RECEIVING_AVERAGE_PACKET_LOSS | The average audio packet loss for the duration of the meeting from the Webex cloud to the client direction, in percentage.
| ||
VOIP_AVERAGE_LATENCY | The average audio latency for the duration of the meeting, in milliseconds. | ||
JOIN_MEETING_TIME | JMT = (the time from clicking the meeting link to loading the preview window) + (the time from clicking the Join button in the preview window to connecting into the meeting). JMT doesn’t count the time the user spends browsing menus, making selections in the preview window, or waiting in the lobby. | ||
TCP_PERCENTAGE | The percentage of the duration participants used TCP connection for a VoIP call. | ||
UDP_PERCENTAGE | The percentage of the duration participants used UDP connection for a VoIP call. | ||
IS_CMR | If the attendee joined the meeting using a Webex Room or Desk Device, | ||
IS_SHARING | Whether or not the participant shared their screen during the meeting. | ||
IS_RECORD | Whether or not the participant clicked the Record button. | ||
VIDEO_MINUTES | The total number of minutes that video was enabled by the participant in the meeting. | ||
CLIENT | The type of soft client used to join the meeting. | ||
CLIENT_VERSION | The version of the soft client used to join the meeting. | ||
MEDIA_NODE | The data center or region of the media node that the client connected to. For cloud-based media nodes, this is a general region name such as "San Jose, USA". For video mesh based media nodes, this will have a more specific name that matches the video mesh cluster name that was provisioned by the customer. | ||
CONNECTION | The type of network connection that the client used to exchange media. Possible values could be "wifi", "ethernet", "cellular", or "unknown".
| ||
HARDWARE | The hardware make and model of the device used to join a meeting. For computers this might be "Lenovo Thinkpad p60". For phones this might be "Samsung Galaxy S7". For room devices this might be "Cisco Webex Room Kit". | ||
CAMERA | The brand name and model information for the camera that was used during the meeting.
| ||
MICROPHONE | The brand name and model information for the microphone that was used during the meeting.
| ||
SPEAKER | The brand name and model information for the speaker that was used during the meeting.
| ||
AUDIO_AVERAGE_LATENCY | The average audio latency for the duration of the meeting, in milliseconds. | ||
AUDIO_MAX_LATENCY | The highest value of audio latency for the duration of the meeting, in milliseconds. | ||
AUDIO_RECEIVING_AVERAGE_PACKET_LOSS | The average end-to-end audio packet loss for the duration of the meeting, in percentage. | ||
AUDIO_RECEIVING_MAX_PACKET_LOSS | The highest value of end-to-end audio packet loss for the duration of the meeting, in percentage. | ||
AUDIO_SENDING_AVERAGE_PACKET_LOSS | The average audio packet loss for the duration of the meeting, in percentage. | ||
AUDIO_SENDING_MAX_PACKET_LOSS | The highest value of audio packet loss for the duration of the meeting, in percentage. | ||
AUDIO_RECEIVING_AVERAGE_JITTER | The average audio jitter for the duration of the meeting, in milliseconds. | ||
AUDIO_RECEIVING_MAX_JITTER | The highest value of audio jitter for the duration of the meeting, in milliseconds. | ||
AUDIO_SENDING_AVERAGE_JITTER | The average audio jitter for the duration of the meeting, in milliseconds. | ||
AUDIO_SENDING_MAX_JITTER | The highest value of audio jitter for the duration of the meeting, in milliseconds. | ||
VIDEO_AVERAGE_LATENCY | The average video latency for the duration of the meeting, in milliseconds. | ||
VIDEO_MAX_LATENCY | The highest value of video latency for the duration of the meeting, in milliseconds. | ||
VIDEO_RECEIVING_AVERAGE_PACKET_LOSS | The average video packet loss for the duration of the meeting, in percentage. | ||
VIDEO_RECEIVING_MAX_PACKET_LOSS | The highest value of video packet loss for the duration of the meeting, in percentage. | ||
VIDEO_SENDING_AVERAGE_PACKET_LOSS | The average video packet loss for the duration of the meeting, in percentage. | ||
VIDEO_SENDING_MAX_PACKET_LOSS | The highest value of video packet loss for the duration of the meeting, in percentage. | ||
VIDEO_RECEIVING_AVERAGE_JITTER | The average video jitter for the duration of the meeting, in milliseconds. | ||
VIDEO_RECEIVING_MAX_JITTER | The highest value of video jitter for the duration of the meeting, in milliseconds. | ||
VIDEO_SENDING_AVERAGE_JITTER | The average video jitter for the duration of the call, in milliseconds. | ||
VIDEO_SENDING_MAX_JITTER | The highest value of video jitter for the duration of the meeting, in milliseconds. | ||
CPU_APPLICATION_AVERAGE | The average CPU usage for the Webex app for the duration of the meeting, in percentage. | ||
CPU_APPLICATION_MAX | The highest CPU usage value for the Webex app for the duration of the meeting, in percentage. | ||
CPU_SYSTEM_AVERAGE | The average system CPU usage for the duration of the meeting, in percentage. | ||
CPU_SYSTEM_MAX | The highest system CPU usage value for the duration of the meeting, in percentage. | ||
VIRTUAL_BACKGROUND_USED | This field shows if participants enabled a virtual background during the meeting. The possible values are:
| ||
HOST_INDICATOR | This field shows if the participant was a host or attendee. The possible values are:
| ||
Meetings Usage Summary
Provides information about the total number of meetings hosted within the selected date range.
Column Name | Description |
---|---|
Number Of Meetings | The total number of meetings hosted over the selected time period. |
Total Meeting Minutes | The total number of minutes for all meetings over the selected time period. For example, if three meetings lasted 30 minutes each, then the count is 90 meeting minutes. |
Number Of Participants | The total number of joins by participants or devices from all Webex meetings over the selected time period. For example, if a participant or device disconnected from a meeting and then rejoined, then the count is 2. |
Total Participant Minutes | The total number of minutes that all participants were in a meeting for. For example, if a meeting has 3 participants and lasts for 10 minutes, then the count is 30 participant minutes (3 x 10 minutes). |
Participant Sending Video Minutes | The total number of minutes that participants enabled video for. For example, in a meeting that lasts 30 minutes with five participants, but only two participants enabled video for the entire meeting, the count is 60 video minutes. |
Participant VOIP Minutes | Total number of minutes for participants who joined meetings using VoIP. |
Participant Audio Minutes | Total number of minutes for participants who called in to meetings using PSTN. |
Meetings Active Hosts
Provides information about how many meetings a host scheduled and started within the selected date range.
Column Name | Description |
---|---|
UserID | The host's email address. |
Count of meetings hosted | The number of meetings scheduled and hosted by this attendee within the reported time period. |
Meetings Inactive Users
Provides information about users who haven’t hosted or attended meetings within the selected date range.
Column Name | Description |
---|---|
FIRST_NAME | The first name of the user. |
LAST_NAME | The last name of the user. |
USERNAME | The email address of the user. |
USER_ID | The unique ID of the user. |
| The email address of the user. |
IS_HOST | Whether or not the user has a Webex Meetings host license. |
IS_SITEADMIN | Whether or not the user has an administrator role for the Webex site. |
DAYS_SINCE_LAST_ACTIVE | The number of days since the user last hosted or attended a meeting through the Webex App app or Webex Meetings. |
LAST_ACTIVE_DATE | The date of when the user last hosted or attended a meeting through the Webex App app or Webex Meetings. PSTN call-in users don’t count as active. |
Meetings Audio Usage
Provides information about the different types of audio that participants used during a meeting.
Column Name | Description | ||
---|---|---|---|
CONF ID | The unique ID of the meeting. | ||
MEETING NUMBER | The 9-digit meeting access code used to join the meeting. | ||
AUDIO TYPE | The audio type that participants used to join a meeting. The audio types are:
| ||
USER NAME | The names of the participants who attended the meeting. | ||
| The email addresses of the participants who attended the meeting. | ||
PHONE NUMBER | The phone number for participants who joined a meeting through CCA, PSTN, VoIP, Edge Audio, or Fallback.
| ||
MEETING ENDDATE | The date of when the meeting ended. | ||
START TIME | When the meeting started (GMT). | ||
END TIME | When the meeting ended (GMT). | ||
AUDIO MINUTES | The total number of audio minutes used by each participant. | ||
MEETING NAME | The subject of the meeting. | ||
Meetings Telephony Report
Provides information about the different types of telephony audio that participants used during a meeting. You can use this chart to get a sense of which calling services that participants prefer to connect to for meetings and calls.
Column Name | Description |
---|---|
MEETING_NUMBER | 9- or 10-digit meeting access code used to join the meeting. |
CONFERENCE_ID | Unique ID of the meeting. |
SESSION_TYPE | Audio type (in numerical value) that participants used to join a meeting. Possible audio types are:
|
MEETING_NAME | Subject of the meeting. |
MEETING_START_DATE_TIME | Date and time (in GMT) of when the meeting started. |
MEETING_END_DATE_TIME | Date and time (in GMT) of when the meeting ended. |
MEETING_DURATION | Duration (in GMT) of how long the meeting lasted. |
USER_NAME | Display names of the participants who attended the meeting. |
| Email addresses of the participants who attended the meeting. |
CALL_SERVICE_TYPE | Call service type that participants used to join a meeting. Possible call service types are:
|
DIALED_IN_PHONE_NUMBER | Phone number that participants used to dial in to the meeting. |
CALLBACK_PHONE_NUMBER | Phone number that participants requested to join a meeting through callback. |
PARTICIPANT_START_DATE_TIME | Date and time (in GMT) of when the participant connected their audio in the meeting. |
PARTICIPANTS_DURATION | Duration (in GMT) of how long the participant's audio was connected for in the meeting. |
ANI | Automatic number identification of the phone number that the participant used to call in to the meeting. |
Meetings Future Schedules
This report doesn't have a date range selection. You can see the meetings that are coming up for a Webex site within the next 90 days from the date that you run the report. You can also see meetings that were scheduled within the previous 30 days.
This report shows you the upcoming meetings for the selected Webex site. Use this report to gain insights into how many users are scheduling meetings in a Webex site and understand the volume and timing of upcoming meetings. This information can help you manage the timing of a site migration or a site upgrade that might impact users. You can also identify critical meetings or events to help plan support accordingly.
Meetings scheduled from Webex are included in this report. If hosts are scheduling meetings with a Personal Room invitation URL, then those meetings won’t be included in the report. |
Column Name | Description |
---|---|
MeetingNumber | The 9-digit meeting access code used to join the meeting. |
ServiceType | If the meeting was scheduled as a Webex Meeting, Webex Event, or Webex Training session. |
HostName | The name of the user who scheduled the meeting. |
| The email address of the user who scheduled the meeting. |
MeetingName | The subject of the meeting. |
StartTime | The date and time of when the meeting will start (GMT). |
EndTime | The date and time of when the meeting will end (GMT). |
CreatedOn | The date and time of when the meeting was scheduled (GMT). |
InviteeCount | The number of users invited to the meeting. |
PasswordSet | If the meeting requires a password to join. |
SeriesType | If the meeting is a one-time meeting or a recurring series. |
ExpirationDate | The date and time of when the meeting series will end (GMT). |
LastModifiedDate | The date and time of when the meeting invitation was last updated (GMT). |
ExceptionMeeting | If one of the meetings in a series was rescheduled for a different time. |
Meetings High CPU
This report shows you which users had an average system CPU usage of 90% or higher for at least 25% of their video minutes during meetings. To optimize resources, Webex downgrades the bit rate and resolution of all videos when the user reaches an average system CPU usage of 95% for five consecutive seconds.
You can use this report to help users on how they can reduce their system CPU usage to have a better meeting experience.
Column Name | Description |
---|---|
User Email | The email address of the user who had high system CPU usage. |
Total Video Minutes | The number of recorded video minutes for each user’s email address during the selected date range. |
Video Minutes with High CPU Utilization | The number of recorded video minutes where the average system CPU usage was at 90% or higher. |
% Video Minutes with High CPU | The percentage of video minutes where the average system CPU usage was at 90% or higher. |
Meetings Active User Rolling Average
Provides information about how many licenses are being used in a subscription, and how many users have hosted at least one Webex meeting within the reported date. This report is only available if your organization has an active true forward eligible subscription.
Column Name | Description | ||
---|---|---|---|
Date | The calendar date within the period.
| ||
Subscription ID | The unique ID of the subscription. | ||
Product | The name of the product for the reported licenses. | ||
Provisioned License Quantity | The total number of licenses provisioned for the subscription and product. | ||
Allocated License Quantity | The number of licenses allocated to users at the reported date. | ||
Unique Active Hosts Per Day | The count of unique active hosts on the calendar date. Unique active hosts are hosts who started at least one Webex meeting on the reported date. | ||
Unique Active Meeting Hosts for Past 30 days | The cumulative number of unique active hosts for the last 30 days, including the current day. Unique active hosts are hosts who started at least one Webex meeting on the reported date. | ||
90 Day Rolling Average Unique Active Meetings Hosts | The average number of unique active hosts for the preceding 90 days of the reported date, rounded to the nearest whole number. If you have less than 90 days in your subscription, then the average is based on the number of days the subscription has been active for. | ||
Consumption Quantity | This number reflects the aligned value used to identity a True Forward. IT admins can track this value throughout the contract term, well before the period in which the subscription is due for a potential change.
| ||
Meetings License Consumption Report
Provides information about how many licenses are being used in a subscription. This report is only available if your organization has an active utility-based billing subscription.
This report isn't available in Webex for Government organizations. |
Column Name | Description |
---|---|
Date | The period that the subscription is in. A period is defined as a 30-day cycle that starts on the day your subscription was activated, and corresponds with your billing cycle. For example, if your subscription started on July 5, 2020, then the next period would start 30 days later, on August 4, 2020. |
Subscription ID | The unique ID of the subscription. |
Product | The name of the product for the reported licenses. |
Provisioned License Quantity | The total number of licenses provisioned for the subscription and product. |
Allocated License Quantity | The number of licenses allocated to users at the reported date. |
Webinar Report
Provides information about Webex webinars that were hosted within the selected date range. You can use this report to find out who the host for an webinar was, what type of webinar was scheduled, and how many users registered or attended.
Column Name | Description |
---|---|
Meeting ID | The unique ID of the webinar. |
Host ID | The unique ID of the host. |
Webinar Topic | The subject of the webinar. |
Webinar Type | If it was scheduled as a Webinar or Webcast. |
Host Email | The email address of the host. |
Host First Name | The first name of the host. |
Host Last Name | The last name of the host. |
Event Date | The date of when the webinar started. |
Start Time | The time of when the webinar started (GMT). |
End Time | The time of when the webinar ended (GMT). |
Duration | The number of minutes that the webinar lasted for. |
Total Registrants | The number of users that registered for the webinar before it started. |
Total Attendees | The number of users that joined the webinar. |
Messaging Bots Activity
This report shows data for every activity of each bot per day during the date range that you select. Each date that you select has their own set of data. For example, if you run a report for June 1, 2020 to June 5, 2020, then the report shows you every activity of the bot for each date of the report.
If a bot hasn't had any activity during a certain date, then those dates don't show up in the report.
Data for this report is only for bots from your organization. If your organization uses bots that aren't part of your organization, then data won't show for those bots. |
Column Name | Description |
---|---|
Bot Name | The name of the bot. |
Bot ID | The unique ID of the bot. |
Date | The date for the activity of the bot. |
Active Spaces Count | The number of spaces that the bot has sent a message or shared a file in. |
Messages Count | The number of messages sent by the bot. |
Files Shared | The number of files shared by the bot. |
New Spaces Joined | The number of spaces the bot joined. |
Spaces Exited | The number of spaces the bot left. |
Bot User Count | The number of unique users that mentioned the bot. |
Bot Mentions Count | The number of how many times the bot was mentioned by users. |
Messaging User Activity
This report shows data for every activity of each user per day during the date range that you select. Each date that you select has their own set of data. For example, if you run a report for June 1, 2020 to June 5, 2020, then the report shows you every activity of the user for each date of the report.
If a user hasn't had any activity during a certain date, then those dates don't show up in the report.
Column Name | Description |
---|---|
User ID | The unique ID of the user. |
Name | The first and last name of the user. |
| The email address of the user. |
Date | The date for the activity of the user. |
Messages Sent | The number of messages sent by the user. |
Calls | The number of calls made and meetings joined from the Webex App client by a user. |
Files Shared | The number of files shared in all spaces by the user. |
Spaces Count | The number of spaces that the user has sent a message, made a call, or shared a file in. |
New Spaces Created | The number of spaces the user created. |
New Spaces Joined | The number of spaces the user joined. |
Space Exited | The number of spaces the user left. |
Messaging Bots Activity Summary
This report shows aggregated data for each activity of each bot during the date range that you select.
Data for this report is only for bots from your organization. If your organization uses bots that aren't part of your organization, then data won't show for those bots. |
Column Name | Description |
---|---|
Bot Name | The name of the bot. |
Bot ID | The unique ID of the bot. |
Bot Owner | The name of the user who created the bot. |
Bot Owner Email | The email address of the user who created the bot. |
Start Date | The first date selected for the report date range. |
End Date | The last date selected for the report date range. |
Average Active Spaces Count | The average number of spaces that the bot has sent a message or shared a file in. |
Messages Count | The number of messages sent by the bot. |
Files Shared | The number of files shared by the bot. |
Spaces Joined | The number of spaces the bot joined. |
Spaces Exited | The number of spaces the bot left. |
Average Bot User Count | The average number of unique users that mentioned the bot. |
Bot Mentions Count | The number of how many times the bot was mentioned by users. |
Messaging User Activity Summary
This report shows aggregated data for each activity of each user during the date range that you select.
Column Name | Description |
---|---|
User ID | The unique ID of the user. |
Name | The first and last name of the user. |
| The email address of the user. |
Start Date | The first date selected for the report date range. |
End Date | The last date selected for the report date range. |
Messages Sent | The number of messages sent by the user. |
Calls | The number of calls made and meetings joined from the Webex App client by a user. |
Files Shared | The number of files shared in all spaces by the user. |
New Spaces Created | The number of spaces the user created. |
Spaces Joined | The number of spaces the user joined. |
Space Exited | The number of spaces the user left. |
Messaging App Version
This report doesn't have a date range or Webex site selection since it shows you data from all Webex sites in your organization and the last known date of when a user sent a message. For example, if a user sent a message on March 1, 2020 and hasn't sent any other messages since then, the report shows the Webex App client version used on that date.
The report shows data on all platforms that a user signed in to Webex App on. For example, if a user signed in to Webex App on the Windows and Mac client, that user will have two separate entries in the report.
Column Name | Description |
---|---|
Version | The latest detected version of the Webex App client. |
Platform | The operating system for the Webex App client. |
User_ID | The unique ID of the user. |
| The email address of the user that signed in to the Webex App client. |
Name | The first and last name of the user. |
Last Known Date | The date of when the Webex App platform and version number was last detected for a user during the last message sent. For example, if a user didn’t send a message after a Webex App version update, then the report shows the Webex App client version used on that date. |
Calling Engagement Report
This report shows data for the call legs that users made or received with the Webex app using Call on Webex and the Webex Calling app.
Column Name | Description |
---|---|
Name | The first and last name of the user. |
| The email address of the user. |
Start Time | The time (GMT) of when the call was made. |
Duration | The amount of time in seconds that the call lasted. |
Video Duration | The amount of time in seconds that the user turned on their video. |
Endpoint | The device or app that the user made or received the call with. |
Call ID | The unique ID of the call. |
Caller | This field shows if the user was the one who initiated the call. The possible values are:
|
Calling Quality Report
This report shows data for the quality of calls made or received by users with the Webex Calling and Webex desktop apps.
The quality of calls made or received from the Webex app and cloud-registered devices aren't captured in this report. |
Column Name | Description |
---|---|
Name | The first and last name of the user. |
| The email address of the user. |
Start Time | The time (GMT) of when the call was made. |
Duration | The amount of time in minutes that the call lasted. |
Endpoint | The device or app that the user made or received the call with. |
Audio Packet Loss | The average receiving audio packet loss in percentage. |
Audio Latency | The average audio round-trip delay in milliseconds. |
Audio Jitter | The average jitter in milliseconds. |
Video Packet Loss | The average receiving video packet loss in percentage. |
Video Latency | The average video round-trip delay in milliseconds. |
UA Version | The Webex Calling or Webex desktop app version of the user. |
Call ID | The unique ID of the call. |
Calling Detailed Call History Report
This report shows detailed call history data. This information can be used to view trends at a high level or drill down to specific call types, which can be used to understand calling behavior.
Column Name | Description |
---|---|
Start time | This is the start time of the call, the answer time may be slightly after this. Time is in UTC. |
Answer time | The time the call was answered. Time is in UTC. |
Duration | The length of the call in seconds. |
Calling number | For incoming calls, it's the telephone number of the calling party. For outgoing calls, it's the telephone number of the user. |
Called number | For incoming calls, it's the telephone number of the user. For outgoing calls, it's the telephone number of the called party. |
User | The user who made or received the call. |
Calling line ID | For incoming calls, it's the calling line ID of the calling party. For outgoing calls, it's the calling line ID of the user. |
Called line ID | For incoming calls, it's the calling line ID of the user. For outgoing calls, it's the calling line ID of the called party. |
Correlation ID | Correlation ID to tie together multiple call legs of the same call session. |
Location | The Webex Calling location of the user for this record. |
Inbound trunk | Inbound trunk may be presented in Originating and Terminating records.
|
Outbound trunk | Outbound trunk may be presented in Originating and Terminating records.
|
Route group | If present, this field's only reported in Originating records. Route group identifies the route group used for outbound calls routed via a route group to Premises-based PSTN or an on-prem deployment integrated with Webex Calling (dial plan or unknown extension). |
Client Version | The version of the client that the user (of this CDR) is using to make or receive the call. |
Sub client type | If the call is TO or FROM a mobile phone using Webex Go, the |
Direction | Whether the call was inbound or outbound. The possible values are:
|
Call type | Type of call. For example:
|
Client type | The type of client that the user (creating this record) is using to make or receive the call. For example:
|
Client Version | The version of the client that the user (creating this record) is using to make or receive the call. |
Sub client type | If the call is TO or FROM a mobile phone using Webex Go, the |
OS type | The operating system that the app was running on, if available. |
Device Mac | The MAC address of the device, if known. |
Answered | Whether the call leg was answered or not. For example, in a hunt group case, some legs will be unanswered, one will be answered. Calls answered by voicemail will show |
International country | The country of the dialed number. This is only populated for international calls. |
Original reason | Populated for calls that transfer, hold, wait, and so on. For example:
|
Related reason | Populated for calls that transfer, hold, wait, and so on. For example:
|
Redirect reason | Populated for calls that transfer, hold, wait, and so on. For example:
|
Site main number | The main number for the user's site where the call was made or received. |
Site timezone | Site timezone is the offset in minutes from UTC time of the user's timezone. |
User type | The type of user (user or workspace) that made or received the call. For example:
|
Call ID | SIP Call ID used to identify the call. You can share the Call ID with Cisco TAC to help them pinpoint a call if necessary. |
User UUID | A unique identifier for the user associated with the call. This is a unique identifier across Cisco products. |
Org UUID | A unique identifier for the organization that made the call. This is a unique identifier across Cisco. |
Report ID | A unique ID for this particular record. This can be used when processing records to aid in deduplication. |
Example record analysis: point-to-point call
If this is a Webex Calling device to Webex Calling device call:
- Alice calls Bob.
- Bob answers the call.
- Either party ends the call.
Two records are created:
- Alice creates an
Originating record
withCalled line ID
= Bob. - Bob creates a
Terminating record
withCalling line ID
= Alice
If this is a PSTN to Webex Calling device call:
- Alice calls Bob.
- Bob answers the call.
- Either party ends the call.
One record is created:
- No
Originating record
is created because no Webex Calling device originated the call. - Bob creates a
Terminating record
withCalling line ID
= Alice
Example record analysis: Blind Transfer
Blind or unattended transfer allows you to transfer calls to an alternate extension or phone number without waiting for an answer or confirming the availability of the receiving party.
Here's how a blind transfer is represented in a detailed call record report.
An example for a Blind Transfer:- Alice calls Bob.
- Bob places Alice on hold.
- Bob blind transfers the call to Charlie.
- Bob clears down.
- Charlie answers the call.
- Alice ends the call.
Four records are created from this blind transfer:
- Alice creates an
Originating CDR
withCalled line ID
= Bob. - Bob creates a
Terminating CDR
withCalling line ID
= Alice. - Bob creates an
Originating CDR
withCalled line ID
= Charlie andRedirect reason
= Deflection. - Charlie creates a
Terminating CDR
withCalling line ID
= Alice andRedirect reason
= Deflection.
Call Timeline:
- Alice takes about 20 seconds to call Bob.
- Bob places Alice on Hold and blind transfers the call to Charlie which takes about 3 seconds before Charlie answers the transferred call.
- Bob clears down and Alice ends the call with Charlie which takes about 23 seconds.
Based on the preceding case, the overall call length is about 46 seconds. For reference, the following spreadsheet captures the Blind Transfer Call Details.

Some records report special functionality. For example, records tagged with |
Rooms and Desks Detail
Use this report to see details of every device in your organization and what they're being used for. Look at the Total Hours Used column to quickly pinpoint underutilized devices. It shows the total usage of the device over the selected date range.
Column Name | Description |
---|---|
Device ID | Unique identifier internal for administrators. |
Device Type | Device model. |
Assigned To | Name of the place or user this device is assigned to. If this field is blank, then the device was deleted from your organization. |
Tags | Shows tags assigned to the device on the Control Hub Devices page. |
IP Address | Last known IP address of when the device was online. |
Mac Address | Media Access Control address of the device. |
Latest Known Status | Device online status from the last 24 hours. |
Total Hours Used | Total usage over the selected date range |
Calls | The number of hours the device was used for a call. |
Local Display Wired | The number of hours the device was used for a wired local display. |
Local Display Wireless | The number of hours the device was used for a wireless local display. |
Whiteboarding | The number of hours the device was used for whiteboarding. |
Digital Signage | The number of hours the device was used for whiteboarding. |
USB Passthrough | The number of hours the device was used for USB passthrough. |
VIMT License Report
This report shows you license usage for unique active Webex devices and third-party SIP devices that use the Video Integration for Microsoft Teams (VIMT) in your organization. Each date that you select has their own set of data. For example, if you run a report for June 1, 2020 to June 5, 2020, then the report shows you data for each date of the report.
For some organizations based in Europe and Africa, this report may return empty fields. This is a known limitation. |
Column Name | Description |
---|---|
Webex Org ID | The unique ID of the Control Hub organization that the report belongs to. |
Date | The calendar date for the recorded data. There is one record per day. |
Device 24 hours | The count of unique devices that used VIMT in the last 24 hours of the date. |
Device last 30 days | The rolling count of unique devices that used VIMT in the last 30 days of the date. |
Unique Devices Rolling 90 day average | The rolling average count of unique devices that used VIMT in the last 90 days of the date. |
VIMT Usage Report
This report provides details about calls where Webex devices and third-party SIP devices used Video Integration for Microsoft Teams (VIMT) to join Microsoft Teams meetings.
For some organizations based in Europe and Africa, this report may return empty fields. This is a known limitation. |
Column Name | Description |
---|---|
Teams Conference ID | The unique ID of the Microsoft Teams meeting. |
Device Name | The name of the device used to join the Microsoft Teams meeting. |
Device URL | The URL associated with the Webex device. |
Device Join Time | The time when the device joined the Microsoft Teams meeting using VIMT. |
Device Disconnect Time | The time when the device disconnected from the Microsoft Teams meeting. |
Device SIP URI | The Session Initiation Protocol (SIP) address associated with the device. |
Teams Tenant ID | The unique ID of the user in the Microsoft Teams client. |
Date device joined call | The date that the device was used to join the Microsoft Teams meeting using VIMT. |
Onboarding User Activation and License Details Report
This report shows details about how users were added to your organization and how licenses were assigned to them.
This report isn't available in Webex for Government organizations. |
Column Name | Description |
---|---|
Name | The first and last name of the added user. |
| The email address of the user. |
Administrator Name | The first and last name of the administrator who added the user, if applicable. |
Administrator Email | The email address of the administrator who added the user, if applicable. |
Invite Sent (GMT) | The date and time an invitation was sent to the user, if applicable. |
Onboard Method | The method used to add the user to Control Hub. |
License Assign Method | The method used to assign the user the license. The methods are:
|
Licenses | The names of licenses assigned to the user. |
License Assign Status | If the licenses were assigned to the user successfully or unsuccessfully. |
Activation Status | The user’s activation status is shown as Activated if the user signs in to the Webex App for the first time. Users that haven't signed in to the Webex App show as Pending. |
Activation Date | The date of when the user’s status changed to Active. |
User ID | The unique ID of the user. |
Administrator ID | The unique ID of the administrator who added the user. |
Enterprise Agreement Report
Provides information about how many licenses are being used in a subscription. This report is only available if your organization has an active true forward eligible subscription.
Column Name | Description | ||
---|---|---|---|
Period | The period that the subscription is in. A period is defined as a 30-day cycle that starts on the day your subscription was activated, and corresponds with your billing cycle. For example, if your subscription started on July 5, 2020, then the next period would start 30 days later, on August 4, 2020. | ||
Date | The calendar date within the period. | ||
Subscription ID | The unique ID of the subscription. | ||
Product | The name of the product for the reported licenses. | ||
Provisioned License Quantity | The total number of licenses provisioned for the subscription and product. | ||
Allocated License Quantity | The number of licenses allocated to users at the reported date. | ||
Consumption Quantity | This number reflects the aligned value used to identity a True Forward. IT admins can track this value throughout the contract term, well before the period in which the subscription is due for a potential change.
| ||
Report list
This tab shows a list of reports that are ready for you to download. If you choose to subscribe to a report when scheduling one, then you'll also get an email that notifies you when the report is ready for you to download.
When the report is generating, the status column changes to “In Progress”. When the report is ready to download, the status column changes to “Complete”. Depending on the number of columns and the date range selected for a report, it may take up to 5 to 60 minutes to generate the report.
You can only have a maximum of 50 reports in this list. Once you reach that limit, delete some reports to generate new reports again. |

Scheduled reports
This tab shows a list of reports that are set up to run recurringly. You can see the recurring details for each report and when they were last generated.

You can customize existing templates by reordering or removing columns to view the data that you want to focus on. For example, you can create customized Meetings Attendees reports that focus on participants in specific locations or on specific operating systems, or customized Calling Quality reports that focus on audio or video media quality instead of both. Custom templates are tagged so you can easily identify them.

Some templates aren't available for customization, and some columns are required for certain templates. You can tell which columns are required by a template if you can't remove them when you're customizing a template, as shown in the following image.

Each administrator can create up to 50 custom templates, and only you can view the custom templates that you created. |
You can create up to 50 custom templates and only you can view your custom templates. Other administrators can create their own set of up to 50 custom templates.
Custom templates aren't editable after they're created. |
1 | From the customer view in https://admin.webex.com, go to Reports. |
2 | Click New template. A full-screen window appears. To exit this window, you can click Cancel or finish creating the custom template. ![]() |
3 | In the Template section, select which template you want to customize, enter the name for the custom template, and add a description. |
4 | In the Data section, you can choose to:
|
5 | Click Save template. |
When you delete a custom template, any automatic schedules for that template will also be deleted. You'll still keep any previously generated report of that custom template.
1 | From the customer view in https://admin.webex.com, go to Reports. |
2 | Click the More button next to the custom template you want to delete. |
3 | Select Delete and then confirm your choice. |
1 | From the customer view in https://admin.webex.com, go to and click Generate Report.
![]() | ||
2 | Select which report you want to generate next to Report Type. | ||
3 | Choose to generate the report:
| ||
4 | Check the Notify me by email check box if you want an email of when the report is ready for you to download. | ||
5 | Depending on the schedule for the report, select Generate Report or Schedule Report. |
You can only have a maximum of 50 reports in this list. Future scheduled reports won't run until there are fewer than 50 reports. |
1 | From the customer view in https://admin.webex.com, go to Reports and click the Report List tab. |
2 | Under Actions, click More |
3 | Click Download Report. |
You can disable a report if you want to pause the report from running automatically.
1 | From the customer view in https://admin.webex.com, go to . |
2 | Under Actions, click More |
1 | From the customer view in https://admin.webex.com, go to . |
2 | Under Actions, click More |
3 | Select Delete |
You can use classic reports to view comprehensive statistics for Webex Meetings, Webex Events (Classic), Webex Training, and Webex Support services in your organization. Monitor usage across services, attendance for events and sessions, and support activities so that you can determine how you can build a more efficient organization.
Learn more about these reports at this article.