Tracking User Sessions Originating from Proxy Servers

Ever look at your web traffic reports in absolute awe, and wonder how it's possible that your reports show more "User Sessions" that "Page Views?" Or maybe you are wondering who the heck that one huge user session is? Or why the heck 35% of your users originate from Virginia?

"Bug in the software" say you. "Nay" say I.

Undoubtedly, you have probably heard by now that there is a shortage of available IP numbers and ranges. One of the ways that internet companies are getting around this issue is by routing their users through a proxy server. In this case, all users showing up on your web site will come in with the IP address of the Proxy Server, and the IP will resolve to the physical location of the proxy servers. Scratching your head are ya?

How about an example:

Say that various different users in different parts of the world use one of those global internet companies, and they dial into a local number in their area, say for this example that the following information is true:

User 1: Anaheim, California
User 2: Los Angeles, California
User 3: Buenos Aires, Argentina
User 4: Dallas, Texas
User 5: Madrid, Spain
User 7: Portland, Oregon

Their connection is being routed to a group of proxy servers owned by their ISP (say, BIG COMPANY INC.). Say BIG COMPANY INC. is in Virginia. This means that every time a user who is using BIG COMPANY INC as an Internet Service Provider connects to your web site, the server will log the IP number of the proxy server on the log file.

Follow?

Okay. Now, whatever software you happen to be using to create your reports takes the IP on your log files and tries to resolve it to a DNS server to provide you with some meaningful data. You anxiously sit back waiting for your report, and when it is finished you look in absolute horror as you encounter the following scenarios:

1. Your web server in Los Angeles is a small network only of interest to local folks, and yet the #1 Most Active Organization is BIG COMPANY INC in Virginia.