Open the site usage panel on your intranet home site and sort the top content by views. In most organisations the same three things sit at the top every month: the canteen menu, the car park notice, and whatever HR published about payroll dates. The chief executive’s strategy update is somewhere on the second page. Then someone in the meeting asks the reasonable question, which is what you should write more of, and the list you are holding cannot answer it. It never could. A view ranking tells you which pages people landed on. It says almost nothing about which pieces of content did any work.
This article sets out a definition of engaging that survives that question, shows how far you can get with the reporting SharePoint already gives you, and is honest about where that reporting stops.
Views measure your distribution, not your content
The mechanism is worth stating plainly, because once you see it you cannot unsee it in your own reports. A page gets viewed because someone put a link in front of somebody. If a news post is promoted on the home site, boosted into the organisation news feed, and pushed to the Viva Connections dashboard, it will out-view a better piece that was published to a departmental site and mentioned nowhere[1]. The ranking you are looking at is a ranking of your own promotion decisions from three weeks ago.
The canteen menu is the clearest case. It ranks because it is a utility that people need repeatedly, not because it is compelling. Utility content and communication content are different jobs, and putting them in the same league table makes both look wrong. Any method that does not separate the two produces a monthly slide that quietly argues you should publish more parking notices.
Four definitions of engaging, and what each one costs you
There is no single correct measure. There are four honest candidates, and the right one depends on what the content was for.
| Signal | What it actually tells you | Where it comes from | What it misses |
|---|---|---|---|
| Unique viewers | How many distinct people opened it, stripped of repeat traffic | SharePoint page and site analytics | Whether they read past the first screen |
| Average time spent | Whether the page held attention long enough to be read | SharePoint page analytics | Distorted by tabs left open and by very short pages |
| Reaction and comment rate per unique viewer | Whether it provoked a response, not just consumption | Page analytics, calculated by hand | Systematically low on sensitive topics where people will not comment publicly |
| Return visits and onward clicks | Whether it was useful enough to come back to or act on | Page analytics plus link tracking | Not available per person without joining external data |
The one that repays the most effort is the third, and the reason is arithmetic. Reactions per view flatters heavily promoted content, because the denominator inflates. Reactions per unique viewer does not. A leadership post with 400 unique viewers and 60 reactions is doing something a post with 4,000 unique viewers and 70 reactions is not, and the raw counts point the other way.
What the native reporting actually gives you
Be fair to Microsoft here, because the native tooling is better than its reputation and it is free. Every modern SharePoint site has a Site usage page showing unique viewers, total views, average time spent per user, popular content and, usefully, where the traffic came from. Individual pages have their own analytics panel with the same shape of data for that page. At tenant level, the SharePoint site usage report in the Microsoft 365 admin centre gives you page views and active file counts per site over rolling windows[2].
For a single site owner asking whether a single page worked, that is genuinely enough. You do not need to buy anything. Our guide to SharePoint native analytics walks through the panels in detail, and if you are unsure why perfectly good pages get ignored, the piece on why SharePoint communications are ignored covers the distribution side of the problem.
Four checks that make a top-ten list mean something
These are all doable with the native panels and a spreadsheet. They take an hour a month and they change what the list says.
- Sort by unique viewers, not views. This alone usually reorders the top ten and removes most of the utility pages, because utility pages earn their position through repeat visits from the same people.
- Divide by the audience the piece was written for. A safety notice for 900 plant operators that reached 400 of them did better than a group-wide post that reached 2,000 out of 14,000. Views hide that completely. This is the single change with the biggest effect on how the list reads.
- Separate mandatory from optional. Two lists, not one. Compliance pages, policy documents and the canteen menu belong in a utility list where the question is whether people can find things. Communication content belongs in a list where the question is whether it persuaded anyone.
- Look at the second visit. A page people return to a week later did something. Return traffic is the closest thing the native data has to a quality signal, and almost nobody reports it.
Doing this consistently across a quarter is more valuable than doing it perfectly once. If you are building the discipline into a publishing rhythm, our note on measuring content calendar performance covers how to keep the comparison stable when the calendar changes.
Where the native panels stop
Three walls, and you hit them in this order.
The denominator is not in SharePoint. The second check above is the most useful one, and native reporting cannot do it, because SharePoint does not know that 900 people are plant operators. Site analytics counts viewers. It does not hold function, site, country, language or contract type. To divide by the intended audience you need those attributes from Entra ID or an HR file, joined to the page data deliberately. Our note on audience segmentation covers how to structure them.
The history is short and it resets. The retained window in native reporting is finite, which makes year-on-year comparison awkward, and a site rebuild or an information-architecture change can break the continuity of your page-level series entirely. If you are planning a redesign, read measuring after a SharePoint redesign before the new sites go live, not after.
It stops at the edge of SharePoint. The same message went out as a news post, in the internal newsletter, and in a Viva Engage community. Native reporting gives you three separate numbers and no way to establish whether that is one audience reached three times or three audiences reached once. That distinction is the whole of cross-channel measurement, and it is the question executives actually ask. Gallagher’s State of the Sector research keeps finding measurement to be the capability internal communicators name first as missing, and this is a large part of why[3].
The Power BI route, honestly
The usual next step is a Power BI model over the Microsoft Graph reporting API[4]. It is a legitimate route and some organisations run it well. Three things to know before you commit. The reporting API is not consistently reliable and produces days with missing data. Customers have observed KPI values in Power BI that do not reconcile with the native SharePoint reports for the same period, which is a bad conversation to have in front of an executive audience. And a dependable build needs a robust ingestion process with scheduled reconciliation against the native figures and a named owner, so budget for the pipeline rather than for the dashboard. Our piece on SharePoint analytics in Power BI goes through the failure modes.
Tryane sits in the layer above. It reads SharePoint alongside Viva Engage, Teams and your newsletter platform, joins page-level activity to your organisational structure through Entra ID or an HR file so the denominator question becomes answerable, and keeps history across redesigns and product transitions. Tryane is SOC 2 Type 2 certified and GDPR compliant by design, hosts in the EU by default with US data residency on request, deploys in a couple of hours over single sign-on with Azure AD or Entra ID, and installs no agent.
Frequently asked questions
Where do I find engagement data for a single SharePoint page?
Open the page and use the page analytics panel, which reports unique viewers, total views, average time spent and traffic sources for that page. For the whole site, the Site usage page gives the same shape of data plus popular content. Both are switched on by default on modern sites and need no configuration.
Is time spent on page a reliable engagement measure?
Treat it as directional rather than precise. It is inflated by browser tabs left open and deflated by pages that are genuinely short and did their job in fifteen seconds. It is most useful as a comparison between similar pieces of content published in the same format, and least useful when compared across formats.
Should we count reactions or comments as engagement on SharePoint news?
Yes, but as a rate per unique viewer rather than a raw count, otherwise you are just re-ranking by promotion again. Also read low comment counts carefully. On restructuring, pay or performance topics, silence in a named, non-anonymous corporate space is a signal about psychological safety rather than about the content.
How do we compare content performance across departments fairly?
Not by raw views, because department sizes differ by an order of magnitude. Use reach as a share of the intended audience, which requires joining page activity to workforce attributes. Native SharePoint analytics does not hold those attributes, so this needs either a manual export and join or a dedicated analytics layer.
Does Tryane replace SharePoint native analytics?
No. SharePoint continues to record what it records. Tryane sits on top, reading SharePoint alongside your other channels and joining the activity to your organisational structure, so you can answer segmented and cross-channel questions that no single native panel can. You keep the Microsoft 365 investment and add the measurement layer for what native does not do.
Sources
• Microsoft Learn, organisation news site
• Microsoft Learn, SharePoint site usage report
• Gallagher, State of the Sector
• Microsoft Learn, Microsoft Graph reporting API
Further reading
• A guide to SharePoint native analytics
• The limits of SharePoint analytics
• Measuring SharePoint communication reach
• Measuring after a SharePoint redesign
• Audience segmentation for internal communications
Tryane runs a 15-minute working session with Heads of Internal Communication, taking your current top-ten list and re-cutting it by unique viewers and intended audience on your own tenant. Book a slot with Jérémy.