CardioLog - the Ultimate Alternative for SharePoint Google Analytics
Have you ever tried implementing Google Analytics with SharePoint?
CardioLog, unlike Google analytics, is specifically designed for SharePoint. It provides true and insightful information about your SharePoint implementation, based on the structure of your SharePoint hierarchy and content.
Ownership of Business Data
Usage data for company intranets contains information such as employee names, employee roles, document names, and more. Being an in-house hosted solution, CardioLog stores all analytic data within the organization, and thus ensures data privacy.
Ownership of the Tracking Code
CardioLog enables full control over the JavaScript tracking code - allowing the elimination and addition of monitoring features - according to business needs and privacy policy.
Single Reports for Multiple Websites
CardioLog's reports can aggregate data for multiple websites - encompassing different domains. For example, in a Microsoft SharePoint portal, a single "Page Views" report can display aggregated data for all web sites in a farm.
Sub-sites Analysis (Enhanced Content Drilldown)
The reporting features and dashboards can be applied to sub-sites, sub-directories, single web pages, documents, or any other level of the portal hierarchy. This is achievable due to CardioLog's familiarity with the portal structure (through portal adaptors).
Custom Aggregation of Usage Data
Reports can provide aggregated data for any combination of sites and directories. For example, in a Microsoft SharePoint portal, a single "Page Views" report can provide usage data for a selection of separated sub-sites. This enables content owners to view usage reports for the content they own, regardless of where their content resides.
Report-Filtering by Page Metadata
Due to its familiarity with the website structure (through portal adaptors), CardioLog provides the capability to filter usage data according to page metadata. For example, in a Microsoft SharePoint portal, reports can be filtered by page type, such as team site, blogs, lists, list-items, documents, etc.
Authenticated Visitors Reports
In websites with authenticated visitors, CardioLog provides report filtering by visitor attributes, such as name, group, gender, department, etc. This is achievable by CardioLog's off-the-shelf integration with Active Directory, and through integration with custom data sources. Report users can drill down on specific visitors, to see their personal usage behavior.
Capturing Document Usage
CardioLog provides document usage data off-the-shelf. Clicks on document links within a website are all captured and analyzed.
Administrative Reports
Portal managers can easily see how fast their portal is growing (numbr of items), who are the top content contributors and what is the magnitude of editorial actions performed throughout the portal (additions, deletions, modifications, etc.).
Unused Pages Reports
Thanks to its familiarity with the portal structure, CardioLog provides lists of unused directories (sub-sites), pages and documents.
External Destinations Reports
CardioLog tracks visitors who click on links to external websites, and provides reports for this action.
Content Areas Reports
CardioLog provides reports about the usage of various content areas in the pages, such as toolbars, menus, headers, footers, etc.
Report Permissions
Through its seamless integration with Active Directory, CardioLog provides the ability to set Report permission levels to users and groups within the organization.
Report Distribution
By setting read permissions to reports, it is possible to control their distribution throughout the organization. Reports can be automatically emailed, exported to web parts, or launched directly from portal pages.
Report Customization and API
One of CardioLog's most prominent features is its ease of customization:
By customizing the JavaScript tracking code, it is possible to track any type of page interaction. CardioLog's API provides a mechanism of creating custom reports, and enables access report data from external resources.
History Data - Importing IIS Log Files
In order to view usage reports for the period prior to the implementation of the CardioLog tracking agent, CardioLog includes an IIS log import feature. The IIS log entries are available for reporting after they are processed, analyzed and linked to the structure of the portal.
Contact us in order to learn more about our SharePoint analytics solution.
Learn More
|
