Setting up Google Analytics is easy. You simply have to install the Google Analytics tracking code on the site and BOOM! Data starts flowing through your dashboard.
One of the biggest mistakes most people make while setting up Google Analytics is they DON’T exclude internal IPs, and you may be one of them.
How many times in a day do you check your own (or your client’s) website? Once? Twice? More than ten times? If it’s more than that, you have skewed data.
The solution is to use the view filters to exclude yours and your client’s IPs from getting tracked in Google analytics.
Let’s take a look at how you can exclude:
- Subnet Of IPs
- IP Ranges (Sequential)
- Random IPs
How to Exclude Specific IP’s from Google Analytics for better reporting:
#1 Exclude Subnet of IPs
Let’s say you want to exclude all the subnets of IPs starting with 192.168.0.x, where x is any number.
You can create a view filter with type as ‘predefined’, then select ‘exclude traffic from IP address that begins with‘ and paste the starting part of an IP ‘192.168.0’
Doing so will filter out all the IPs starting with 192.168.0
For Eg: 192.168.0.1, 192.168.0.2, 192.168.0.3 and so on…
Save the filter and you’re good to go.
#2 Exclude IP Range (Sequential)
IP Range can be any range of sequential IPs, for eg:
- 192.168.0.0 – 192.168.0.9
- 192.168.0.10 – 192.168.0.19
- & so on…
I have seen a lot of people creating ten different filters for each IP, a very time-consuming job. The best way is to use REGEX to exclude the group of IPs in a single filter.
Here’s how you can do it.
- Go to view filters and create a new one.
- Choose Filter Type as ‘Custom’ and Filter Field as ‘IP Address’
- Add ‘^192.168.0.[0-9]$’ in the filter pattern
The above example will exclude IP range from 192.168.0.0 to 192.168.0.9 (10 IPs).
I won’t go into much details about regex, but remember these basics:
- ^ – denotes the start of the string
- $ – denotes the end of the string
- | – denotes the ‘OR’
- – denotes the escape character.
- [0-9] – denotes any number from 0 to 9
Lastly, save the filter.
#3 Exclude Random IPs
Well, most of the times you need to exclude the IPs of your home, office, mobile, and clients.
These IPs are neither sequential nor a part of the same IP subnet; they are random.
In that case, you can simply use the ‘OR’ in Regex which is denoted as ” | “. So if you have random IPs, say 184.108.40.206 & 127.101.1.1.
You can use ^220.127.116.11$|^127.101.1.1$
Check the image below.
As we discussed earlier ‘^’ denotes ‘starts with’, ‘$’ denotes ‘ends with’ & ‘|’ denotes ‘OR’ condition.
So, if you have five random IPs, you can simply put it in this format:
Tip #1: Use Regex Tool To Verify The Syntax
Sadly, Google Analytics does not provide the ‘preview‘ for IP address filters.
You can use any Regex testing tool available online. One of them, which I use a lot, is Regextester.
You can input your Regex pattern in the above row and paste all the IPs you want to exclude in the ‘Test String’ box.
I have included four IPs in the Regex pattern and pasted the same in the Test String box (along with one extra IP).
If the IPs turn blue, those are matched.
If everything goes well, you can copy the same expressions and add ^ & $ at the start/end of each IP and use it in Google Analytics.
Tip #2: Use Tag Assistant To Test Different IPs
Tag assistant is a chrome add-on which allows you to debug and test whether or not your Google tags are firing correctly.
One of the features is to change the IP address.
You can test the IP addresses which you have excluded via Regex filters one by one and click ‘update’.
Tag assistant will re-analyze the reports and show you if the hits are well filtered. You can learn more about it here.
Google Analytics filters are non-retroactive. i.e., the filters will only alter the data moving forward.
So make sure you exclude internal IPs at the initial stages of setting up the Google Analytics.
This is a guest post by Ritwik. If you would like to submit something original for epostakur then read our submission guidelines here.
Also, here are a few hand-picked guide for you to read next: