Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

 

System Architecture

CardioLog Analytics SaaS's architecture is built upon four main layers:

  1. Data Source - This layer includes all the main sources that CardioLog Analytics SaaS can track, including Office 365, SharePoint 2013, 2016 and Yammer.  
  2. Data Capturing - This layer combines both tracking of user behavior with data pulled from various APIs. 
    The user behavior is captured by a JavaScript code, which allows for tracking all kinds of information including what pages users viewed and what they searched for. 
    This data is combined with information that we get from SharePoint and Yammer APIs, like portal content, structure, users, groups, profile attributes and much more. 
  3. Data Processing - Once data is captured, there is a mechanism that processes the data and combines it into analytics that are displayed in reports. 
  4. Data Visualization - The processed information is displayed at the Data Visualization level. The data is visualized through Power BI, a powerful visualization tool provided by Microsoft.

 

CardioLog Analytics SaaS Schematic Overview


CardioLog Analytics SaaS Architecture Diagram


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 APIs, SharePoint user profiles and Active Directory) 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: 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.

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

 

 


  • No labels