Page Tagging (cookies) vs. Log Analysis
Each has pro’s and con’s, but fortunately you can use both methods combined if you’re using Logaholic.
But first, let’s take a look at the differences.
Your website is hosted on a webserver that creates log files, these accurately store any kind of visitor movement on your site. This ‘Big Data’, is difficult to read, complicated to transport to a central server, and impossible to digest in raw format.
Logaholic can be setup using log files as main data source to report valuable visitor behavior in a understandable format. It then imports (this process is called “Parsing”) visitor data into a local database that accurately stores traffic history on the visitors to a Web Site.
Which method is best for you is hard to determine without knowing your situation. Both methods have their merrits, despite the fact both methods will show significant different traffic numbers there is not a good or bad method, actually they compliment each other.
You might already know that a large part of your website traffic comes from non-human visitors (bots). This could be search engines crawling your site, bots with darker intentions or maybe a mailfunctioning script in your own site.
- Visitors that Block/Delete Cookies.
- Cookies that time-out.
- Impatient visitors that click away before the tagged page loads completely.
Logaholic supplies a uncompromising view not hindered by any limitations that an exclusive SaaS solution has or that ad serving interests might lead to favoring the not so accurate method. We simply want you to use the best tool for your specific situation we don’t need to sell you anything else.
Using Google Analytics to track your ads? Read this!
Above is highlighted that both mainstream data collection methods will report significant differences in your website traffic. Obviously advertising conversion rates will also differ. Combining results of both data collection methods will lead to more accurate insights crucial for staying in control of performance based ad-buying costs. Not a very comfortable feeling having to give your ad provider control over your credit card and knowing you are not able to verify ad-charges.
Web server logs contain ALL website traffic. Javatrackers don’t and may miss a lot of (paid) clicks. Known fact; a percentage of ad clicks are ‘false’ or violate the terms of your paid traffic provider and should not be charged. Consequently false clicks are subject to ‘Click Fraud’.
Experts estimate that 15-20% of all paid traffic (ppc) is in a grey area. Not being able to conduct proper forensics with a reliable tool is costing you or is going to cost you. Advertising charges are impossible to verify with a java tracker only, you have to at least use a tool capable of analyzing web server logs, Logaholic supports both methods.