Tag all your pages!First and foremost, we need to make sure all pages are tagged. Obvious isn't it?
What strikes me when beginning with a new client is how bad their web analytics implementation is. Missing tags is the #1 problem to look into. Sadly, the area that are left out are transactional areas: the outcomes! Why?
- It's more complex to tag transactions beyond the mere "page view" tags
- Content areas are often rendered out of templates, transactions require case by case tagging to be implemented
- Transactions are often under the realm of IT and changing them implies "negotiation" for resources, timely delivery, tests and answering any security considerations.
- In some cases, transactions are on a different host and even a different technology altogether
Because WASP blends itself into your browsing session, you will be able to go into any area of your site and make sure the tags are correctly implemented, even checking if specific parameters are being set correctly: custom variables, events, segmentation, etc.
Simply put, I'm from the school who think quality assurance of transactions can hardly be automated. You have to define test scenarios and diligently go through them not only to make sure the transaction work as expected and provides the appropriate results, but also to make sure you are measuring them correctly.
Coming up in WASPThe next release of WASP will include a couple of long awaited features:
- Site crawl*: from any page, launch a recursive crawl of all pages on that same site.
- List of links to parse*: already have a list of URL you would like to scan? Simply open the file and WASP will visit all of them and report back the results.
You will also get two ways of viewing the information:
- Web analytics implement view: what's currently shown by WASP
- Web analyst view*: showing simplified and plain English information about the tags found on that page.
* Those features will be part of an advanced version of WASP available on a subscription base/purchase only.