WASP 1.31.2 Release

Dave Renouf — Wed, 27 Jan 2010 18:42:41 +0000

-Fixed an issue with the crawler in some conditions
-Fixed an issue with bad robot.txt and sitemap.xml
-Fixed an issue with illegal character in tag attribute

WASP 1.30.14 Released

Dave Renouf — Thu, 21 Jan 2010 18:14:48 +0000

We just released a new version of WASP. Please update from the main download link.

New features:

Detection: e-Visit

Detection: Survey Monkey

Detection: Survey Gizmo

Detection: Cobalt

Detection: Audience Science

Detection: LinkStorm

Detection: Blue Lithium

Better iPerceptions detections

Fixes an issue with the sidebar width

WASP Pro replaced by WASP Market Reasearch

Dave Renouf — Mon, 11 Jan 2010 15:10:28 +0000

To better satisfy customer demands, we have decided to Merge WASP Pro and WASP Market Research. Additionally, the price of WASP Market Research is now at the level of Pro, $699 instead of $999.

This is great news for our customers because they now get all the benefit of Market Research for the price of Pro, and the typical Pro user will now benefit from all the Market Research features.

WASP 1.30.10 release

Dave Renouf — Wed, 06 Jan 2010 16:39:40 +0000

Please update to version 1.30.10 as it fixes some minor issues:

-Fixed an issue with the internal DB

You can update from our download page at: http://webanalyticssolutionprofiler.câ€¦

Tracking tool diagnostics

Dave Renouf — Tue, 05 Jan 2010 18:12:55 +0000

We received this email a while ago and recently received more information. I thought it would be appropriate to share some of the insight that came out of it

—————————————————————————————-

Greetings,

Iâ€™m Matteo , developer in xxxxxx.com.

Iâ€™m currently developing a tracking system for the site using WASP as main tool for checking and testing, and Iâ€™m facing a strange problem:

in some cases, when I try to track forms in a onSubmit event handler, Â I get WASP displaying correctly the data I want to track, but no packet is sent to the tracking system.

I know that this is an implementation issue, but I expected WASP to show nothing if the packets are not sent.

Can you please provide me with some detail about how does WASP capture tracking packets?

I really like the tool, and Iâ€™d like to keep using it, but Â I really have to know that it is reliable enough.

Thanks for your time and for assistance

—————————————————————————————-
Matteo confirm Wasp shows the data is generated by the tracker but he does not see it on the receiving end. He goes along and give more detail in the next email.
—————————————————————————————-

The problem, in more detail, is the following:

Iâ€™m using WASP along with firebug (that has a good packet sniffing feature).

I cannot see the image request with the sniffer but WASP actually shows me the tracking. In all the other cases the packets are shown, and I can see the collected data on the tracking system side, so Iâ€™m sure Iâ€™m tracking on the correct ID.

You told that WASP watches for packets, as I supposed. This is the reason of my last email: I still cannot figure out what is happening. Probably, as you said, is a problem involving the implementation and the particular environment.

Thanks anyway, if I figure out whatâ€™s going on Iâ€™ll let you know immediately.

Matteo

—————————————————————————————-

He also does not see anything with Firebug but confirms he is using the proper ID for tracking.Â Recently, we got the resolution from Matteo:

—————————————————————————————-

The problem was the related to NS_BINDING_ABORTED error code (as seen in HttpFox).

Probably this is what is happening:

Firebug is smart enough (or not smart enough, depending on your point of view) to hide all the ajax call that will never come back with a response.

This can happen if you send out an async call, and then quickly tell the browser to change web page (e.g. all the events with a page change, like link clicks).

WASP shows the packet, and this seems to be the right behavior. We could say that, in this strange case, we can be sure to being trying to track the event (WASP shows it) but we cannot be sure to actually track it (we cannot wait for the tracking system response, due to user experience constraints).

Hope this is all (and hope this is what is really happening)

Thanks for all, and have a happy new year

Matteo

—————————————————————————————-

This means, NS_BINDING_ABORTED cancels the async call back and the analytics server did not succeed. Due to the page being changed too quickly, the async connection was killed in the process.

Firebug Â did not display the call at all making it hard to see what was going on.

WASP was properly showing the tracking code being executed and sent to Google Analytics by the client’s browser but didnâ€™t show the error code of the aborted connection. Itâ€™s also the fastest and most convenient way to confirm itâ€™s working properly

HTTP Fox, being a more technical analysis of network traffic, was properly showing all the connections and status codes. However, you need greater technical skills to use it and itâ€™s a little more tedious to use.

WASP 1.30.8 release

Dave Renouf — Mon, 04 Jan 2010 20:54:12 +0000

Please update to version 1.30.8 as it fixes some minor issues:

-Fixes an issue with the license in relation to the date
-Fixes some other minor issues

You can do a manual update from our download page at: http://webanalyticssolutionprofiler.c…

WASP Blog » 2010 » January

WASP 1.31.2 Release

WASP 1.30.14 Released

WASP Pro replaced by WASP Market Reasearch

WASP 1.30.10 release

Tracking tool diagnostics

WASP 1.30.8 release