Implemented GA Tracking
Contents
Implemented GA Tracking
Simple Definition
Values Returned
Implemented GA Tracking in More Detail:
Coming Soon!
Examples of How This Data is Used
Example 1: Identifying Pages with Multiple Accounts
Example 2: Missing Code
Related Content
Benefits of this Data
Implemented GA Tracking
This data set is the combination of several checks based upon the Google Analytics (GA) data that our web crawler scrape from webpages.
Simple Definition
We check if Google Analytics (GA) tracking code is implemented in some form on every HTML page. We them log and report on that data to you.
Raptor also collects ‘UA’ Google account numbers and logs these against the pages they are found to be located on.
Values Returned
Below are the different values that can be returned within this column and a definition of what they mean:
Good (GAT) = Implemented without error with tracking code
Good (GTM) = Implemented without error with GTM (Google Tag Manager)
Missing = No GA code or GTM code implementation Is present
Error = GA code or GTM code implementation Is present but is incorrectly Implemented
Implemented GA Tracking in More Detail:
This is a check that informs you whether a page contains any Google Analytics tracking code, whether its implemented through tag manager or located in the source code.
Regardless of the type of implementation, if the implementation is inline with the guidelines, we will consider a page to have the most basic Google Tracking code implemented.
We check the following:
- GA tracking code is present on the page
- That the implementation of the GA code is correct
- In the correct location
- Aren’t missing parameters
- Doesn’t have multiple accounts on the same page
- Google Tag Manager (GTM) is correctly managing the GA code implementation
- All this data is logged against each page
Coming Soon!
Currently, we do not scrape the following data, but this is coming soon:
- Event tracking code
- Goal Tracking Code
- AdWords tracking code
- Remarketing code
- Non-Google Analytics Tracking Code (Adobe, Omniture, etc)
We are in early release phase now and are always adding new data, checks and analysis to our tools, we aim to add all these components over the coming weeks and months.
Examples of How This Data is Used
All the data our web crawler scrapes is used in various ways by SEOs or web developers. We provide some examples of these use below.
Example 1: Identifying Pages with Multiple Accounts
Using the following filtering criteria to identify pages that you know for almost 99% certainty are setup incorrectly:
- Only show indexable URLs
- Only show canonical URLs
- Only show URLs with multiple UA Accounts
In above example, we are ensuring that we are only including HTML/Text pages, that are the preferred pages, and are technically indexable web pages. You can widen the net and use your own custom combination of filters to interrogate the data.
Example 2: Missing Code
In the example below where you may not have a reliable canonical configuration, you can therefore look at pages that are at least indexable HTM/Text pages that are missing GA Tracking Code
- Only show indexable URLs
- HTML/Text
- Only show URLs missing UA Accounts
Related Content
The list of guides below might be useful if you are analysing this data and want to know more about it:
Other content and definitions from this section of Analytics column headers are as follows:
Benefits of this Data
The three main benefits of this data are as follows:
- Identify pages that are missing GA tracking code
- Identify pages that have incorrectly implemented tracking code
- Identify pages with multiple GA Account tracking code
So why not sign up for a Free 30-Day Trial today and check for any Google Analytics implementation problems on your site.