Confluence Agent Analytics and Mission Control Guide
On this page
Quick answer
Atlassian says Confluence Analytics now counts agents alongside people across page, space, site, and Mission Control views. Page analytics can distinguish all viewers, people, and agents; agents can appear as contributors; and an agent working on someone’s behalf can be shown next to the person who invoked it.
Use that data for discovery and accountability, not as proof of quality or ROI. An agent reading a page 200 times can indicate a useful shared source, an inefficient loop, a broken automation, or unexpected access. The count alone cannot decide which.
What each signal can tell you
| Signal | Useful interpretation | What it does not prove |
|---|---|---|
| Agent page views | Which pages agents read and how often | The answer was correct, necessary, or policy-compliant |
| Agent contribution | An agent helped create or update content | The change was accepted, accurate, or valuable |
| Invoked-by identity | Which person initiated an attributed action | The person reviewed every later step or approved every destination |
| Invocation count | Adoption or repeated automated use | Time saved, user satisfaction, or outcome quality |
| Space or site trend | Where agent activity is concentrated | Causality, risk level, or permission correctness |
Pair analytics with page versions, agent configuration, tool and audit records, reviewer decisions, and downstream outcome data.
A practical scorecard
Define one workflow and measure:
- eligible invocations and unique active users;
- accepted outputs without material correction;
- median review time and total time to an accepted result;
- factual, permission, policy, formatting, and destination correction rates;
- stale-write rejections, denied actions, retries, and abandoned runs;
- public-share, export, restricted-content, or incident exceptions;
- successful rollback and mean time to recover;
- the underlying team outcome, such as current release notes or resolved documentation gaps.
Keep denominators visible. Ten corrected outputs out of twelve is different from ten corrected outputs out of ten thousand.
Mission Control and analytics access
Atlassian’s support documentation describes the Confluence administrator Mission Control center for Premium or Enterprise plans. It also notes that its high-level metrics refresh approximately every 24 hours. That cadence is useful for administration, not real-time incident detection.
Confluence administrators can restrict which groups use analytics, and space-level analytics access depends on the global permission boundary. Review analytics access itself: agent activity can reveal which projects, pages, and workflows are important even when page content is not shown.
For the underlying read, write, and recovery gates, use the permissions and version-history guide.
Investigate unusual agent activity
- Confirm the time window, data refresh time, filters, plan, and migration history.
- Identify the exact agent, owner, invoker, version, automation, external client, and tool set.
- Compare page views with invocations, successful actions, accepted outputs, and errors.
- Inspect permissions and whether the source page was expected context.
- Check for retries, loops, stale data, duplicated triggers, or an overly broad search.
- Pause the agent or automation if the pattern could expose data or create repeated writes.
- Record the explanation and corrective action without calling correlation a proven cause.
Treat vendor results carefully
Atlassian publishes customer examples, usage totals, claimed time savings, and its own Teamwork Graph benchmark. These can explain intended use and motivate a local test. They are vendor-authored evidence, not a guarantee that your agent, sources, permissions, review process, or workload will produce the same outcome.
Frequently asked questions
Can Confluence Analytics separate people and agent views?
Atlassian’s August 2026 launch says page analytics can switch between all viewers, people, and agents, and show which agents read a page and how often.
How are agent contributions attributed in Confluence?
Atlassian says agents appear as contributors on content they create or update, and an agent acting on someone’s behalf appears next to the person who invoked it.
Does a high agent-view count prove business value?
No. A view or invocation is activity. Measure accepted work, correction rate, time to review, policy exceptions, incidents, and the human or business outcome separately.
Who can use Confluence Mission Control and analytics?
Atlassian’s support documentation ties the administrator Mission Control center to Premium or Enterprise and allows administrators to restrict analytics permissions. Verify the current plan and role requirements.
Official sources
- Atlassian: Agents are in Confluence
- Atlassian Support: Act on insights from Mission Control
- Atlassian Support: View Confluence analytics
- Atlassian Support: Control analytics access
Source check: August 27, 2026. Recheck plan, analytics fields, attribution, permissions, privacy mode, lookback, refresh cadence, exports, and Mission Control availability.