Page History

...

In order to provide enhanced reports and meaningful insights to stakeholders to better understand and improve the business, the CardioLog Analytics solution collects, processes and stores data from various sources. Some of these sources are shared (such as the SharePoint Microsoft APIs, SharePoint user profiles and Microsoft Azure Active Directory) and some are the unique IP of CardioLog Analytics (such as the JavaScript tracking agent).

Please note that the JavaScript tracking agent relies on the following SharePoint objects in the SharePoint page model - spPageContextInfo and spClientContextInfo (which are included on all SharePoint pages by default) in order to collect information about the current user and page.

...

Data collected by CardioLog Analytics for SharePoint and Microsoft 365 apps (such as Teams, Yammer, OneDrive and Exchange Online) includes the following:

1. Page tagging: Page SharePoint page tagging (via JavaScript tracking agent): Usage information including page URL; query string; date and time; user ID; session ID; browser type and operating system; IP address; search terms; position of clicked search results; amount of time spent on a page; page loading time.
2. SharePoint portal tree structure (via Microsoft API): SharePoint content information including page ID; page URL; title; content type; template; owner; editor; date created; date updated; size; and additional optional metadata fields (configurable).
   
3. Azure Active Directory or SharePoint user profiles : User (via Microsoft API): User information including user account name; user principal name; user display name; email address; and additional optional attributes such as department and location (configurable)
4. Social activity from SharePoint and other social networks such as Yammer: RatingsSharePoint Social activity (via Microsoft API): Social activity information such as ratings; likes; follows; comments ; groups and group activity, etc.Website tree service: Page ID; URL; title; content type; template; etc.
5. Teams activity (via Microsoft API): Teams information including team name; type; owner; date created; members, and social activity information such as number of messages; replies; reactions; mentions; meetings; calls; apps used; device types used; content shared and channel messages content - optional (configurable)
6. Yammer activity (via Microsoft API): Yammer groups information including group name; group URL; date created, and social activity information such as number of messages; replies; likes; message excerpt etc.
7. OneDrive activity (via Microsoft API): OneDrive content information including file name; owner; editor; date created; date updated; size; and additional optional metadata fields.usage information such as number of creations; modifications; deletions; shares etc.
8. Exchange Online activity (via Microsoft API): Exchange usage information including email traffic; apps used; storage used; and email subject - optional (configurable)

An event is any action a user makes in the monitored environment.

The following events are collected via page tagging for SharePoint:

1. Page view
2. Document view/download
3. Page duration (time spent on page)
4. Page load time
5. Page interactions (such as scroll) - optional
6. External link click
7. Search
8. Search result click
9. Search result preview
10. Video interactions (such as play/auto play/pause/stop/seek/full screen/sound) - optional