<< Frequently Asked Questions Install WASP for Firefox

The challenges of JavaScript tagging

In my experiences implementing various web analytics solutions, I found that tweaking and checking if the tracking code matches our requirements might sometimes become a significant part of the technical implementation effort.

The simple tag debugger (also sometimes called web beacon) provided by the web analytics vendors are too simple and not as convenient as WASP.

WASP aims to tackle the most common errors and problems web implementation specialists are faced with:

Feature Free  Pro1 Future
Basic information
Show tags "in context" of your browsing session.
Make sure all pages are tagged.2
Make sure data is being captured correctly.
Show first or 3rd party cookies.
Page names should be unique and significant.2
Work on intranets/extranets/development sites.
Crawling
"Crawl from here" feature.2
Crawl using given list of URLs.2
Crawl using sitemap.2
Advanced inclusion/exclusion rules for crawling.
Follow (or not) robots.txt rules.
Show itself as a crawler (for exclusion rules from stats)
Reporting
CSV report output.
Enhanced report output.
Advanced quality assurance
Validate tags positionning within the page.
Validate/avoid Javascript wrapped links.
Validate/avoid redirects links.
Highlight overwritten values.
Wrong data types or length of tags.
Vendor script version.
Domain of values for custom variables.
Work with Flash, Flex, RIA, RSS, videos etc.

The feature list was initially inspired from a post by web analytics guru Avinash Kaushik: "Web Analytics Technical Implementation Best Practices. (JavaScript Tags)".

  1. Features scheduled for release in the Pro version of WASP. However, they are currently available with some limitations in the Free version.
  2. The crawling feature in the Free version is limited to 100 pages.

If you use WASP for profesional purposes,
please consider a contribution.
Feedback Form