Can you see who viewed a Confluence page?
Yes, on some plans. Confluence page analytics in Confluence Cloud comes in two layers. Every paid plan shows how many people have viewed a page. The list of who viewed it, with dates and engagement, is part of the full analytics on the Premium and Enterprise plans. On the Free plan, Atlassian doesn't list page insights at all.
| Plan | What you get on a page |
|---|---|
| Free | No page insights |
| Standard | Estimated read time and the all-time number of viewers in the byline, plus a summary chart of views and unique viewers |
| Premium and Enterprise | Everything in Standard, plus full content analytics: date ranges, a per-person viewer list, views by mentioned people, and site and space analytics |
Plans and features change, so check your own site before you rely on any of this. If you don't see a view count under a page title, your plan most likely doesn't include it.
What Confluence page analytics shows
On the page itself
Under the title of a page, live doc or blog post, Confluence shows an estimated read time and how many people have viewed it in total. Select that text (or open Details on the floating action bar and choose Views under Stats) to open a summary. Its Views tab charts the number of views and unique viewers over time. The summary also has a Mentions view for people mentioned on the page and a Links view for the most-used links into and out of it.
Full content analytics (Premium and Enterprise)
From the summary, Get more insights opens the full analytics for that page. This is where you see who viewed it:
- A date range to filter views by period, with the data grouped by total or unique users.
- A viewer list, with each person's engagement, the last version they viewed, when they last viewed it and how many times. Engagement is either Engaged (the page was open for 20 seconds or longer) or Brief (under 20 seconds).
- Mentions, filtered to people mentioned on the page who have or haven't viewed it.
- Linked content, with click counts for links on the page and for pages that link to it.
Space and site analytics (Premium and Enterprise)
Beyond single pages, space analytics lists each content item in a space with when it was created, last modified and last viewed, its comment activity, and its views and unique viewers for a chosen date range. A Users tab shows who created, edited, commented on and viewed content. Site analytics adds the same view for spaces and users across the whole site, plus the terms people search for. Space and site reports can be exported as CSV.
Important: Atlassian describes full analytics for sites, spaces and content as having a one-year lookback. If you migrated from Confluence Data Center, data starts from the migration. Don't count on page analytics to answer questions about views from further back.
Who can see Confluence page views
On Premium and Enterprise, who can open analytics is a permission you control at two levels:
- Site level. A Confluence administrator allows or denies groups under Security > Analytics permissions in Confluence administration. With no restrictions set, new groups get access to analytics. Once at least one group is denied, new groups are denied by default.
- Space level. A space admin can restrict analytics in their space to named people or groups, under the space's access settings. Only people and groups who already have the site-level permission can be granted it.
Anonymous users can't view analytics. If your company treats viewing history as personal data, decide who really needs the viewer list (space owners, a documentation lead) and restrict the rest, rather than leaving the default open to every group.
Privacy mode and hiding who viewed a page
A Confluence admin can turn on privacy mode for analytics: in Confluence administration, open Security configuration under Security and turn on Hide personal data in analytics. With it on:
- Every viewer's name and avatar is replaced with a hashed, anonymous name, in all analytics views. Each alias still stands for one person, so you can see engagement patterns without knowing who.
- It applies to existing data too, not only new views.
- Repeat views by the same person aren't recorded individually, so total view counts can be lower than reality.
- Space analytics hides its most active readers and contributors, and its Users tab.
If you turn privacy mode off again, data from before it was switched on shows real names again, but views recorded while it was on stay anonymous. That matters if you later want named viewing data for a period: you can't recover it.
Two things people often look for and won't find in Atlassian's documentation: a per-person setting that lets an individual hide their own views, and a switch that stops Confluence counting page views altogether. The documented controls are the site-wide privacy mode and the analytics permissions above. If your employees should know their page views are visible to others, say so in your acceptable use or internal privacy notice.
What Confluence page views are good for
Page analytics is a good tool for keeping a knowledge base healthy. Some practical uses:
- Find stale pages. In space analytics, look for content whose last view and last edit are both long ago. Those are candidates to archive, merge or rewrite. Note that the CSV export only includes items with at least one view, edit or comment in the period you picked, so a page nobody touched at all won't be in it: compare against the page tree too.
- Find the pages that matter most. The most-viewed pages in a space deserve the most care: a named owner, a review date, and a quick check that they're still correct.
- See whether a rollout landed. After you publish a new process or announce a change, watch the view chart for the first few days. On Premium and Enterprise, mention the people involved and use the Mentions view to see who hasn't opened it yet, then follow up.
- Check whether people stay. A page with many Brief views and few Engaged ones may be the wrong page for what people are looking for, or too long to be useful.
- Find gaps. Site search insights show what people search for. Frequent searches with few clicks often point to documentation you don't have yet.
Why a page view isn't proof for compliance
The question changes when an auditor, HR or a regulator asks you to show that employees read and accepted a policy. It is tempting to open the viewer list and export it. Here is why that usually isn't enough:
- A view is not acceptance. Opening a page isn't reading it, and reading isn't agreeing to it. Engaged only means the page was open for 20 seconds or more.
- It doesn't pin the approved text. The viewer list shows the last version each person viewed. It says nothing about whether that was the approved version, and a later visit replaces it.
- It has no audience or deadline. Analytics lists who looked, not who was supposed to. You still have to compare it against a staff list to find who is missing, and there is no due date that makes someone overdue.
- It may not exist or last. Named viewing data needs Premium or Enterprise, can be anonymized by privacy mode, and is described with a one-year lookback. SOC 2 Type 2 observation periods are commonly 3 to 12 months, and auditors may sample from earlier periods too; your auditor decides what they need.
For SOC 2 and similar programs, what holds up is an explicit, recorded acknowledgement: who, which version, when, and that they accepted it. The Confluence read confirmation article walks through the workarounds people try and what a defensible record holds, and policy acknowledgement tracking covers what auditors look for and when to ask people to acknowledge again. Use page analytics alongside that record, for engagement, not instead of it.
Policy acknowledgements in Confluence with Compliance in a Box
Compliance in a Box is a Confluence Cloud app that runs a SOC 2 compliance program in one Confluence space. For the policy pages it manages, it replaces "did they view it" with a click-through acknowledgement:
- An explicit step. The person opens the approved version, selects I have read and understand this policy and clicks Acknowledge, either from My Tasks in the app or from Please acknowledge under the policy page's title. See acknowledge a policy.
- Bound to the approved version. The app records the Confluence page version and a fingerprint of its content. If the page has unapproved edits, people are pointed to the approved version instead.
- An audience and a due date. Each policy goes to All employees or Specific groups, and everyone asked has 30 days. People who join the audience later are picked up by the app's daily check.
- Evidence for the auditor. The Policy Acknowledgement Report lists every person asked, their status, when they acknowledged and which page version, and every acknowledgement is in the audit log.
Only Compliance Admins see who has and hasn't acknowledged; policy owners see a percentage for their own policies. The full detail is in the policy acknowledgements chapter of the user guide.
FAQ
Can I see who viewed my Confluence page on the Standard plan?
On Standard you see the read time, the total number of viewers and a chart of views and unique viewers. The per-person viewer list is part of the full content analytics, which Atlassian offers on Premium and Enterprise.
Can people tell that I viewed their page?
On Premium and Enterprise, anyone with analytics permission can see the viewer list, unless an admin has turned on privacy mode. Atlassian's documentation describes no setting for an individual to hide their own views.
How far back do Confluence page views go?
Atlassian describes full analytics for sites, spaces and content as having a one-year lookback. The view count in the page byline is an all-time total.
Is a Confluence page view enough evidence that employees read a policy?
Usually not. A view shows the page was opened, not that the person read and accepted a specific approved version. Auditors generally expect an explicit acknowledgement tied to the version; confirm the evidence format with your auditor early.