Analytics Spam - Filtering By Domain Extension

[traffik daddy]

Hi,

I was managing to keep on top of Analytics spam but it seems to have taken to another level now. Its like swatting a fly away and three more come back and it's getting to the point where I am constantly fighting these pests.

I opened this thread to see if anyone anyone has any advice that will help fight a better fight against Analytics referral spam.

I am looking for a way of filtering referrals by domain extension, so I am looking at filtering .info domains, .xyz domains, etc. I have looked online and cannot really find a lot of information or if it can be done, which is why I came here. I tried setting up an Analytics filter to exclude .info in referrals but they still manage to get through.

Any ideas/advice would be welcome :)
TD

[keyplyr]

Analytics referral spam

Commonly called Log Spam.

We've been discussing it many years in the Search Engine Spider & User Agent ID Forum [webmasterworld.com]

[lucy24]

Any ideas/advice would be welcome

If you used an analytics package that was hosted on your own server, all requests would be subject to your own access controls. Then you wouldn’t have to filter out analytics reports from entities that would never be allowed to set foot on your site.

[NickMNS]

The most effective way of "blocking" referral spam is by setting a filter in Google Analytics to only show traffic from hostname == to your domain. This isn't actually blocking anything, but referral spam isn't actual traffic going to your server it is an external resource calling the Anayltics server using your analytics code.

You may continue to see fake referrers after filtering by the hostname. This remaining spam is actual bots going to your server while faking the referrer, or keywords or both. This traffic tends to be less pervasive than the typical referrer spam, this can then be handled by blocking UA's and other method referenced above by Keyplyr.

[keyplyr]

Personally, if i did use a 3rd party software to report server activity (which I never would) I would not block anything from that report.

Google Analytics does a poor job of analyzing web traffic. Why make that even worse?