Get better data by filtering bot traffic in Google Analytics!

Google Analytics recently released a new feature where you can click on a flag to assist with filtering bot traffic from spiders and bots. This is important because it will allow your statistics to be more accurate.

Before I explain how to enable the bot filtering flag in Google Analytics, I want to explain a bit more about what the bot traffic is.

What is the definition of bot Traffic?

Bot Traffic is online traffic and activity generated artificially through automated robots and spider programs.
Although it is difficult to evaluate, according to several sources it is estimated that the proportion of bot traffic to a website is between 10% to 20% of total traffic. Each website will automatically receive a certain level of bot traffic. So the lower the proportion of genuine traffic the greater the proportion bot traffic. The proportion of bot traffic also varies depending on the site’s nature and activity. For example, the more often a website or blog is updated with new content more often will search engine bots will be pinged to visit the site.

There are eligible, Official bots and bad bots.

Good bots are useful because they provide a variety of Internet services.

The good bots are:

  • Search Engine bots
  • Bots used to measure the availability and response times
  • Bots that measure advertising

The bad bots are:

  • Harvesting email addresses
  • Automated account registration in order to create multiple email accounts
  • Spinning content (write about the content of an article as it is perceived as multiple articles at eg Google)
  • Spamming blogs and comments
  • Clicks and fraudulent impressions of such ads

Filtering bot traffic with Captcha

There is something called “Captcha “is a good way to prevent the bot traffic. Captcha is designed to determine whether the user is a human or not. The most common way and you come across many times is that the user must enter the characters you see in the distorted image. Very annoying, unfortunately for most of us. This won’t help against filtering bot traffic in all cases, but can be useful. Especially when the image of the characters are very indistinct. A more modern variant and that I use is that you get to choose which characters but there must be at least two. Maybe not as safe but still!

[lightbox full=”http://dreamcore.net/wp-content/uploads/2014/11/captcha-examples.jpg” title=”Captcha Examples”]

captcha examples
Click for larger image

[/lightbox]

When the user agent or bot signature recognized, web analytics and ad servers filter out bot traffic. See, for example, the Interactive Advertising Bureau  (IAB).Meanwhile, the bad bots often an unknown signature. The only thing that is not influenced by bots is online panel survey.

IAB estimated in March 2014 that the bot traffic generates 36% of all traffic online!

How do you filter Spider and bot Traffic Through Google Analytics?

Google has on its official Google+ page announced  a new filter that helps owners of websites to identify the “real” traffic from coming from bots and spiders.

By checking a box in a filter, will Google Analytics to filter out all traffic from known bots. The list of bots, Google just from the IAB I mentioned above and their: IAB / ABC International Spiders & Bots List .

To filter out spider traffic from Google Analytics:

  • Go to the Admin Page
  • Select View Settings

[lightbox full=”http://dreamcore.net/wp-content/uploads/2014/11/google-analytics-admin.png” title=”Google Analytics Admin”]

Google Analytics Admin
Click for larger image

[/lightbox]

  • Scroll down until you see Bot Filtering
  • Check the box  Exclude all hits from known bots and spiders
  • Don’t forget to click save!

[lightbox full=”http://dreamcore.net/wp-content/uploads/2014/11/google-analytics-bot-filtering.png” title=”Google Analytics Bot Filtering”]

Filtering Bot Traffic in Google Analytics
Click for larger image

[/lightbox]

I hope this helps, happy data gathering!

Leave a Reply

Your email address will not be published. Required fields are marked *