Have you ever been asked the influence of Javascript disabled or cookie disabled for web analytics by your client? This is really a problem haunting me for long time, and sometimes clients will regard it as a scary issue. They would like to challenge that web analytics is not "accurate" (see the Chinese article for detail on "accurate" of web analytics: 网站分析——我们的数据准确吗？) from this perspective. Therefore I think it’s really my task to figure out how much influence it will bring substantially.
- JavaScript disabled
Adding JavaScript tracking codes to track page performance is the most popular way of web analytics today. As below graph illustrated, tracking codes is like the tiny red block embedded in page’s HTML source file. When page downloads, these JavaScript codes will be executed in the meantime, just like the Zerg’s parasite in StarCraft, or monitoring camera in bank, and the data recorded. If a browser disabled JavaScript, tracking process can’t be triggered and the user’s behavior data won’t be transfered to web analytics tracking tools. It’s pathetic, right? So, JavaScript function to be opt-on is vital for web analytics.
JavaScript tracking codes is the "spy" in a page to track page performance continue reading…