Cross domain tracking has always been difficult to get right in Google Analytics - and it still remains a challenge. This audit guide will help you get on top of it.
Since GTM introduced an automatic way of tracking scroll depth in Google Analytics, there has been a proliferation of this tracking. In this post I explain why you should avoid such "noise" and avoid the cost implications.
Part of my job involves the audit of Google Analytics setups in order to establish the quality of the data collected. This video story brings together some of the extraordinary findings of this work. It's a study of 75 enterprise websites using Google Analytics.
Universal Analytics collects and stores visitor IP addresses by default. These are used to provide geolocation information about your visitor – such as which city, country, continent visitors connect from. In the new GA4 however, no IP addresses are stored. That’s a big change in approach. In this post, I investigate what impact that will have on your data.
If you have a transactional site, then of course you will want your transactional and product data as measured by Google Analytics, to match the real sales numbers that your back-end system collects. However in reality, these never exactly match due to a number of issues.
I continuously come up against smart people with responsibility for data who remain waaaay too focused on data points, rather than the business they support. A good example of this is the confusion that is stirred up when discussing KPIs…