How to Interpret SharePoint Audit Log Visitors and Object IDs
Question details
The user needs to determine whether SharePoint audit log entries that show a visitor and an object ID, such as a site icon or image, represent a genuine page visit or only background resource access.

- Product
- Microsoft SharePoint / Microsoft 365 unified audit log
- Device & OS
- not provided
- Scenario
- A user reviews SharePoint audit data and sees a user account only once or twice, sometimes with a site icon or image object ID, and wants to avoid overcounting these as real site visits.
- Observed behavior
- Audit records show users only once or twice, sometimes associated with a site icon or another image object rather than a viewed page.
Before interpreting records, confirm that audit logging is enabled in the Microsoft 365 compliance center or Microsoft Purview compliance portal and that you have permission to search the unified audit log. Gather the operation, accessed URL, object type, timestamp, user agent, and related event entries for the records you want to verify.
Correlate Microsoft 365 unified audit log fields before counting SharePoint visitors
Use this method when you need to confirm whether a SharePoint audit record represents a real page view or a background request for a site icon, thumbnail, or other resource.
SharePoint audit logs can include requests for icons, thumbnails, and other supporting resources. These background requests may create activity records without proving that the user opened or viewed the site, so a single record is not enough to count a unique visitor.
Sign in to the Microsoft 365 compliance center or Microsoft Purview compliance portal, go to Audit, and select Search. Set the date range and workload to SharePoint to focus on the relevant records.
Search for the user account and object ID shown in the audit record, then review the Operation field and the accessed URL. Look for operations such as FileAccessed, PageViewed, or icon and image requests rather than treating all rows as page visits.
Open the record details and note whether the object is a site icon, thumbnail, image, or actual page. Check the user agent and timestamp to see whether the request came from a browser session, a background service, or an automated process.
Search for other audit entries for the same user and IP address around the same timestamp. A genuine site visit usually includes a series of page or file events, while isolated icon-only access is likely a background resource request.

Open, edit, and share Office documents without SharePoint audit log complexity
WPS Office is a free, lightweight Microsoft Office alternative that lets you open, edit, and share Word, Excel, and PowerPoint files with strong format compatibility, a familiar ribbon interface, and seamless migration. When you prefer not to rely on SharePoint audit logs for everyday document work, WPS Office gives you a simpler path for file handling and collaboration.

Frequently Asked Questions
Does an audit record with a site icon mean a user actually viewed the SharePoint site?
Not necessarily. A site icon or thumbnail request can be generated when a user's SharePoint start page displays the icon, without direct site access. Review the accessed URL, operation, object type, and related events before counting it as a visit.
Which audit log fields should I check before counting a unique SharePoint visitor?
Check the operation, accessed URL, object type, timestamp, user agent, and related events. In the Microsoft 365 compliance center or Microsoft Purview compliance portal, open Audit > Search and inspect the record details for these fields.
Where do I search the Microsoft 365 unified audit log for SharePoint activity?
Go to the Microsoft 365 compliance center or Microsoft Purview compliance portal, select Audit, and use the Search tool. Set the date range and workload to SharePoint, then search by user, operation, or object ID.
Can background requests for icons or thumbnails create SharePoint audit records?
Yes. Requests for icons, thumbnails, and other supporting resources can create activity entries even when a user does not open the site, which is why you should correlate multiple events before counting visits.




