When we discuss Web Analytics, we talk about Implementation, Reporting/Analysis and offering recommendations on how to improve a website. QA/Testing is something which is often put in the backburner. Companies focus on the Analysis of data but don’t usually concentrate on the validity of data. This often leads to reimplementation of code and the data being inaccurate. This is not good news for companies tagging their website with Web Analytics code and paying for Implementation and Analysis. This article at a high level explains some of the things which may help improve the Web Analytics QA process of organizations. These are some of the points which can be useful for Web Analysts looking to setup a Web Analytics QA process.
1) Spread the word: Spread awareness about Web Analytics QA benefits to your Manager/Stakeholders specifying how thorough Web Analytics QA can help them save cost in the future. For e.g. you can tell them that proper Web Analytics of the code/data can help companies reduce repetitive fixes/patches of code or resultant skewness of numbers while performing Analysis.
2) Include in Release cycles: Try to incorporate Web Analytics QA in the weekly/monthly release cycles by bringing into perspective all stakeholders from QA Analysts, Developers to Program/Project Managers. It might involve lot of patience, persistence and convincing but it is worth the time. Come up with a process document/Flow chart depicting the QA process and share it with the concerned teams.
3) Performing QA/Knowledge Transfer: Once the Web Analytics QA process has been approved, start off by performing QA yourself and transition this responsibility to the resident QA Analysts as a Web Analyst should be involved more with Analysis/client interaction etc. Sharing tutorials about different Web Analytics tools might be helpful to pass on to the QA Analyst.
4) Create a reusable Test document: Once the training has been imparted, the QA Analyst or Web Analyst can create a test document to perform Web Analytics testing. The QA document should leverage a Packet Sniffer (explained in my previous article) and should also validate data in the Web Analytics tool. For e.g. the below screenshot makes use of conditional formatting to color incorrect values (not matching requirement) as Red and correct values as green. This is a screenshot taken from a QA document which I created in one of my assignments where we were QA’ing Omniture data. This document helps in validating the code as well as checking the output and should be reusable.
Hope you like this post. Please comment in case you agree/disagree with my analogy about Web Analytics QA process being an integral part of a Web Analytics assignment.