Boot ISP filter configuration:

[kexej28769@nongnue]

Filter name : Exclude bots by ISP.

Filter field : ISP organization
Filter pattern : [ISP provider REGEX]
ISP provider bots REGEX (pre-built)
hubspot|^google\sllc$|^google\sinc\.$|alibaba\.com\sllc|ovh\shosting\sinc\.
Latest ISP bot expression

IP filter for internal traffic
We've already covered different types of internal belgium number data , one from test sites (with a hostname filter), and one from third-party tools (with a campaign source filter).

Now it's time to look at the most common and damaging: traffic generated directly by you or a member of your team while working on any task for the site.

To deal with this, the standard solution is to create a filter that excludes the public IP (not private) of all locations used to operate the site.

Examples of places/people that should be filtered.

Any space that is regularly used to work on your site.
To find the public IP of the location you're working at, simply search Google for "my IP." You'll see one of these versions:


No matter which version you look at, create a list with the IPs of each location and combine them with REGEX, just like we did with the other filters.

IP address expression: IP1|IP2|IP3|IP4 etc.
Static IP filter configuration:

Filter name : Exclude internal traffic (IP)
Filter type : Custom > Exclude.
Filter field : IP address
Filter pattern: [IP expression]
Cases when this filter would not be optimal:
There are some cases in which the IP filter will not be as effective as it used to be:

You use IP anonymization (required by GDPR regulation). When you anonymize the IP in GA, the last part of the IP is changed to 0. This means that if you have 1.23.45.678, GA will pass it as 1.23.45.0, so you need to put it in your filter like that. The problem is that you are leaving out other IPs that are not yours.
Your internet provider changes your IP frequently (dynamic IP). This has become a common problem recently, especially if you have the long version (IPv6).