SharePoint intranet user experience in a modern office

SharePoint Analytics for Internal Communication: Build the Practice, Not the Dashboard

By Nicolas Saliba · 8 min read

An intranet redesign went live in March. By June the page views are up, the bounce rate is down, and the head of internal communication cannot answer the only question the steering group asks: did it work? The numbers moved, but news is published from twelve different sites with no shared taxonomy, three of those sites also host document libraries, and the two that serve the plants were never migrated. There is no population the figures can honestly be divided by.

This is the ordinary condition of SharePoint measurement in a large organisation, and it is rarely a reporting problem. It is an architecture problem showing up in the reporting. You cannot fix it in the dashboard, which is why so many intranet analytics projects stall after the first review.

The measurement problem is usually an architecture problem

SharePoint site analytics reports on a site. That is a reasonable design decision by Microsoft and it has one consequence that determines everything downstream: your reporting units are your sites. If your site structure reflects who built the intranet rather than who reads it, your reporting will describe the build.

Microsoft’s own guidance on modern information architecture treats hub structure, navigation and audience as one design problem rather than three^[1]. Internal communication teams often inherit an architecture designed before they were involved, then try to compensate with reporting. It does not work, and three decisions in particular set the ceiling on what you will ever be able to measure.

Where organisational news is published from

An organisation news site designates the authoritative source of corporate news across the tenant, which is what allows official news to surface consistently in the SharePoint start page, Viva Connections and the mobile app^[2]. It also gives you one reporting unit for corporate communication instead of twelve. If corporate news is published from wherever the author happened to have edit rights, no amount of analytical effort will reassemble it afterwards.

Whether a thing is a news post or a page

News posts and site pages behave differently in the news feed, in search and in the analytics. Teams that use them interchangeably end up unable to separate “communication we published” from “reference material that exists”. The distinction is worth enforcing editorially, because it is what makes a content performance report readable a year later.

Whether audiences are defined before or after publishing

Audience targeting works from Entra ID groups. If those groups exist and are maintained, targeting and segmented reporting are the same underlying structure. If they are built ad hoc per campaign, you will have a different audience definition every quarter and no comparable trend. Getting the attributes right in advance is the substance of our note on audience segmentation for internal communications.

Every metric should name the decision it triggers

The single most useful discipline in intranet measurement is to refuse to put a number on a report unless someone can say what they would do if it moved. It removes about half of most existing dashboards immediately, and what remains is defensible.

Metric	Decision it should trigger	Who acts
Unique viewers of corporate news, as a share of a fixed population	Whether the channel mix is adequate for that population	Head of internal communication
Share of viewers by function, site or language	Where to add a cascade, a translation or a physical channel	Communication business partner
Read completion on long-form posts	Whether to change format or length, not whether to publish	Editor
Search terms returning no useful result	What to write next, and what to retire	Content owner
Time from publication to 50 per cent of eventual reach	Send time, cascade timing, and whether a reminder is warranted	Channel owner
Pages with no views in 90 days	Archive or reassign an owner	Intranet manager

Notice what is missing. Total page views appear nowhere, because no one has ever changed a decision on the basis of them. They are worth keeping as a health signal and worth keeping off the report you take to a steering group.

A cadence that survives a change of director

Most measurement practices die because they are built around one enthusiastic person and one large monthly document. A practice that lasts has three separate rhythms with different audiences and different lengths.

Weekly, operational, fifteen minutes. One screen. Last week’s publications, reach against the fixed population, anything that underperformed by a wide margin, and search terms that returned nothing. The output is a task list, not a document. Nobody outside the team sees it.

Monthly, editorial, one page. What we published, who it reached by segment, what we learned, what changes next month. This is where the gap between best-served and worst-served populations belongs, because that is the number that drives editorial planning. Our reporting template is a reusable starting point.

Quarterly, executive, three slides. Trend, gap, and one decision you want from them. Gallagher’s State of the Sector research has consistently found measurement to be the capability internal communicators name as their biggest gap^[3], and in practice the shortfall usually appears at this level rather than in the operational reporting. Teams measure diligently and then present the measurement instead of the decision. Our guide to executive reporting for internal communications works through that translation.

The virtue of separating the three is that the quarterly deck stops being a compilation of everything you counted. It becomes an argument with evidence attached, which is what survives a change of sponsor.

What SharePoint native analytics does genuinely well

This deserves a proper paragraph rather than a concession clause. Site usage reports in the Microsoft 365 admin centre give you site-level views, unique viewers and file activity across rolling windows without any configuration, and site owners get page-level detail in the site itself^[4]. The page diagnostics and portal health guidance will also tell you when a page is slow, which is a real cause of low read completion that no amount of editorial work will fix^[5].

If you run one communication site for a population of a few hundred, that is the whole job. Export it monthly, keep the file, and spend your budget elsewhere. Our walkthrough of using SharePoint native analytics covers how to get the most out of the panel before you consider anything else.

The boundary is well defined. Native reporting has no view of your organisational structure, so it cannot divide by function, site, language or contract type. It retains a finite window, so multi-year comparison is not available. And it sees SharePoint only, so it cannot tell you whether the population that missed the intranet post caught the same message in the newsletter or the Viva Engage community. We treat that boundary properly in the limits of SharePoint analytics, which is the piece to read if you are building the business case rather than the practice.

Before you build it in Power BI

The standard next step is a Power BI model over the Microsoft Graph reporting API. It is a legitimate route, and three things need saying before a budget line is committed to it.

The Graph 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 difficult conversation to have in front of an executive audience. A dependable build therefore needs a robust ingestion process and scheduled reconciliation against the native figures, with a named owner for both. Budget for the pipeline rather than the dashboard. Our note on SharePoint analytics in Power BI sets out the specific failure modes.

Where the joined layer earns its place

Once the architecture is right and the cadence is running, the residual gap is always the same one: you can describe activity inside SharePoint, but not participation across the workforce, and not across channels. Tryane sits in that gap. 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, and keeps history across redesigns and product transitions so a three-year trend is one line.

On the practical points: Tryane is SOC 2 Type 2 certified and GDPR compliant by design, hosts in the EU by default with US data residency available on request, deploys in a couple of hours over single sign-on with Azure AD or Entra ID, and installs no agent or code on your sites. If your immediate problem is proving the redesign worked, measuring after a SharePoint redesign is the closest match, and if the symptom is publishing into silence, why SharePoint communications get ignored approaches it from the content side.

Frequently asked questions

What can SharePoint analytics tell me about internal communication?

Within a site, a good deal: which news posts and pages were viewed, by how many unique viewers, over rolling windows, plus file activity and page performance. What it cannot tell you is who those viewers were in organisational terms, or whether the people who did not view the post received the message another way. Those two questions are the reason most teams eventually add a layer.

Should we fix the intranet architecture before buying an analytics tool?

Fix the parts that determine your reporting units first, which usually means designating an organisation news site, separating news posts from reference pages, and getting audience groups maintained in Entra ID. Analytics on a coherent architecture produces decisions. Analytics on an incoherent one produces a longer argument about the numbers.

How often should we report on intranet performance?

Three cadences rather than one. A weekly operational check that produces tasks, a monthly editorial page that drives planning, and a quarterly executive summary that asks for a decision. Merging them into a single monthly document is the most common reason a measurement practice quietly stops.

Can we measure SharePoint and the newsletter as one campaign?

Not from the native tooling. SharePoint counts viewers against its own visibility, the newsletter platform counts opens against a distribution list, and neither holds the workforce attributes that would let you compare them fairly. Joining them requires reading both and resolving them against a single definition of your population.

Does Tryane replace SharePoint native analytics?

No. SharePoint continues to record what it records, and site owners keep their native reports. Tryane sits above, consuming that data alongside your other channels and joining it to your organisational structure so you can answer segmented, cross-channel and multi-year questions. You keep the Microsoft 365 investment and add what native was never designed to do.