Over the years as SharePoint has grown their marketshare in the CMS space and by number of implementations we learned a lot of the common uses of SharePoint. Some are: 1. Because of the inherent requirement of authentication for SharePoint access it provides you a wealth of valuable data such as unique visitor tracking. 2. Most organizations will choose not to use a hosted solution for their intranet sites due to security concerns of exposing company information to the outside. In this case Webtrends is a viable option. 3.One of the many factors that inspired the development of Mergence SP Analytics is the limitation of native analytics to SharePoint currently; our customers wanted more….
Some of reporting features clients wanted were as follows: Unique Users What areas of the site did they access What are the most common paths on the intranet – Path Analysis Most viewed aspects or areas of the intranet Onsite Search results such as most searched terms, terms not found, etc… Document check-outs, downloads, edits
Significant to our clients was also Community Engagement such as: Understanding the interactions between individuals Across departments – for example, a sales manager would want to know which sales brochures are useful to his or her team; an HR Manager would like to know how many employees visited the new Benefits subsite; someone in Operations would want to know if the new invoice form is being used and by whom; Also how company-wide the organization is using SP – are the company announcements drawing the right traffic, is the president’s message being viewed by the employees, are departments improving workflow?
So if you look at SP and see how documents are created: A user requests information from the SP server, that visit gets recorded in the logfile and that allows to create web analytics reporting. But this becomes more challenging for more in-depth reporting such as Web Parts, breadcrumbs, subsites, and particularly document actions like check-out, modifications. For this, you’ll need to modify the web analytics tag and some key SP files that are absolutely untouchable – these files are called core.js and cannot be altered. If you do MS will discontinue support for the product. So our approach is to keep that file, core.js fully intact and so we’ve developed Mergence SP Analytics which bridges the analytics and SP and instead modifies standard SP files, the Masterpages and yet still delivers the same functionality.
We’ve designed Mergence SP Analytics to be compatible with: WT, Adobe and GA integrated with SP with plans for other CMS solutions
Some of the Mergence SP Analytics advantages are: No need to make changes to the critical core.js files or even the WA tag. As mentioned it would adversely affect your support with Microsoft. For those that have SP hosted services we can support easily since core.js will not be touched. And very significantly, the reporting available is compelling per the next slide.
So with Mergence SP Analytics you can report: Company intranet sites or even subsites Exact users and IDs that access SP How search is being used How your users traverse SP Document activity Web Parts
Here are a couple of screenshots before the demo: Content Groups and Content Sub-groups Web Parts by User Breadcrumbs by User To extend the capabilities of Mergence SharePoint Analytics we’ve developed an app called VHED which Eric will discuss.
Nad Balata: Product Manager Eric Tobias: Director, Analytics Services Questions? Ask @unilytics via Twitter by using #UnilyticsSP