Spamming the Analytics data of websites is now an old practice. It’s better known as Referral Spam, and I have written about this in the past at multiple times. Purely a black hat practice, I doubt whether it would give great returns.
Yes, it would give traffic to the spammer, but how does that really translate into revenue. Or is the tactic hoping to drive gullible folks by the hordes?
The referral spam industry for some reason also loves to send the geographical position as Samara. For those of you who are noticing this now, here’s how the tactic works.
How Referral Spam works
- The bot hits a particular site for multiple times in the day
- The analyst sees his Google Analytics account, and gets surprised by a spike in traffic. Who wouldn’t mind seeing such a spike :)
- The obvious report to check this out would be the Source / Medium in the Acquisition section.
- There staring at you in all glory is the spamming domain
- The analyst gets curious, and visits the site
The rest, would not be history, it would be a scam.
How should I combat this?
Raven Tools has a comprehensive article on combating Referral spam. They have listed multiple methods to ensure that this spammy data is not accounted for in your analytics data.
Personally, I allow the data to reside in my Master Data View. The reason behind that is – since I do not look at aggregate data anyways (I prefer lots and lots of custom segments), I am not too bothered with that data! I do however, mark it as a annotation on my GA. That’s the advice I would give to anyone.
This post is part of the thread: Samara Oblast – an ongoing story on this site. View the thread timeline for more context on this post.