After months of analysis and early tests, I was able to find a pattern common to all solutions that makes uses of JavaScript tags.
Contrary to most other ways of detecting the presence of a web analytics solution, WASP looks at the object level, not the source code.
It also act like a proxy and detects the HTTP Get and the HTTP Response patterns.
Once the right "signature" is identified, this method increases the confidence level and can catch any website using a specific solution.
WASP is able to detect even the most obscure tracking systems as long as it fits the right behavior and it's signature is known.
Leveraging the browser
WASP being a browser extension, it is able to tightly match a real user behavior and account for broken JavaScript and any unpredictable behavior.
Running on the client-side also allows you to use WASP on intranets & extranets safely. Especially when testing on-line transactions, WASP is the only solution that can really be used to test complex transactional scenarios.
Automation
The latest release of WASP includes a "crawl from here" and "open file" features used to automate some of the most common tasks.
In both cases, WASP builds a list of links and waits for the complete page load before moving on to the other link.
At the end of the process, a report is automatically generated. Note also that a report can be generated any time simply by sing the "show log" feature.
