Exclude some IP addresses from Stats

[owlette]

Our web designer configured our StatCounter account so his IP address is not logged within the Stats.....however, is there a way of excluding our own IP address from the Stats...I haven't gone public with the site yet and have just been checking various things myself and am registering as a "returning visitor". Any clue please?

[webado]

Our web designer configured our StatCounter account so his IP address is not logged within the Stats.....however, is there a way of excluding our own IP address from the Stats...I haven't gone public with the site yet and have just been checking various things myself and am registering as a "returning visitor". Any clue please?
Get the IP address for a computer on the connection whose IP address you want to exclude and sign into the Satcounter admin page. For each project, use the wrench icon and edit the project settings and add the IP address of your own internet connection to exclude. All accesses to your tracked pages will not be counted - for all computers sharing the same IP address (internal IP addresses do not count).

Otherwise create blocking cookies from each computer involved.

[DVDsPlusMore]

Great advice.

To build on this, blocking by IP address will really only work if you are using a system with a *fixed* IP address. This describes most corporate environments. If you're a home business, though, you may see problems. AOL users, for instance, get a new IP address each time they log-on -- clearly a problem unless you set up a new block each time you access your site. Many people with broadband access through their cable service will encounter the same situation.

For people whose IP address does change periodically, it's better to block with a cookie. This cookie lives harmlessly on your computer and ensures that your visits aren't accidentally included in your data set. Through the control panel, the cookie can be activated and/or deactivated quite easily.

As far as I know, there's no harm in using both blocking solutions -- a belt and suspenders solution, if there ever was one!

Make sense to you?

Best,

James @ DVDsPlusMore (http://www.dvdsplusmore.com/)

[webado]

Great advice.

To build on this, blocking by IP address will really only work if you are using a system with a *fixed* IP address. This describes most corporate environments. If you're a home business, though, you may see problems. AOL users, for instance, get a new IP address each time they log-on -- clearly a problem unless you set up a new block each time you access your site. Many people with broadband access through their cable service will encounter the same situation.

For people whose IP address does change periodically, it's better to block with a cookie. This cookie lives harmlessly on your computer and ensures that your visits aren't accidentally included in your data set. Through the control panel, the cookie can be activated and/or deactivated quite easily.

As far as I know, there's no harm in using both blocking solutions -- a belt and suspenders solution, if there ever was one!

Make sense to you?

Best,

James @ DVDsPlusMore (http://www.dvdsplusmore.com/)
QUite right. My IP address is also part-time fixed. It's nto a new address at every conneciton, but it changes quite often on a whim frlom my ISP. I use ADSL.

My blocking cookies work generally, except that every so often some gremlin I have that I haven't identified yet seems to delete either some blocking cookies or even my admin login cookie. It's still a mystery as to which process does that, since I do not as a matter of course delete cookies automatically (that I know of), Ad-aware has the statcounter cookies on its ignore list and I see no rhyme or reason to it. :lol: All I've noticed is that every time Ad-aware runs it finds a Statcounter cookie again with a new appendage (number of hits for a strange reason), which appears to it to be a new one, so every time I have to place that in the ignore list again and again. Maybe it's a bug of Ad-aware SE which I have recently installed.

I'm just wondering if it's not a little bug in the creation of the session cookie mixed in with the blocking cookie which means that the blocking cookie sort of expires in tandem with the session cookie - I'm all muddled on this so sorry if I don't make sense. I don't even make sense to myself :lol: Or else it's another one of those mysterious settings I may have messed up in IE while trying to tweak the privacy and security settings. :evil: