CardioLog Analytics vs. Office 365 Reports

Advantages of CardioLog Analytics over the Office 365 Out of the Box Reports

  • Product: while out-of-the-box reports are shaped as a broad dashboarding tool and is focused on presenting a high level adoption matrix of Office 365 apps, including SharePoint Online, CardioLog Analytics on the contrary, is designed as a dedicated Analytics solution for SharePoint / Office 365 and Social platforms (i.e., Yammer, Sitrion and more). As such, it provides in-depth analytics and insights on the portal and particularly its user behavior.
  • Value: whereas the out-of-the-box Office 365 reports can help users see where adoption issues exist (which groups, sites or users have low adoption), CardioLog Analytics provides this information and much more. The insights CardioLog Analytics provides enable users to take action, thus helping them increase adoption and improve the portal overall. In addition, it offers additional metrics that users can leverage to ease migration and increase engagement.
  • Technology: from a technological perspective, CardioLog Analytics offers a unique JavaScript client that resides in the browser of each portal’s user, as well as wide API calls that collect and analyze the portal structure and changes, constructing accurate and valuable reports and insights. The out-of-the-box reports base their data on existing logs and files, and simply presents them through the dashboard.

Main Differentiations

CardioLog Analytics enables you to filter reports or aggregate data flexibly based on a variety of information

  1. Portal Tree –  CardioLog Analytics generates a tree view of the portal which makes it easy to filter any report by the part of the portal you are interested in, whether it’s a site collection, subsite, a list or a library, a particular item or any combination. Using the tree structure, you can aggregate the usage data by any part of the portal – so you can get statistics not only per URL, but also see what the total statistics are for an entire site, list or library.
  2. User data from any source – segment and filter any report based on user information coming from Active Directory, SharePoint User Profiles (including custom attributes), SharePoint groups, Yammer or any other data source.
  3. Content information and metadata – filter any report based on any content attributes, such as:
  • The content type (including user-created types)
  • Owner, or owner’s user attributes (department, groups, etc)
  • File extension
  • Size
  • Last activity
  • Creation date
  • Metadata fields


1. Behavioral reports – learn how users behave and navigate in the portal to improve their usage experience. For example:

  • Learn which content is most popular, what content gets viewed the most and by which users
  • Learn what are the most common navigation paths to make those paths easier
  • How much time do users spend on each page or in general in the portal, to see which users and groups are more engaged (and which require more help) and which content is more engaging
  • What are  the top landing pages and what was the user behavior when coming from each landing page
  • What are the common exit pages and what’s the exit rate per page
  • From which page users got to any given page
  • Which promotions got most entries
  • What times of the day and which days of the week users usually spend time in the portal

2. Social activity – Learn what content is liked or rated the most can give you further insights to what users are interested in, rather than just viewing which content is viewed the most. You can also learn who the influential users are and which users collaborate with each other by learning about users followers.

3. Search – Learn about the trends of using search overtime. How well is search working, what are the popular search phrases and do they yield good results, which result clicks users usaully click on.

4. Technology – Learn which devices, operating systems and browsers your portal users use the most to make sure your portal is compatible with the ones that are used the most. See how common the usgae of common devices and tablets are in your portal. Drill down to the version level of each browser type and operating system, and segment any report based on the users technology to learn more about the behavior of each technology segment.

5. Geographical location – Learn where users browse the portal from, based on their IP address or based on their user attributes, allowing you to drill down to the city level. Filter or segment any report based on geographical location to learn about the users behavior from the different location, which locations are most active and where users spend most of their time in the portal – in the office or on the go.

6. Reports on external users behavior – Filter any report to show information only on external users, to learn about their behavior in the portal, which content they are exposed to and how common they visit the portal

7. External links – Learn which external links are used the most, which pages contain the most popular links and from which page users navigated to each external link.

8. Page loading performance – Pages that take a long time to load affect the user experience of the portal and waste your users time. Using Javascript, CardioLog Analytics measures how long it takes for every page to be fully visible to users so you can identify your slow loading pages. For each page that a user views, CardioLog Analytics tracks how much time it took for that page to load. This way you can see exactly the users experience was and see how it affected their behavior.

9. Video tracking – Learn which videos are most popular in the portal, where users view them and which users view them.  Video tracking also allows you to understand which percentage of a video usually gets watched, where users usually pause and how many users watched the video more than once.

Data Granularity and Retention

  1. Data granularity – view  reports down to the event level of any user, including timestamp, URLs visited, time spent on each page, navigation paths, geographical location, device and browser information and more.
  2. Data retention – CardioLog Analytics users can choose how much history data they want to obtain

Take Action based on Analytics

CardioLog Engage allows you to harness the data collected and analyzed by CardioLog Analytics to take useful actions in your portal. The data collected can trigger any action, such as:

Show a message to users based on their behavior

  • Send an email to users who haven’t logged in to the portal in a while
  • Show a pop up message to users who have navigated through more than a certain amount of pages or spent more than a certain amount of time in the portal
  • Who are about to close to the page and more

Trigger an action based on the content the user is viewing or the user’s segment

  • Pop a survey to users who are on a search results page
  • To users who belong to a certain department or use a specific device
  • Display a message that a site was moved on any page that is part of that site or even redirect users to the new site, and more

Get feedback – get first hand feedback from your users by adding surveys or rating buttons

  • Add a question “was this page helpful” to the bottom of the page
  • Add any multi-answer or open text question to any page that can be shown based on rules that you define