i How to Prevent and Remove the Spam from your Google Analytics – All things in moderation

How to Prevent and Remove the Spam from your Google Analytics

1. Spam Google analytics What things you need to know ?
  • FAKE TRAFFIC is defined as one or more fake hits sent to your GA property. A ‘hit’ is that user interaction with your website that result in data being sent to your Google Analytics property. A hit can be a ‘pageview’, ‘screenview’, ‘event’, ‘transaction’ etc.

  • A fake hit is the one which is generated by a program or a bot instead of as a result of a living breathing human being who interacted with your website. At present it is possible to fake any GA hit. What that means, spammer can send fake referral traffic, fake organic traffic, fake direct traffic, fake traffic from social media etc. Spammer can fake events, virtual pageviews, screenviews, hostname, request URI, keywords and even transaction and item data

  • Why you must care about it ?
    The spam in Google Analytics is becoming a headache for many users that rely on their analytics to track the performance of their business and to make important decisions. Unfortunately, the spam they receive makes that hard to do!
  • Who could possibly benefit from sending fake traffic?
    Affiliates are most likely tobenefit from sending fake traffic as they get commission. Internet marketers (particularly SEOs) can also benefit from sending fake traffic. It is not very hard to artificially inflate organic search traffic in GA and then boast about one’s marketing efforts in front of client/boss. In fact any person who can benefit financially, in any shape or form by sending fake traffic can send fake hits to your GA account. Of late fake GA hits were also used to promote propaganda. This was in the form of language spam to vote for ‘Donald Trump’ in the US election.

The wrong way to against Spam
* Create simple exclude filters for each spammer. This is extremely inefficient and can become messy
* Use the referral exclusion list for spam; it will just complicate the issue even more
* Use server-side solutions like WordPress plugins or the .htaccess file for Ghosts (the vast majority of spam) they won’t have any effect

The Right Way of dealing with the spam
* Creating a filter for Crawler Spam
* Creating a Filter for Language Spam
* Excluding Internal Traffic
* Enabling “Exclude all hits from known bots and spiders”

2. Stopping Google Analytics Spam and Other Irrelevant traffic

All of steps I did in the video below this post , you can follow it to do , I just write some notes maybe you need
a. Creating a Valid Hostname Filter for Ghost Spam
The main characteristic of GHOST Spam is that it NEVER VISITS YOURS SITE. Instead, it uses the MEASUREMENT PROTOCOL to reach your GA directly. For that reason, this type of spam always leave a FAKE HOSTNAME or leaves an “undefined” hostname which will appear as (NOT SET) in your reports.
* Find your Hostname
Make a list of all relevant host names you find. At least you see one that will be your
primary domain. The rest depends on the configuration of your site and all the services that have added tracking code
* Build your Hostname Expression
* Create a valid Hostname filter

This filter will stop most of the spam and doesn’t require updates for new ghost spam, but it’s essential to update the expression whenever you add the tracking ID to new service or domain.
b. Creating a filter for Crawler Spam
The following expressions are optimized to block all crawler spam detected over the last couple of years.
Create 1 filter for each expression ( because GA only regex less than 255 characters)
– Expression 1:

  • Expression 2:

If you have exception , add them in regex.
c. Creating a Filter for Language Spam
Regex for Language Spam


d. Enabling “Exclude all hits from known bots and spiders”

NOTE While most of the time filters start working in minutes, officially it may take up to 24 hours before the filter effects become visible in your data, so be patient!

Leave a Reply