Analytics provides workspace-wide visibility into real visitor traffic, Lead capture, Agent activity, page performance, and Knowledge coverage.
The page is designed to help you identify which Agents are receiving traffic, which pages convert visitors into Leads, and which questions still need better Knowledge.
The Analytics header displays the date range represented by the current reporting window.
The primary trend visualization in the deployed interface identifies itself as the Last 30 days.
When reviewing changes, compare metrics over a meaningful period rather than reacting to a very small number of Conversations.
The Conversations metric reports visitor Conversation volume for the reporting period.
The metric card also compares the current value with the previous period and displays a trend indicator when appropriate.
Messages reports the number of visitor messages represented in the Analytics period.
Use this together with Conversations to understand the depth of engagement rather than relying only on Conversation count.
The Leads metric reports captured visitor Leads.
Compare Lead volume with Conversations and page traffic to identify where visitor engagement is successfully turning into captured opportunities.
Lead Conversion is displayed as a percentage.
Use this metric to evaluate how effectively Conversation traffic becomes captured Leads.
A higher traffic count is not automatically better if Lead Conversion falls substantially at the same time.
Messages / Convo measures Conversation engagement depth.
It can help distinguish short interactions from Conversations where visitors continue asking questions.
Interpret it in context: a concise Agent may solve a question in fewer Messages, while a sales qualification flow may intentionally require more turns.
The main Analytics chart compares:
The interface explains that Conversations drive the primary area and Leads appear as a separate trend line so you can see whether Lead capture is increasing with traffic.
The Analytics summary reports the number of Active agents.
Use this as a quick indicator of how many Agents are currently contributing to workspace activity.
Published agents reports how many Agents are currently published.
If an Agent is expected to serve production traffic but remains Draft, investigate its publishing state before interpreting a lack of activity as poor visitor demand.
Tracked pages reports how many page locations have been observed through real visitor traffic.
Page URLs begin appearing in Analytics after the widget sees traffic associated with those locations.
The summary also displays the current number of Open gaps.
Open gaps identify visitor questions that still need attention in Agent Knowledge or Curated Answers.
The Top agents section helps identify which Agents are driving the most Conversation and Lead activity.
Each Agent row can include:
Select an Agent to open its workspace when deeper review is required.
The Top pages section identifies entry points that are receiving traffic and converting visitors into Leads.
Page rows can display:
Selecting a tracked Page can open the relevant filtered Conversations view.
A useful review pattern is:
A section with no traffic may legitimately show no Agent or Page activity yet.
Verify that the Agent is published, the widget is correctly installed, and real visitor traffic is reaching the relevant page before treating zero Analytics as an application problem.