Semalt: Effective Ways To Exclude Internal Traffic In Google Analytics

One of the simplest mistakes that companies, agencies, and individuals overlook when it comes to counting their monthly number is the inclusion of their traffic in their client's websites. It may seem insignificant, but it has a huge role to play in the conversion rate, as it inflates the traffic they receive from visitors.

There are several ways, specified by Andrew Dyhan, the Customer Success Manager of Semalt Digital Services, that one can use to alleviate this problem. They range from simple installations to those that require developer resources to implement. One thing to remember is always to have a separate analytics account where one can store all raw data as backup.

#1 Google Analytics Opt-Out Browser Plugin

It is the easiest to implement. All the users that one wishes to block need to download and install the Google Analytics Opt-out Browser Add-on. Once installed, they will no longer be able to send their visitor data to the analytics. It works by prohibiting GA JavaScript from sending visit information. It, however, does not allow the user to choose which information is blocked out. Therefore, if there is some information that needs to transmit visit data, then disable the extension.

Install the add-on on all user profiles, browsers, and all devices with access to a browser. Also, remember that the add-on is on for all profiles. Therefore, if the current profile in use is what runs tests, then change to a different profile or disable the add-on to see if the tracking is working correctly.

#2 Custom Filters Based on IP

Single IP Address:

Go to the Admin tab in GA, and select filters. From these, choose to add a new filter from the filter tab. From here, insert a custom filter using a single IP address. After setting the parameters, click save and then exit.

The range of IP Addresses:

Follow the same procedure for single IP addresses. However, after selecting a new filter, choose a custom filter in the filter type, and the exclude the IP in the exclude filter field. Finally, insert the range for the IP in the filter pattern.

#3 Custom Filters Based on ISP

Excluding traffic from an ISP can either be through a predefined or a custom filter. In the same way, one can ignore an ISP from GA. It is either one uses the ISP domain or ISP organization. The difference is that one refers to the registered name as per the ISP issue, while the other means the ISP's geographical domain. The predefined filter only allows one to work with an ISP domain.

ISP Domain:

Use the same procedure for a range of IP addresses, use the predefined filter in filter type, and then exclude the ISP domain.

ISP Organization:

Filter type should be a custom filter, then exclude the ISP organization in the filter field. Then insert its domain in the "from ISP Domain."

#4 Set a JavaScript Cookie

The two methods to use are _setVar() and _setCustomVar(). The difference between the two is that _setVar() uses the User Defined Filter field and the latter cannot. _setVar() allows the user to set a profile filter they can use to exclude personal traffic. The alternative _setCustomVar() uses advanced segments that make it possible to filter out traffic. It means that the data it filters comes after it goes through GA.

_setVar(): set a custom filter in the filter type, should be a user defined filter field and use an employee as the filter pattern.

_setCustomVar(): exclude a custom variable (key 1), then select those that are exactly matching employee. Then include the custom variable (Value 01), and exactly matching Yes.