We have recently created a new Chrome Extension to check if a particular goal is firing or not. Currently it supports 7 testing tools. The plan is to gradually increase the number of A/B testing tools to help marketers, CRO consutlants, QA engineers, and developers to QA metrics.
But why this is important?
Well - first of all, if your metrics are not firing as expected, how are you going to analyze the results of your tests? In simple terms, there is no point of running an experiment if you can't measure the performance - whether it is a button click, pageview goal or transactional metrics.
The other reasion for making sure that the metrics are working correctly up front is so that you don't lose out the days of testing - only to find at a later stage that some of them were not working as expected.
We all know that in simple terms, Conversion Rate Optimisaiton is making changes to improve specific KPIs. If you are not making sure that the metrics are being tracked properly - what's the point!
Key takeaway - QA your metrics before you launch the tests!
