Create a Filter to exclude the Traffic Bot Open the “admin panel” in your Google Analytics accounts navigate to your “test view” and click on “filters” within the view column.ģ. In our example we will use traffic from the source “trafficbot.live” Identify the bot you want to exclude based on the indicators mentioned above. Identify the Bot Traffic you want to exclude
Trafficbot live how to#
In the next 7 steps we’ll show you exactly how to exclude bot traffic, based on the example used above.ġ. So you have selected the “Exclude all hits from known bots and spiders” and you are still seeing bot traffic in your GA account? Then we need to exclude them individually using view filters.
In order to exclude unknown bot traffic make sure you work in a test view. As mentioned above, this traffic can very clearly be identified as bot-traffic, as we see that the bounce rate is 100%, sessions are exactly 1 and the average time per session is 0 seconds. Here is an example of how we could easily use the word “bot” to filter for traffic sources in order to exclude and identify which traffic (in this case traffic sources) should be excluded.
Some of the most common indicators we have seen are: There are few indicators for unnatural / bot traffic which you can search for within your Google Analytics property. However, before you start excluding ”bot traffic” you will need to identify which traffic should be excluded. In order to exclude these, we suggest excluding them using a filter. Next to a testing view, we recommend that you have an “all website data view” which contains all your raw data and does not contain any filtering.Įvery now and then we see common traffic spikes across the client accounts which are not covered within the standard bot and spider filtering. Within the next steps, we will focus on bot traffic only, however, most of these rules can be applied for spider/crawler traffic.īefore you continue – always make sure you have a “test-view” within your Google Analytics account and test all of your changes in this test view before deploying anything in your production or reporting views. However, other crawlers might be tools that you actively use for on-page optimization, website tracking or even something as simple as uptime monitoring. One of the most common spiders is the “Google Spider” which crawls the web in order to find “new content”. You should not see any of this traffic showing up in your analytics data, however, you will be able to identify them in your server logs.Ĭrawlers access your website in order to access and process data. This traffic is generated by so-called spiders or web crawlers. Next to bot traffic, there’s another type of traffic that is accessing your page, however, should also not show up in your analytics reports. Therefore it’s important to keep your data clean and to make sure you exclude “unnatural and unwanted traffic” from your reporting. Again, we do not recommend anyone using these service as You want to optimize your website for actual users, and actual users only. These “bot-sessions” do not reflect actual user behaviour and will completely mess-up your actual website data. We can however make a very clear statement that you should always refrain from using these services in order to “manipulate” your website metrics. As this “unnatural and faked traffic” can increase website visits, bounce rates and/or time on site, some companies might think it’s a good idea to make use of these services. This is the latest Trend in analytics Spam (however, nothing new) and these services are offered as a way to influence your website metrics. In the last months, there are a handful of providers who send Bot sessions as a means of doing Marketing for their services within your Google Analytics account. Bot traffic is traffic generated by so-called “bots” which are automated programs that perform website activities such as website visits, clicks or the placement of comments.
0 kommentar(er)
