Open the site usage report on your main communication site and you get five things: views, unique viewers, site visits, average time spent and a ranked list of popular content. It takes about a minute to move those into a slide, which is why so many intranet reports look like that. The problem starts one question later, when someone senior asks what the number means for the population they care about, and the honest answer is that the report does not know who those people are.
This piece is narrow on purpose. Not internal communication measurement in general, which we cover in the broader guide to internal communication KPIs, but the intranet specifically: what SharePoint native gives you, which of it misleads, and what to report instead.
What SharePoint native actually reports
Two levels matter. At page level, a modern SharePoint page carries an analytics panel with views, unique viewers and average time spent for that page. At site level, the site usage report aggregates the same measures across the site collection and adds site visits, popular content and, where relevant, sharing with people outside the organisation. Microsoft’s portal health guidance is the reference for what is available and how to read it[1]. Tenant-wide SharePoint activity also appears in the Microsoft 365 admin centre usage reports, over selectable windows[2].
Three properties of that data determine everything below. It is scoped to a site or a page, not to a person or a population. It is retained for a finite window rather than indefinitely. And it holds no organisational attributes at all, so function, country, site, grade and contract type are simply not present. None of this is Microsoft doing a poor job. It is a site-first product doing exactly what a site-first product does, and our guide to SharePoint native analytics goes through each report field by field.
The five numbers that mislead
1. Page views presented as consumption
A view is a page load. It is not a read, and the gap is wide. Navigation generates loads, the homepage collects loads from people passing through to a payslip link, a browser refresh counts again, and one enthusiastic communications colleague checking her own article renders can produce forty. In the other direction, an assistant answering from the page produces none at all, which is now depressing the figure on exactly your most useful reference content. That effect deserves its own treatment and we give it one in what happens to your numbers when AI answers first.
2. Unique viewers called reach
This is the most common error in intranet reporting and the most damaging, because it looks rigorous. Unique viewers is a numerator with no denominator attached. Four thousand unique viewers is excellent in a company of six thousand and a serious problem in a company of forty thousand, and the report will present it identically in both cases. It is also unique per site, so a person who read the same announcement on two hubs is two unique viewers. Fixing this starts with deciding what population you are measuring against, which is the argument in our piece on what counts as the intranet.
3. Average time spent
An arithmetic mean over a distribution that is never normal. A handful of sessions where somebody left the tab open over lunch drag the average up; the many two-second bounces drag it down; the resulting number moves for reasons unrelated to your content. It also carries no completion signal, so a rising average is as likely to mean people are struggling to find the clause they came for as it is to mean they are engaged.
4. The popular content list
Ranking pages by raw views mostly ranks them by navigation prominence. The homepage wins. The page linked from the global header wins. The HR landing page that sits between employees and the leave request form wins. Almost nothing in that list is a judgement about content quality, and treating it as an editorial signal leads teams to produce more of whatever happens to be structurally well placed.
5. The site traffic trend across a redesign
Site usage is tied to the site collection and the URL. Move to a new information architecture, split a hub, or rebuild the news site, and the series restarts. Teams frequently show a year-on-year intranet trend that silently spans two different sites, which is not a comparison. Handling this properly is the subject of our note on measuring after a SharePoint redesign.
| Native metric | What it counts | Failure mode | Better question |
|---|---|---|---|
| Views | Page loads | Inflated by navigation and refresh, deflated by assistants | How many of the intended audience received this? |
| Unique viewers | Distinct viewers per site | No denominator, double counts across hubs | What proportion of the target population, by segment? |
| Average time spent | Mean session duration | Skewed by open tabs, no completion signal | Did people who started the critical content finish it? |
| Popular content | Pages ranked by views | Ranks placement, not quality | Which content performed above expectation for its placement? |
| Site traffic trend | Traffic within one site collection | Resets on redesign or URL change | What is the multi-year trend for the intranet as a whole? |
Five intranet measures that survive scrutiny
Reach rate against a stated population. Not a count, a proportion, with the base written next to it: “62 per cent of the 31,400 people with an Entra ID account”. State the denominator every time, and never change it mid-year without saying so.
Coverage across a campaign, not per post. The share of the target segment reached at least once during the campaign window, on any surface. Per-post reach rewards volume. Coverage rewards actually getting to people, which is the thing you were asked to do.
Read-through on the content that matters. Not everything, and not as a vanity measure. Pick the five or six pieces a year that genuinely have to land, typically the strategy update, the results announcement, the code of conduct and the safety-critical pages, and measure whether the people who started them finished them.
The equity gap. The difference in reach rate between your best-served and worst-served segment. In most organisations this is the single most useful number on the page, because it turns “the intranet is doing fine” into “the intranet is doing fine for head office and reaching 9 per cent of manufacturing”. Gallup’s workplace research keeps finding the widest engagement gaps in frontline and deskless populations[3], and an aggregate intranet figure hides precisely that. Structuring the attributes is covered in our piece on audience segmentation.
Content decay. The proportion of published pages with zero views in 90 days, and the proportion with no named owner. This is the only measure on the list that improves by deletion, which makes it unpopular and useful. It has also become a risk measure rather than a tidiness measure, because unowned stale pages are now feeding assistant answers.
The honest position on native, and on the Power BI route
If you own one communication site and want to know whether your pages are being read, native SharePoint reporting answers that, it is free, it is already switched on, and you should build nothing. The same is true for a community manager and a single Viva Engage community. The limits only appear when the question becomes organisational: proportion of a defined population, comparison between segments, one figure across intranet, Viva Engage and the newsletter, or a trend that spans a redesign. Gallagher’s State of the Sector research has repeatedly found measurement at the top of the capability gaps internal communicators name[4], and the reason is structural rather than personal.
The common next step is a Power BI build on the Microsoft Graph reporting API[5]. Some organisations run it well. Know what it involves: the reporting API is not consistently reliable and produces days with missing data, customers have shown us Power BI dashboards whose KPI values do not reconcile with the native SharePoint reports for the same period, and a dependable build needs a robust ingestion process, scheduled reconciliation against the native figures and a named owner. Budget for the pipeline rather than the dashboard, because the reconciliation argument in front of an executive audience is where most of these builds quietly end.
Tryane exists to supply that layer without the pipeline. It reads SharePoint alongside Viva Engage, Teams and your newsletter platform, joins the activity to your organisational structure through Entra ID or an HR file so that segment and equity-gap questions are answerable, and keeps unlimited history so a redesign or a product transition does not restart the series. It 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. The side-by-side detail sits in our comparison of Tryane against SharePoint native analytics.
Frequently asked questions
How many intranet metrics should we report to the executive?
Four or five, held constant all year. The temptation is to show everything the tool produces, which invites the audience to pick the number they find least convincing. A short stable set with defined denominators reads as a measurement programme; a long changing set reads as a search for a flattering figure.
Is unique viewers a valid reach measure?
Only once you attach a population to it and account for the same person appearing on several sites. On its own it is a count, and a count cannot be good or bad. Convert it to a proportion of a named population, state that population next to it, and it becomes defensible.
How far back does SharePoint keep usage data?
A finite window, selectable within limits, and shorter than the multi-year comparisons executives ask for. This is the practical reason teams either export regularly into their own store or run a measurement layer that retains history independently. Discovering the limit in the week you need a three-year trend is the common way to find out.
Our page views fell but engagement seems fine. What is going on?
Check whether an assistant was rolled out in the same period. When Copilot or an intranet chatbot answers from your content, the read happens and the page load does not, and the fall concentrates on reference pages rather than news. That is a measurement artefact rather than a communication failure, though it does mean your reach definition needs rebuilding.
Does Tryane replace SharePoint native analytics?
No. SharePoint carries on recording what it records. Tryane sits above it, reading SharePoint alongside your other channels and joining all of it to your organisational structure so you can answer segmented and cross-channel questions no single native report can. You keep the Microsoft 365 investment and add the layer for what native was never built to do.
Sources
• Microsoft Learn, portal health and site usage
• Microsoft Learn, Microsoft 365 admin centre activity reports
• Gallup, State of the Global Workplace
• Gallagher, State of the Sector
Further reading
• Internal communication KPIs for 2026
• A guide to SharePoint native analytics
• The limits of SharePoint analytics for internal communication
• Measuring after a SharePoint redesign
• What is an intranet, and why the definition decides what you can report
Tryane runs a 15-minute working session with Heads of Internal Communication that starts from your current intranet slide: which of those numbers would survive a follow-up question, and what the same period looks like once it is expressed by segment. Book a slot with Jérémy.