The CardioLog Scheduling Service includes the following components:

1. Usage Data Processing - Processes incoming tracking data from the Event Collector every hour.
2. Portal Tree Updates - Retrieves the structure of the portal (ie., Monitored environments). This structure is the basis for data aggregations.
3. Report Scheduling - Responsible for the automatic generation of all scheduled reports, and their distribution and publication.
4. Active Directory Updates - Retrieves the list of all users and groups directly from Active Directory, SharePoint or custom sources for use with visitor segmentation and other user targeted features.
5. User Categories Updates - Retrieves the list of custom user categories from Active Directory, SharePoint or custom sources for or use with visitor segmentation and other user targeted features.

Data Collected by CardioLog Analytics

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 databases, SharePoint APIs, SharePoint user profiles, Active Directory, IIS logs*) and some are the unique IP of CardioLog Analytics (such as the JavaScript tracking agent).

Data collected by CardioLog Analytics includes the following:

1. Page tagging: 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. Active Directory or SharePoint user profiles: User account name; user display name; email; and additional optional attributes such as department and location (configurable)
3. Social activity from SharePoint and other social networks such as Yammer and Sitrion: Ratings; likes; follows; comments; groups and group activity, etc.
4. Website tree service: Page ID; URL; title; content type; template; owner; editor; date created; date updated; size; and additional optional meta data fields.

To enable CardioLog Analytics to provide distinctive reports with exceptional value, the solution is required to collect, store and process more data and information than most generic analytic solutions.

The following events are collected via page tagging:

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
    

*History data is collected from IIS logs during the initial installation only 

 The Data Collection Process