Page view counter at the bottom of the page not matching the number shown on usage report.

George 20 Reputation points
2026-11-03T16:37:41.8266667+00:00

So this question is building off a question of the same name that I didn't feel had a satisfying answer. I'll try to phrase the poster's question slightly differently to hopefully get a better answer.

Looking at the 7 day history of a given sharepoint news article using the analytics button on the news article is hugely inflated compared to the numbers generated through the 90 report in a way that cannot be accounted for by the 90 day report being pulled at a certain time.

For example, my company has a recently published news article last week. Clicking the analytics bar, it shows me a graph on 'unique viewers' section set to 'last 7 days' which reads 0,0,135,14,13,196,88 (total 446) . The total reads 379, All time reads 207.

Obviously we're off to a bad start with none of the totals matching up to reality. When the usage report gets involved it gets stranger. Pulling a report on the same day, the popular content tab gives me 85 for 'Last 7 days unique viewers' and 139 for Last 7 day visits. There's no way to line any of these numbers up that I can see.

This is not a problem unique to this example page. It's been a consistent mismatch across reports for months.

Can someone explain to me what is the difference in criteria between the 90-day report and the page analytics summary for unique viewers?

For bonus marks, could someone explain why this difference exists?

Microsoft 365 and Office | SharePoint | For business | Windows
0 comments
Answer accepted by question author
Ryan-N 16,940 Reputation points Microsoft External Staff Moderator
2026-11-03T17:30:11.48+00:00

Hi George,

Welcome to the Microsoft Q&A forum.

Based on your description, I understand that:

For the same article:

  • The Page Analytics > Unique viewers > Last 7 days chart shows the number of viewers for each day as follows: 0, 0, 135, 14, 13, 196, and 88.
  • The total of the daily viewer counts is 446, but Page Analytics shows a total of 379.
  • The All time metric shows only 207, which is even lower than the figure for the last 7 days.

If the same person views the article on multiple days, they will be counted once for each day on the chart. However, when SharePoint calculates the total number of unique viewers across the entire 7-day period, that person is counted only once

For example:

Person A views the article on Monday and Tuesday.

On the daily chart, Person A appears on both days. However, in the total number of viewers for the 7-day period, Person A is counted only once.

Therefore, the sum of the daily figures may be 446, while Page Analytics shows a total of 379.

However, under normal circumstances, the All time figure should not be lower than the figure displayed in Page Analytics for the last 7 days.

In this case, I recommend creating a support ticket with Microsoft Technical Support so that the issue can be investigated in greater depth. They have the necessary tools to examine the analytics data and the data aggregation process on the back end, which can help determine why the All time figure is lower than the figure shown in Page Analytics.

To create a support ticket with Microsoft Technical Support, you can refer to the following documentation:

 Get support - Microsoft 365 admin | Microsoft Learn

If you have any questions or need further assistance, please feel free to share them in the comments on this post so I can continue to support you.

I look forward to continuing the conversation.

If the answer is helpful, please click "Yes" and kindly upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.