General Google Analytics and Google Tag Manager Implementation Issues
About 12-18 months ago I saw Digital Marketing Company Stafford a disturbing trend in our client’s Google Analytics configuration.
As a number of our clients begin to upgrade to Universal Analytics or switch to implementation through GA GA, a number of small issues began to grow.
This is the most common scenarios and issues:
Upgrade to Universal Analytics, forgot to remove Classics
During the Universal Classics to increase, quite often our client development team would forget to remove the Classic Analytics code while implementing Universal Analytics.
It is a common mistake, but it can go easily unnoticed.
Implementing GA via Google Tag Manager (GTM) and then forget to delete the original GA code
As more clients begin adopting GTM to track the GA (if you have not been able to start with this or are unsure about GTM, check out our post here), often times they will apply the container GTM (containing GA tracking) but forgot to remove the code GA native , Again, this will contribute to problems such as increased page views, events interaction etc.
Some Types of Implementation
I also see a scenario where the client will use different types of implementations. For example, the GA implementation of the code in the main site and then the implementation of the GA through WordPress plugins for blogs.
When there is a trend in this sort of thing, I get all angry.
So I began to explore potential solutions.
Here’s how to check the Google Analytics code is on every page of your site and, erm, a hidden agenda behind this post.
Pentasia Case Study
6 GA Tagging tool that will help – and The Hidden Agenda
ObservePoint doing far more than just check the page containing the Google Analytics code.
You can consider your enterprise tag management and debugging tool.
If you are working on a large site (over 10,000 pages) and has worked with a large number of third-party tag, it is worth considering ObservePoint.
ObservePoint also offers App and Video solution configuration tracking, in addition to expert support in planning the measurement.
If you have a site that is quite small (under 1,000 pages) and the time to do a little manual analysis in Excel, you may want to consider using a Custom Search feature.
Just add the Google Analytics tracking ID or GTM ID into your container contains / does not contain a section on Custom Search, run a crawl and then export to CSV page.
If you are confident with the Screaming Frog and Excel, this is a fairly easy process. If you do not, it’s fiddly as hell.
Regardless, the possibility is not a solution that is useful for sites that are larger than 1,000 pages, mainly because of the time required to browse the site and that you also have to hope Screaming Frog did not experience timeouts or crawling problem.
WASP w / Tableau
I’ve completely forgotten exactly how I did this but as I was testing a number of solutions, I use a combination of WASP Chrome Extensions Crawler and Tableau to report tagging coverage.
If you are not familiar with Tableau, they offer a set of tools Analytics for data analysis and visualization.
One of them included a free Chrome extension, stored, including crawler.
Using free crawlers and up to two filters, you can scan up to 100 pages and will return detailed information about the tag on the page, but only if you export the data and work in Tableau for reporting.
If you are familiar with Tableau, this is a practical solution.
I’ve not used Hub’Scan so I can not Digital Marketing Company Sheffield comment on the functionality.
Hub’Scan offers a suite of Analytics, Conversion and SEO tools, one of which specifically referred tagging efficiency and compliance.