![]() Maybe Google has found a way to identify these fake visits (by maintaining a database containing known IP addresses of such bots?). As long as there is no "bot" or "spider" or similar word appearing in the User-Agent header, AWstats counts these visits as real visitors. Many hacking bots claim to be an Internet Explorer browser by faking the User-Agent header. When I compared both statistics outputs, I got aware that there was a mismatch of the used browsers of the website visitors. Therefore these visitors do not appear in the stats of Google Analytics. It's quite possible that some (advanced) Internet users make use of such an add-on. NO Google Analytics for Firefox), which actively prevent GoogleAnalytics code to be executed in the browser. There are browser add-ons available (e.g. If JavaScript is disabled in the browser, the code will not be launched and therefore Google Analytics is missing out on that visitor. The Google Analytics code is embedded in the website as a JavaScript code snipped. However this is a security measure to not execute code in the browser. In the era of modern web sites this can cause a website to look catastrophic, agreed. Note that these are only assumptions.īrowsers have the possibility to block all JavaScript scripts. There could be several reasons for that massive difference. The very same for November with an even bigger difference: To my big surprise, the collected data for page view/page impressions are not that far off: Page loading isn't a issue for me, i have anyhow included javascript code for tacking as a seperate JS file and not embedded on html which ensures it is cached on client side.The difference is massive, especially for the visit statistics.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |