Speed ​​up the counters: from myths to reality

    We're speeding up the counters: from myths to reality

    Not only beginners, but also advanced optimizers are at a standstill when it comes to traffic counters - after all, this is usually a JS code that needs to be inserted on the page (and it’s good if you don’t require it as close to the opening tag body) and which cannot be changed in any way. Otherwise, the statistics simply will not work.

    In fact, everything is not so bad. Rather, everything is very good, but few people know about it :)

    Take a look inside



    What is a JS counter code? Usually (in 99% of cases), he “pulls out” from the client environment a set of parameters (URL of the current page, URL of the page from which they switched to the current one, browser, OS, etc.) that are transferred to the statistics server. All the bells and whistles of the counters are associated with ensuring the maximum accuracy of the transmitted information (cross-browser, in fact). The most powerful (Omniture, Google Analytics) also use their own variables and events to strengthen the marketing component.

    But now this is not about that. How does the data collected on the client get to the statistics server? Everything is very simple: a unique element is created in the document, in the URL of which all the necessary values ​​are "sewn up" (usually as GET parameters). This URL leads, as you might guess, to the statistics server, where the data is put into the database and somehow displayed in the admin interface.

    Read more on webo.in →

    Also popular now: