View Analytics for the AI Assistant for Page Groups

🎯 Who this article is for: Admins, page group owners, and page group editors who manage the AI Assistant for a page group.

💼 Availability: Analytics for page group AI assistants are available to Starter, Growth, and Enterprise.

🔒 Permissions: Viewing analytics is available to admins or users with analytics viewing permission. Being a page group owner or editor, or having enabled the assistant yourself, does not grant access to its analytics on its own.

💻 Devices: Viewing analytics is only available on desktop.

🧪 Open beta: The AI Assistant for Page Groups, and its analytics, are currently in open beta. Metrics and layout may change as the experience develops.

1. Overview

The AI Assistant already gives your team direct, cited answers from a page group's content the moment they ask. Analytics turn that activity into insight: who's using the assistant, how those conversations play out, and how well the answers are landing. That's the evidence behind every decision that follows, where to enable the assistant next, and whether a page group's content is pulling its weight, backed by real usage instead of a guess.

2. Use cases

• Tell a reach problem apart from a real quality problem: If active users drop while conversations per user stays flat, the people already relying on the assistant haven't slowed down, fewer people are finding it. That points you toward visibility, like adding the Ask Widget to the page group's landing page.
• Know when a page group's content is due for a review: A rise in negative feedback rate is a cue to have the page owner take a look, whether that means updating a page that's fallen behind a policy change, filling in a topic that isn't covered yet, or checking whether Restrict search to this page group is blocking the assistant from an answer that lives elsewhere.
• Prioritize your next rollout with real demand, not a guess: The top page groups without an agent list ranks the highest-traffic page groups that don't have one yet. If one page group brings in hundreds of visits while the rest sit in the dozens, that's a clear signal of where enabling the assistant next will reach the most people, fastest.

3. Before you begin

• You must have analytics permission to view analytics for AI page group assistants. This is granted separately from your page group role, so being an admin, owner, or editor of the page group, or the person who enabled the assistant, does not grant this access on its own.
• An assistant must already be enabled on the page group. Page groups without one only appear in the top page groups without an agent list, not with their own analytics.
• Analytics reflect activity from users with access (edit and view rights) to the page group during the period you select.

4. Key terms

A few words get used close together when talking about assistant activity. Here's what each one means:

5. How to view analytics

1. Click your avatar and go to Analytics.
2. Navigate to Pages > Agent.
3. Use the Agent filter (labeled All Agents by default) to switch between combined data across every assistant or a single page group's assistant.
4. Select the reporting period you want to review (e.g. last 30 days, weekly).

Results update automatically to show usage and satisfaction data for the selected assistant and period.

6. How to interpret your usage metrics

The Usage section shows how much your organization is engaging with the assistant, from how many people ask questions to how deep those conversations go.

• Active users: The number of users who sent at least one message to the assistant during the selected period.
• Total conversations: The number of conversations started with the assistant.
• Conversations per user: The average number of conversations per user, calculated as total conversations divided by active users.
• Avg. messages per conversation: The average number of messages exchanged within a single conversation, reflecting how often users ask follow-up questions.
• Avg. session length: The average amount of time spent in a single conversation.
• Top page groups without an agent: The page groups receiving the most traffic that don't yet have an assistant enabled, ranked by visits, showing you the biggest opportunities to enable one.

7. How to interpret your satisfaction metrics

The Satisfaction section shows how well the assistant's answers are landing, and reads best alongside the Usage numbers above it.

• Positive feedback: Out of the conversations where a user left a rating, the percentage rated thumbs up.
• Negative feedback rate: Out of every conversation with this assistant, including conversations where no rating was left at all, the percentage that got a thumbs down.
• Monthly retention: The percentage of users who return to use the assistant again in later months, showing whether adoption holds over time rather than fading after an initial trial.

🗒 Note: Positive feedback and negative feedback rate use different totals as their base (one looks only at conversations that received feedback, the other looks at all conversations, rated or not), so the two numbers won't add up to 100%. See the FAQ below for more.

8. Best practices

• Read usage and satisfaction side by side, not on their own: A single metric rarely tells the full story. Rising messages per conversation only signals real engagement when it's read next to feedback and retention, not looked at in isolation.
• Track a page group's own trend, not how it compares to others: A company-wide Onboarding Hub will always generate more volume than a small Legal page group, so a side-by-side comparison of totals tells you little. Watch whether each assistant's own numbers are moving in the right direction over time.
• Give new data time to settle before judging it: The first few weeks of any page group's numbers often reflect curiosity as much as real use, so wait for a few weeks of activity to build up before drawing conclusions from them.

9. Frequently asked questions

If the assistant expands its search with Search AI, does that show up in these analytics?

No. If the assistant expands its search using Search AI, that activity isn't reflected in these analytics, which only show usage of the page group's own assistant.

Is a rise in negative feedback always a content problem?

Not always. The content itself might be outdated, hard for the assistant to locate within the page, or missing entirely, but the assistant's search scope could also be set to Restrict search to this page group, blocking it from an answer that exists elsewhere on your intranet. Worth checking both before deciding what to fix.

Can I compare analytics across all my assistants at once?

Yes. Set the Agent filter to All Agents to see combined data, or select a specific page group's assistant to isolate its numbers.

Why don't "positive feedback" and "negative feedback rate" add up to 100%?

Because they're calculated differently. Positive feedback only looks at conversations where a rating was left, and shows the share that were thumbs up. Negative feedback rate includes every conversation with this assistant, including ones where no rating was left at all, and shows the share that got a thumbs down. Since each metric uses a different total as its base, they aren't meant to add up to 100%.

Does archiving a page group affect its analytics history?

No. Its assistant's analytics history is preserved even after the page group is archived.

Does disabling the assistant affect its analytics history?

No. Analytics are never deleted. They stay exactly as they were, even after the assistant is disabled on a page group.