sarettah
05-19-2005, 07:52 PM
Just a note after reading a different thread.
Those that know about counting dynamic ips etc need read no further, those (especially programmers that write the stuff that counts unique hits and don't know this shit, you can continue to read)
Back in the day, when I was working for ODC, one of my original primary responsibilities was writing the code to count the raw versus unique counts each day. We took painstaking methods to get those numbers as accurate as possible,
A difficulty any program can have in the computation is dynamic ips, where an isp uses the same ip over and over and over again for different users each time.
Now, if you sre setting cookies, then that is going to give you the most accurate count (imho), but, if you are trying to compute from raw logs then you have to be aware of which isp it is coming from and whether they use dynamic or statis ips (or server side caching which is another whole kettle of fish)
If you have an isp that uses dynamic caching, especially if it is a larger isp (lets say AOL or roadrunner) you must go a lot deeper than just looking at the ip to determine if it is a new user (unique) or someone who has been there before.
Some of the methodologies we used were:
1. counting the timeouts between hits. If it was within a certain time period (I think we started with 15 minutes and then tuned from there, it was a while ago and my brain aint what it once was) ie: if the same ip hit within a 15 minute time period, it was the same surfer. If over 15 minutes had gone by, then it was a new user.
2. looking at what was coming in as the 'remote_host' string. Quite often an isp will pass member info in the remote string (or the server picks it up on a reverse ip lookup at the time of the hit, however it gets there, it is oftem there) Unique member info in the host string tells you which surfer it is.
3. Looking at the referer string. If the referer was coming from our site(s), then it definitely was NOT a new hit, as the referring string should have been anything other than our sites on a new hit.
There were several other things we looked at, like I said, it was a while ago.
The main thing I am trying (in such a long winded manner) to say is that if you are calling a hit unique or not based solely on the ip address, then you are automatically shaving off a lot of your traffic especially if you have a lot of AOL, Roadrunner, SWBell, SBCGlobal or any of the other large isps traffic.
It is important to know how many actual uniques you are getting so that when you do the shave, you are shaving accurately and not cutting the balls off of your affiliates by accident. :yowsa:
Those that know about counting dynamic ips etc need read no further, those (especially programmers that write the stuff that counts unique hits and don't know this shit, you can continue to read)
Back in the day, when I was working for ODC, one of my original primary responsibilities was writing the code to count the raw versus unique counts each day. We took painstaking methods to get those numbers as accurate as possible,
A difficulty any program can have in the computation is dynamic ips, where an isp uses the same ip over and over and over again for different users each time.
Now, if you sre setting cookies, then that is going to give you the most accurate count (imho), but, if you are trying to compute from raw logs then you have to be aware of which isp it is coming from and whether they use dynamic or statis ips (or server side caching which is another whole kettle of fish)
If you have an isp that uses dynamic caching, especially if it is a larger isp (lets say AOL or roadrunner) you must go a lot deeper than just looking at the ip to determine if it is a new user (unique) or someone who has been there before.
Some of the methodologies we used were:
1. counting the timeouts between hits. If it was within a certain time period (I think we started with 15 minutes and then tuned from there, it was a while ago and my brain aint what it once was) ie: if the same ip hit within a 15 minute time period, it was the same surfer. If over 15 minutes had gone by, then it was a new user.
2. looking at what was coming in as the 'remote_host' string. Quite often an isp will pass member info in the remote string (or the server picks it up on a reverse ip lookup at the time of the hit, however it gets there, it is oftem there) Unique member info in the host string tells you which surfer it is.
3. Looking at the referer string. If the referer was coming from our site(s), then it definitely was NOT a new hit, as the referring string should have been anything other than our sites on a new hit.
There were several other things we looked at, like I said, it was a while ago.
The main thing I am trying (in such a long winded manner) to say is that if you are calling a hit unique or not based solely on the ip address, then you are automatically shaving off a lot of your traffic especially if you have a lot of AOL, Roadrunner, SWBell, SBCGlobal or any of the other large isps traffic.
It is important to know how many actual uniques you are getting so that when you do the shave, you are shaving accurately and not cutting the balls off of your affiliates by accident. :yowsa: