Issue Summary

Confluence Page Analytics returns incomplete identity data for Rovo Chat page views.

When a user accesses a Confluence page through Rovo Chat, the usePageViewsAnalyticsViewersQuery response identifies the event as an agent interaction but does not resolve the associated Confluence user.

Example response:

{
  "accountType": "AGENT",
  "agentType": "rovo_chat",
  "relatedUserAccountId": "<user aaid>",
  "relatedUser": {
    "id": "<user aaid>",
    "displayName": "<user name>"
  },
  "confluenceUser": null,
  "userProfile": null
} 

For comparison, the same user accessing the page through the standard Confluence UI is returned as accountType: "USER" with populated confluenceUser and userProfile data.

Steps to Reproduce

1. Step 1 : Open a page
2. Step 2 : Use Rovo agent to read it.

Expected Results

The API should either:

• Populate userProfile and confluenceUser for the user associated with the Rovo interaction, or

• Return dedicated, clearly defined agent/initiator identity fields that the frontend can use.

Actual Results

In analytics , we see anonymous user.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available