Open Web Analytics

Open Web Analytics (OWA) provides web site owners and developers with easy ways to add web analytics to their sites using simple Javascript, PHP, or REST based APIs.

It is an alternative to other traffic analytics solutions like Piwiki or Google Analytics.

OWA comes with built-in support for tracking web sites made with popular content management frameworks such as WordPress and MediaWiki.

Features:

• Graphic Installer
• Login Protected Backend
• Track Multiple Web Sites
• Conversion Goals
• Admin Dashboard
• Custom Event Tracking
• E-commerce Support
• Goal Funnels
• Page Views, Visits, and Other Similar Stats
• Custom Variables
• Click Heatmaps
• DOM Click Tracking
• Mouse Movements (recording and playback)
• Reporting & Analysis
• Charts
• Data Export API
• Segmentation
• Command Line Interface
• Asynchronous Event Logging/Processing
• Distributed Event Processing
• Data Warehousing
• Object Caching
• Javascript Tracking Client
• PHP Tracking Client
• WordPress Plugin
• MediaWiki Plugin
• Drupal Support Through Third Party Plugins

What is new in this release:

• BUG:
• Security fix for remote queueing.
• FEATURE:
• Broke out remote event queuing into it's own module. See the [remote queueing] page for more infer on how to enable this feature.

What is new in version 1.5.5:

• This is required release addresses security vulnerabilities when running OWA under certain configurations of PHP.
• Also, the release contains a improved batch event queuing system that makes it easier to manage a multiple server installation of OWA.

What is new in version 1.5.4:

• New Feature:
• DoNotTrack support.

What is new in version 1.5.3:

• This maintenance release fixes a number of bugs in the 1.5.x series of releases.

What is new in version 1.5.2:

• This maintenance release fixes a few bugs including a possible race condition when installing via the WordPress plugin.

What is new in version 1.5.1:

• This maintenance release fixes a number of bugs and issues relating to site level access controls.

What is new in version 1.5.0:

• Custom Variables - it is now possible to set and store up to five custom properties on all tracking events (pageviews, sessions, clicks, action events, etc.). Custom variables can be set for a single tracking request, across all requests that make up a single session/visit, or across all visits for a single visitor.
• Segmentation - it is now possible to generate data result sets for a specific segment of your visitors. Segmentation is applied to the result set prior to any filtering or grouping functions - delivering a true segmented data set for you to work with. Segments can only be applied to result sets via the data access API as of this release.
• Live View - it is now possible to turn any reports into "live" dashboards that will continually update themselves as new tracking events occur.
• Result Set Filtering - filtering result sets has always been possible by applying constraints via the data access API but it is now possible for analysts to filter the data contained in any data table displayed on any report via the GUI.
• Lots More Metric and Dimension Combinations - the number of dimensions and metrics that can be combined to generate result sets has been greatly expanded in this release.
• Independent Tracking Modes - it is now possible to use only a subset of OWA's tracking modes. For example, you can now choose to just use OWA for tracking clicks and generating heatmaps, or for only recording and playing back mouse movements/dom streams, or even just use OWA for tracking site actions. Prior to this release you needed to track all page views and sessions in order to use any of the other tracking modes. Now you can choose to track whatever combination of tracking events that you want.
• IP Address Exclusion - it is now possible to exclude specific IP addresses for being tracked via the general configuration UI or via the new excluded_ips config setting.
• IP Address Anonymization - it is now possible to anonymize IP addresses by removing the last octet prior to storing them in the database. Anonymization can be controlled via the general configuration UI and the anonymize_ips config setting.
• 20+ new dimensions - lots of new dimensions have been added. See the release notes for the full list.

What is new in version 1.5.0 RC2:

• Custom Variables - it is now possible to set and store up to five custom properties on all tracking events (pageviews, sessions, clicks, action events, etc.). Custom variables can be set for a single tracking request, across all requests that make up a single session/visit, or across all requests for all visits. Custom variables can be set via both the php and Javascript trackers.
• Segmentation - it is now possible to generate data result sets for a segment of visitors. Segmentation is applied to the result set prior to any filtering or grouping function delivering a true segmented data set. Segments can only be applied to result sets via the data access API at this time.
• Live View - it is now possible to display live updates to data in all reports as new tracking events occur and are processes by OWA. Live view can be controlled by a switch at the top of all reports.
• Result Set Filtering - filtering result sets has always been possible by applying constraints via the data access API but now it is now possible for analysts to filter the data contained in any data table/grid displayed on any report via the GUI. Constraints can be made up of both metrics & dimensions.
• More Metric and Dimension Combinations - the number of dimensions and metrics that can be combined to generate result sets via the API and reports has been greatly expanded in this release. See the metric and dimension combinations page for more information.
• Independent Tracking Modes - it is now possible to use any of OWA's tracking methods independently of one another. Prior to this release if you wanted to track dom clicks (needed to generate heatmaps), dom streams, action events, or e-commerce transactions - you also needed to also track all page views and visits. As of this release you can simply use OWA for whatever kind of tracking you want enabling you to deploy instances that for example might e dedicated to only tracking dom clicks, or domstreams, or action events. See the tracking methods for the php or Javascript trackers for more information.
• IP Address Exclusion - it is now possible to exclude specific IP addresses for being tracked via the general configuration UI or via the new excluded_ips config setting.
• IP Address Anonymization - it is now possible to anonymize IP addresses by removing the last octet prior to storing them in the database. Anonymization can be controlled via the general configuration UI and the anonymize_ips config setting.