#Why Are Page Views Different from SharePoint?

Microsoft provides built-in site usage data and inline article statistics in SharePoint. Because these numbers are highly visible, they often become the primary reference point for users and stakeholders. For that reason, it can be surprising when tyGraph page views or unique user counts are higher or lower than the numbers shown in SharePoint.

#Why Is tyGraph Different?

There are multiple ways to capture telemetry in Microsoft 365, and each service measures activity differently. Because of that, counts from two systems will not always match exactly.

We recommend comparing results across sources with that in mind. A variance of about 5% to 10% can be normal, especially in large global tenants. If you are seeing a much larger variance, such as 500% or more, review the possible causes below. Network configuration, especially cloud proxies and filtering, is one of the most common reasons for significant discrepancies.

#Firewall Restrictions for Scripts, Application Insights, API, or tyGraph CDN

If users connect through a corporate network, VPN, or DirectAccess, page view logging can be blocked by security controls such as a cloud firewall or reverse proxy. Although the SDKs used by tyGraph support batching and retries, telemetry traffic can still appear bursty to network devices. Some firewalls may block or deprioritize this traffic, which prevents telemetry from being captured.

This can significantly reduce reported page views, in some cases by as much as 80% for organizations with strict network controls or large on-premises populations. Review your firewall or reverse proxy rules to confirm that connections to the tyGraph API, CDN, and Application Insights endpoints are allowed. Also review the network requirements for tyGraph Pages.

Even if your firewall is not explicitly blocking Application Insights or related IP addresses, content filtering or content tracking policies may still prevent outbound traffic from reaching our endpoints.

For a full list of IP addresses required for tyGraph to send telemetry to Application Insights, see this Microsoft article. You may need to allow all addresses listed in the tyGraph Pages network requirements.

We have also seen cloud firewalls block the JavaScript file from loading from the CDN. When that happens, the script never loads for that user session and no telemetry is collected. If you use a cloud firewall or reverse proxy, review the network requirements and add https://tygraphpagescdn.azureedge.net to the allow list. This is one of the most common causes of discrepancies in page view and unique user counts.

#Different Page View Definitions

SharePoint and tyGraph for SharePoint, which is based on the audit log, typically count one page view per session. SharePoint's built-in usage metrics also attempt to filter repetitive actions by the same user.

For example, if a user refreshes a page or returns to the same page repeatedly during the same session, Microsoft may not count each of those actions as separate views. Microsoft describes this behavior in this article:

"The algorithm used to calculate Site visits is designed to filter out repetitive, continual operations by the same user on the same item (page, document, or news). For example, when a user repeatedly refreshes a page, document, or news post."

By contrast, tyGraph Pages captures each page action, even when multiple actions occur in the same session. This can result in higher page view counts for some tenants.

#Unsupported Browsers in tyGraph Pages

The tyGraph Pages Engine does not capture user activity from unsupported browsers.

For example, page views from Internet Explorer are not counted. For supported browsers, refer to tyGraph Pages browser support, which includes Microsoft Edge, Google Chrome, Mozilla Firefox, and Apple Safari.

#Report Latency

Different tyGraph products refresh on different schedules. tyGraph Pages collects data in near real time, usually within 15 minutes, while tyGraph for SharePoint typically refreshes every 24 hours. If you notice major differences between reports, verify the latest refresh times before drawing conclusions.

#User Selection and Filters

Power BI filters can be applied unintentionally. Double-check the current report selections to confirm that data has not been excluded or filtered out.

#Low Bandwidth or High-Latency Connections

The tyGraph Pages Engine waits one second after the page has fully loaded before sending telemetry. On slow or unstable connections, the script may time out or the user may navigate away before the telemetry is sent. In those cases, the page view may not be recorded.

#Perform a Health Check

The tyGraph Pages Site Analytics web part includes a health check feature that can help identify connectivity issues. If you suspect telemetry capture problems, run the health check with different users and from different physical locations. A successful result in one location does not guarantee that another user or location will behave the same way.

#Comparing Views on a Page Created Before tyGraph Was Installed

If you compare SharePoint page views with tyGraph Pages for a page that existed before tyGraph was installed, you may see a difference because tyGraph only collects data from the time of installation forward. Historical page activity is not imported retroactively.

#Users in Multilingual Settings

In multilingual environments, aggregated page views in tyGraph Pages are accurate, but they may not align exactly with native SharePoint usage metrics unless you drill into the language-specific pages. For example, if English and Japanese versions of a page are tracked separately, the default tyGraph Pages view may show the combined total while SharePoint usage may be displayed differently at the individual page level.

#Installing tyGraph Pages Engine in a Single Site Collection App Catalog

If tyGraph Pages Engine is installed in only one Site Collection App Catalog, telemetry will be collected only for that site collection. We recommend using the tenant-level app catalog and making the package available to all relevant sites rather than deploying to a single site collection.

#Look for Errors in the Browser Developer Console

Open the browser developer console and look for warnings or errors related to tyGraph. You can also enable tyGraph debug mode for more detailed information. Test with several user accounts, including non-administrators, and from multiple physical locations where possible.

#Azure Monitor Private Link

If your organization uses Azure Monitor Private Link, it can affect telemetry capture when tyGraph hosts Application Insights on your behalf. In the browser developer console, this issue often appears as a 403 error on the POST request to dc.services.visualstudio.com.

To allow tyGraph Pages to send telemetry successfully, make sure the Private Link access mode is configured as Open. Additional information is available in Microsoft's documentation.

#Why Page Like Count May Differ from SharePoint

tyGraph Pages captures page likes in real time when a user clicks the Like button. Depending on the platform, such as the SharePoint mobile app or Microsoft Teams, that interaction may not always be captured in the same way. In addition, pages that existed before tyGraph was installed will not include historical like counts. A future release will improve the way page like counts are reported.

#tyGraph's Commitment to Transparency

As a report owner, you may be responsible for communicating data to analysts, decision-makers, and business stakeholders. After completing your own validation, it is important to use the data with confidence so you can realize the value of tyGraph insights.

We want to be transparent about how data is collected and calculated so you can understand where differences may come from and make informed decisions.

"After many discussions and tests, we can now report that the inconsistencies in the numbers (comparing TyGraph Pages and SharePoint Site Analytics) are caused by SharePoint Online. We called the pages using a script and compared the numbers. The numbers from TyGraph Pages were correct in the tests." ~ tyGraph customer