![]() Feel free to verify the filter if you wish. ![]() ![]() But if you look at the event globally you can find these four directories. /trafficbot.live|/trafficbot.life|/bot-traffic.icu|/bot-traffic.xyz – you may only see one or two of these in your analytics.Exclude | traffic to the subdirectories | That are equal to.I would avoid names like “bot spam” since a few years from now there might be new type of bot spam. Give the filter a descriptive name like “2021Q1BotSpam”.We’re going to do all of the work today in your non-unfiltered view – in my case I call that the Master view. And a few types of spam I’ve seen in previous years.On my Master view with my filters – I remove prevent a whole bunch of data from coming in: The unfiltered view, my master view, and a test view for experimentation. Knowing you have an unfiltered view then it’s time to create one or more views that removes any unimportant data. This will be your backup view that collects all data. One of them is that you can create an Unfiltered view. There’s several great things about views. Each view gets the exact same data but you can filter out different pieces of that data. One of the best features of Google Analytics is that you can setup multiple views. This could throw off your entire analytics & reporting system, so let’s see if we can prevent this type of spam moving forward. It was added by several thousand bots coming from different IP addresses. The first thing to know is that this is spam. This is the easiest and most scalable solution (scalable to an extent).If you’re the type of person who checks your website Google Analytics often you might have noticed a spike in traffic at the end of January or early February. So this is it, setup view filters in Google Analytics.Ĭlick here to see how to create and manage view filter in your Google Analytics (GA)Ĭreate an exclude filter for the Request URI dimension, filtering out the ghost traffics string ( “trafficbot, bottraffic, bot-traffic“). Note that this method is only scalable to an extent. This is because the traffic is not coming to your website and the Cloudflare firewall can only block traffic on your website. I have seen several people who said they have tried using Cloudflare to filter these ghost traffics out but didn’t help at all. Unlike regular bot spam, ghost traffic appears only in your GA reports and would not be visible in server logs. wont help one bit!) as this is ghost traffic that bypasses your server and targets Google Analytics directly using what is called “Measurement Protocol”. There is nothing you can do on your site or server (.htaccess rules, WP plugins, firewalls, etc. It tends to hit smaller sites harder, as it represents a higher percentage of their overall traffic. Of course, the indirect harm caused by the data pollution is hard to estimate and will vary. Traffic, with a landing page of “/trafficbot.life, /bottraffic.live, bot-traffic.xyz, bot-traffic.life ” in your traffic reports or the same page in your Content reports poses no direct harm to your site. So If you’re seeing sessions with the exact landing page “/trafficbot.life, /bottraffic.live, bot-traffic.xyz, bot-traffic.life ” or page then your analytics account has been a victim of spammers that pollute your stats in order to get your attention. Trafficbot.life is ghost traffic that spam Google Analytics and then the Google monitoring tools have picked up. Before we proceed here, you need to note that trafficbot.life is not an attack on your website but to spam your Google Analytics (GA).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |