Web Analytics. Open Source.
Easy, Open, Web Analytics.
OWA can be downloaded as a tarball or by checking it out of it’s Subversion repository. If you would like to see a demo of OWA before you download, head over to the Demo & Examples site.
Download a Tarball
To download the latest releases of OWA, point your web browser at http://downloads.openwebanalytics.com or click the button below:
Subversion access to the OWA source code is available at http://svn.openwebanalytics.com/owa.
For the latest code, tell your SVN client to:
svn co http://svn.openwebanalytics.com/owa/trunk
For a specific release of OWA, choose the release you want from the tags directory:
Help and support for OWA is provided by it’s community of authors, users, and contributors. To get help take a look at one of the resources below.
Demo & Examples
You can find a full demo of OWA along with development examples over at the Demo & Examples site.
The OWA wiki contains all end user and developer documentation. To access the wiki point your web browser at:
The OWA support forums are a great place to ask for help and get answers from other OWA users. Whether you are troubleshooting an installation or just have a quick question about how something works, you will definitely want to check out the forums. The forums can be accessed at:
Bug Reporting & Feature Requests
To report a bug, check the status of OWA development, or even to log a feature request, visit OWA’s tracking system at: http://trac.openwebanalytics.com.
If you need realtime support or are familiar enough with OWA to provide support to others, then join the #owa channel on IRC (freenode). There is usually an OWA guru or two hanging out there.
Below are some screenshots of OWA’s reports, tools, and visualizations. If you’d like to see a full demo of OWA, head on over to the Demo & Examples site.
Anil blogs his response to the question: “Is Web Analytics Dead?” and concludes that no, it’s just maturing into a holistic platform for gaining a 360 degree view of the customer.
Personally I think companies are still a long way from having that 360 degree view of their customers due to the fact that web analytics data is mostly stored in a disonnected or outsourced silos and systems.
There are many reasons for this, but I blame the lack of strong open source web analytics efforts like the ones that exist around other areas of web application development (i.e. web servers, or content management, or databases, or tagging, etc.).
Think about it. When a developer sets out to build a new web application for their company, they don’t spend any time writing code to serve the web pages. Instead they use an open source web server like Apache and rely on its features. In fact, frameworks like Ruby On rails or the Zend framework now allow the developer to bypass spending time on a whole lot of lower level application code and base services like authentication and database access.
However, when it comes to web analytics, developers have historically been out of luck when they reached for the an open source solution to the problem. This has put their company on a collision course with outsourcing their web analytics and data management to a 3rd party.
Working with a 3rd party service provider allows a company to put a lot of base capabilities in place quickly, but can begin to cause problems when it comes time to link web analytics data to detailed customer records stored in internal databases.
Right now that is hard to do for most companies that have outsourced their web analytics to a 3rd party service provider because that service provider either does not provide access to the raw event level data, or they set their own tracking cookie with their own unique visitor ids.
We are hoping to reverse this trend by providing developers and companies with a full featured toolkit that they can use to quickly add web analytics capabilities to their own web applications.
Our goal is to ultimately provide plugin level integration for OWA with all the major application frameworks that developers are using today. For example, if you are developing an PHP based web application or using WordPress or MediaWiki then you can use OWA to add web analytics functionality to your application in minutes.
If this sounds familiar to you or your situation, then you might want to give OWA a try.
This release candidate contains:
- Introduces a “Digg-like” Spy report that allows for a real-time, continual, AJAX update of new site visitors – perfect for that plasma screen in your reception area…
Release candidate fixes a few bugs including:
- Referrers now tracked properly when tracking a second domain under a WordPress Install.
- Fixed bug in first hit processor that was causing fatal error under certain php configurations.
- Enabled Google Earth KML export to be saved as a file with the proper .kml extension.
- Refactored development error logger to be resiliant to cases when does not have permission to write to its logs directory.
To upgrade just copy the new files over the old ones.
Quick bug fix release for a fatal error that happens under PHP4 when users are behind an http proxy.
This Release Candidate fixes some bugs and refactors a few things. Includes:
- Re-factored OWA’s cookies to set a per site cookie to store session and last request timestamp. A cross site visitor cookie is still used as the default. You may see some strangeness when you upgrade around new sessions getting created for users that are already within the 30 minute session window.
- Includes a fix for apache redirects that cause php to set the wrong cookie domain.
- Adds a config file setting for logging all php errors to OWA’s error.txt file
This is a release candidate, so please give it a try and look for anything odd.
To upgrade just copy the new files over the old ones.
Bug fix release. Includes:
- Numerous fixes to incoming link snippet creation
- Refactoring of the global configuration object including adding a proper update() and setSetting() methods that can be used to easily add settings to the database.
- Fixed case where inproperly formated HTML was causing the dashboard layout to trash the WordPress footer
To upgrade just copy the new files over your old ones.
This is a security bug fix release. It is strongly recommended that you upgrade to this release.
The release fixes insecurities in the standalone installer among other things.
To upgrade, just copy the new files over your old ones.
This is a bug fix release. Fixes and features include:
- Fixed broken anchortext logging and report
- Fixed condition where referring page title was not being logged due to anchortext extraction method removing the title tag.
- Vastly improved the referring link snippet creation code. Snippets should now not contain CSS/HTML entitities.
- Added ability to track multiple wordpress blogs using the same instance of the OWA database by overriding the databse configuration in the owa-config.php file. See the wiki for more info.
To upgrade just replace your old files with the new ones. No database schema changes were made as part of this release.
A new report from CMS Watch suggests that the lack of an API or ability to integrate Google Analytics with other systems is an enterprise deployment deal breaker.
I couldn’t agree more, but think that this is really the case for all the Web analytics service providers. Most hosted web analytics solutions are essentially integrated at the presentation layer (i.e. pixel tracking) making database access or code extension off limits to users. This makes it impossible to extend these systems feature wise on your own timeline.
Companies that need a more custom solution but do not want to start from scratch will hopefully find Open Web Analytics to be a welcome alternative.
OWA’s asynchronous event processing model allows it to be deployed in high volume enterprise scenarios and the plugin/module framework makes adding features pretty straight forward.
There is still a lot more to do, but give OWA a whirl if you are looking for an alternative to the commercial services or want really tight integration with your applications.