OWA 1.5.5 is available. 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.
See the release notes for more details.
Version 1.4.0 is now available. To see the full list of features, changes and bugs fixed in this release see the 1.4.0 release notes.
Major features of this release include:
- Conversion Goal Tracking – define and track up to 15 conversion goals per web site.
- Goal Funnels – visualize the set of steps (or funnel) that users experience before hitting your goals.
- Campaign Tracking – add campaign tracking parameters to your inbound links and see how effective your traffic driving efforts are.
- E-commerce Tracking – track and report on revenue and products purchased.
- First Party Cookies – track and report on an unlimited number of web sites from a single OWA instance.
- 60+ new metrics – all accessible via the data export API.
- 20+ new dimensions – all accessible via the data export API.
- 10+ new standard reports.
- Clustered Deployment – deploy OWA across a cluster or tier of servers for better redundancy and scalability.
See the OWA wiki for the latest documentation, and please join the OWA community and file tickets for any bugs or oddities that you find.
Also, support open source web analytics by spreading the word about this release and OWA in general. Tweet, blog, smoke signals, whatever. The more we can get the word out that there is a robust open source alternative to commercial web analytics services/software, the better OWA will become.
And lastly, a big thanks to everyone that contributed to this release by filing tickets, writing code, and offering up an instance or two for debugging purposes. We had a record number of submissions and contributions to the 1.4.0 release milestone.
Next up is release 1.5.0 which you can view development plans for here.
The good folks over at ClickTake have posted a great piece on how eye tracking compares to mouse tracking in terms of analyzing web page usability.
Mouse tracking differs from eye tracking in that a user’s mouse movements are recorded instead of their eye movements as they interact with a web page. The best way to think about mouse tracking is that it turns your web pages into a one way mirror through which you can literally watch how your users interact with the page.
When it comes to usability work, mouse tracking often times is far more effective than eye-tracking because:
- It can be performed on live users of your site, instead of simulated in a lab.
- It doesn’t require specialized/expensive labs, recruitment efforts, consultants, or equipment
- If you use Open Web Analytics you can do it for FREE and get started immediately. No waiting.
Have you ever debated a design decision with a client or colleague only to wind up agreeing to disagree? Well, if you were recording mouse movements you’d be able to back up or disprove your hypothesis with real interaction data in minutes. Heck, you’d even be able to show live recordings as examples.
Here are some of the important usability questions that mouse/key-press tracking can answer:
- Do users ever scroll the web page? If so, how far exactly?
- Do users ever click on a particular element of the page?
- How long do people spend interacting with the web page?
- Do users use any keyboard short cuts to navigate the page?
General web analytics tools can’t answer these questions because they do not track what happens after a web page loads.
Open Web Analytics comes with built-in support for tracking a user’s entire “in-page” experience including mouse movements, scrolling, and key-presses. We call the entire stream of in-page events a “Domstream” and allow you to record them for all of your visitors or just a sample percentage that you define.
Watching Domstream recordings is like watching a reality TV show – once you start watching you can’t stop.
Because OWA is free open source software there is no limit on the number of Domstreams you can record. This means that if you have a large web site with lots of different page types you won’t bump up against the limits that commercial tools put in place or run out of budget as you record more streams or do A/B tests.
To see how OWA’s Domstreams work check out the OWA demo site and start tracking your user’s Domstreams. We just did 😉