---
title: 'AI Assistant on Web: Analytics '
deprecated: false
hidden: false
metadata:
  robots: index
---
All Assistant on Web usage data is automatically included in your existing customer-facing analytics dashboards.
There are no new dashboards or configuration steps required. Once your users start interacting with Assistant on Web, all metrics will appear alongside your existing Assistant data.

# Access your Analytics Dashboard

1. Login to your [my.moveworks.com/moveworks_analytics ](my.moveworks.com/moveworks_analytics) .

_Screenshot below is illustrative, sourced from our internal demo & testing environment._

![](https://files.readme.io/a99454b096851953f19ef8840de670757e4bff7d618f96f88956484b776e5db3-image.png)

# Available AI Assistant Insights Dashboards

Analytics for Assistant on Web is available in your standard dashboards:

* Overview – Tracks total Assistant usage and key metrics over time.
* CSAT – Measures employee satisfaction with AI-generated responses.
* Triage – Displays how requests and issues are categorized and resolved.
* User Insights – Shows active users, adoption trends, **and now includes a “Web” platform view.**
* Plugin Insights – Highlights which plugins are most frequently used by the Assistant.
* Raw Interactions – Provides a detailed log of every user interaction.

Note: No setup is required. Data for Assistant on Web will flow automatically into these existing dashboards as soon as your users start using the web experience.

# What's new?

You'll see a new platform within the User Insights webpage.

* User Insights – Shows active users, adoption trends, **and now includes a “Web” platform view.**

The list of platforms you may see depending on how many platforms are available in your organization include:

* `msteams`+ `msteams_agent`: Microsoft Teams
* `slack`: Slack
* `movewebchat`: Embedded Assistant
* `web`: Assistant on web
* `gchat`: Google chat
* `glip`: Glip
* `webex`: Cisco Webex
* `zoom`: Zoom
* `facebookworkplace`: Meta Workplace 

These will appear within the** "How is AI Assistant adoption across surfaces?"** bar graph.

_Screenshot below is illustrative_

![](https://files.readme.io/ca9e52cea65de25328db0d6e5f5618458f0d7f0a64c28273b2bd6b6de86e4a98-image.png)

<Callout intent="warning">
  **Known issue:** 

  Assistant on Web launched to all customers on November 6, 2025. We are not able to differentiate some types of user interactions between the `web` and `movewebchat` platform. This means that as of November 6, 2025 the following user interactions will be labeled as "web" when there's a possibility the user interaction actually occurred on the  `movewebchat` platform.

  The list of user interactions only apply to notifications. Since the following notifications are sent to all platforms: Employee Communications, Ticket Updates, and Agent Studio. When those notifications are sent to both `web`and`movewebchat` platforms, we are unable to properly label any URL clicks. Specifically the types of URL clicks we are incorrectly labeling as the `web` platform include:

  * URL links to tickets (user is viewing a ticket in an ITSM system)
  * URL links related to knowledge base articles (ex. user is viewing a confluence article)

  This means that if any notification, specifically these (Employee Communications, Ticket Updates, and Agent Studio) contained a URL to tickets or knowledge base article we don't know if the action was taken on the `web` and `movewebchat` platform given that at this moment we will log this interaction with the  `web`label.

  This issue does not apply to any chat platforms. Our engineering team is actively working on resolving this issue.
</Callout>