Analytics support

More features

There are website analytics packages to suit a range of budgets and requirements, one of which will meet the precise needs of your organisation. The companies that produce this software invest millions of pounds every year in developing their products. Rather than compete with them, we integrate with them.

The two main types of solution available today consist of log crunchers and embedded JavaScript solutions. Both are supported by Contensis.

Log crunchers

Log crunchers simply read the log files created by the web server in question.

Contensis usually publishes to a Microsoft IIS Server, although we do have the ability to publish to any other web server of your choice including Apache, Sun, etc. Each of these web servers will have a built-in logging function.  As Contensis publishes pages, the statistics solution can be configured to look at the relevant log files.

Log crunchers are being used less but they are still, at present, a contender in the statistics marketplace.

JavaScript-based solutions

JavaScript-based statistics servers embed a piece of script or image into the web page. When the user visits the page the script is triggered, executing a HTTP request to your system of choice.

Because embedding JavaScript in templates or pages is fully supported, any of these packages, including Google Analytics, will work with Contensis.

Because most of our customers use either WebTrends or Google Analytics, we created standard functionality to support them. If you use either of these, you can add your unique code to the site config to automatically enable the statistics.

Get analytics reports in your Contensis dashboard

Simple statistics tracking

Although we do not provide a set of statistical reporting tools for websites in our core package, there is need to record some statistical information for the purpose of areas such as personalisation.

Contensis has the option to enable stats tracking and, once enabled, the system will record statistics to its internal databases of the visits to pages and content.

We can use this information to personalise user experience. One example would be a "what's hot" control. This could be placed on a user's dashboard and show the content that is most regularly visited. You could also change a user's features depending upon which email campaigns they have clicked through to.