Block traffic from referral spambots in Azure Web App with DNN
I'm sure many of you found fake referral traffic in your Google analytics reports / reviews. This makes it difficult to build low to medium traffic sites to get accurate marketing data. I'm wondering what others are doing to exclude this traffic from their analytics reports.
If you go to your analytics account and go to the buy page -> all traffic -> referrals, you will see sites like floating-share-buttons.com. These are the sites that I want to filter out. Which you can do by setting up your own filter for the view, as described at the bottom of this page . I did this and it works.
I would prefer to block these bots from entering the site all together. Just note: my sites work like web applications in an azure look.
I'm not sure if setting up the URL rewriting rules described here will work in azure applications or if it would be useless with the existing URL rewriting features of the content management system in use (DotNetNuke DNN 7 platform).
I really just want to know what others have done to block bots, not set up filters in the analytics view settings.
thank
PS
for those interested, this is the current filter list I am using:
webmonetizer\.net|trafficmonetizer\.org|success-seo\.com|event-tracking\.com|Get-Free-Traffic-Now\.com|buttons-for-website\.com|4webmasters\.org|floating-share-buttons\.com|free-social-buttons\.com|e-buyeasy\.com
source to share
Regarding this problem, there are a number of things you can do. You are taken to the route that I usually use, which should block information using filters in Google Analytics.
You can also follow the IIS filter route as you do. DNN friendly URLs will not necessarily affect this as they are processed BEFORE the DNN receives the request. There is negligible performance impact as two things are overworked, but nothing bothers you until the incredibly high volume of users.
This is a great collection of options.
source to share
First you need to know that there are currently two types of spam affecting GA, Ghost and Scanner .
The first one (ghosts) never interacts with their page, so any server-side decisions like HTTP rules or htaccess file will have no effect and will only populate your config files.
Crawlers, like the name, imply access to your website and can be blocked this way, but there are only a few compared to the ghost. To give you an idea, there are about 8 active scanners, while there are over 100 ghosts and each week increases.
This is because the ghost method is easier for spammers to implement.
From your expression, only success-seo is a finder. The rest needs to be filtered. There is now a better way to get rid of all ghosts with just one filter based on valid hostnames instead of updating every week.
You can find more information on ghost spam and the solution here.
fooobar.com/questions/251085 / ...
https://moz.com/ugc/stop-ghost-spam-in-google-analytics-with-one-filter
Hope it helps.
source to share