Welcome to WebmasterWorld Guest from 18.104.22.168
Page views: 1490
Records with no cookie: 185
Records with cookie inserted by us: 185
Records with ASP session id in the cookie: 735
Records with siteserver=id=a-long-number: 5
Here are specific questions
a.We never did anything specific to get siteserver=id in our log file. We have no idea how it got there. And that too on just 5 records out of 1490. How did this happen?
b.We have enabled asp session id. What I donít understand is that there are 735 records with asp session id in the cookie, but only 185 records with our variables in the cookie.
I assume that part of the traffic would be crawlers and people who disable even first party cookies. But would that number so high?
Would appreciate some hints on where to look for a solution?
The whole idea of persistent cookies was to do better tracking
A user requests a page. Your server records the request in the log. The response includes a command to save a cookie in with the HTML, etc.
For the second request (usually an image on the page) the request includes the cookie (all requests include the cookie value when it exists). This cookie is dutifully recorded in the log along with all the usual data.
No, I didn't realize the bit about first request not including the cookie. I think both your inputs combined answers my question to some extent. Testing cookie for just one page probably was not a good idea. We will do it on a few more pages and then collect the results again. I will post the results here again
Page A: the page where we were setting cookie
Page B: pages that were referred by page A
I looked at all records for Page B and these are the results
Records that have the values we explicitly inserted:610
Records that have the session id in the cookie, but not the values we inserted: 237
The good news is that around 72% visits are showing cookies correctly. What we are not able to find is why certain records have asp sessionids showing up in the [cs(cookie)] field in the log file, but not the values we are inserting in the cookie. I tried looking at client ips to see if there is one IP that is skewing the data. That's not the case. They are different IPs.
Hope I'm not confusing anyone here.