Page tagging for hybrid analysis

Top  Previous  Next

Professional edition only

 

To eliminate limitations of log file compared to script-based web analytics, such are better visitor/spider identification and more information, you can consider using page tagging with Web Log Storming. It works similarly to various widely-known web analytics, with one of important differences that data stays on your server. This way, Web Log Storming combines best features of two web analytics worlds. Page tagging is required if you wish to see Cookie IDs or Screen Resolutions reports or if you wish better detection of previous visits, spiders and time spent on page.

 

How to use it?

Page tagging feature uses a small JavaScript that hosted on your server (no third-party involvement) and additional information will be written directly to regular log files (no databases or additional files), which you already analyze in Web Log Storming.

 

Step 1: Download wls_log.zip arhive and unpack it to root of your server (so file paths are /wls_log/wls_log.js and /wls_log/wls_log.gif).

 

Step 2: Include this one line in your pages that you want to track (template, header file, all static html files, whatever matches your system):

 

<head>

...

<script src="/wls_log/wls_log.js"></script><script>wlsInit();</script>

...

</head>

 

Wait a bit to collect some data and that's it. No additional configuration of Web Log Storming is needed - if it finds additional information, it will use it. Otherwise, it will simply work like before. Note that putting this line into HEAD tag is preferable, but not mandatory.

 

See also

       Cookies IDs report

       Screen Resolutions report

       Time Spent report