Blog

Categories

Search

StatCounter: Blocking Your Own Visits

If you spend a lot of time browsing/checking/editing your own site, it’s a good idea to block your visits from being counted by StatCounter… Otherwise, your personal visits can skew your stats. At StatCounter we offer two different blocking methods.

IP Blocking
This method is suitable if you have a static (unchanging) IP address (e.g. 12.345.67.89) OR if your IP always falls within a particular range (e.g. 12.345.*.*). Hits from any blocked IP address or IP range will not be included in your StatCounter stats.

Blocking Cookie
If you have a dynamic (constantly and completely changing) IP then use the Blocking Cookie method. Note that for this method you *must* enable cookies in your browser and ensure that cookies are not regularly destroyed by either your browser or your antivirus software. A blocking cookie must be set up for each separate browser you use. Hits from any browser which contains a blocking cookie will not be included in your StatCounter stats.

More about IP Blocking
Please note that this method will *only* be effective if you have a static (unchanging) IP or if your IP remains within a set range. If your IP is dynamic and changes completely and constantly then IP blocking is not suitable. Instead you should consider using the blocking cookie method.

You can confirm your IP address via many different websites like this one, that one or another one and then block your IP using these steps:

1. Login to StatCounter.

2. Click the small “wrench” or “spanner” icon to the right of any project name. (You will later have an option to apply the IP block to all projects)

5. Check the box in the section called “Update IP Blocking in All Projects?” if you want to block the visits in all of your projects.

6. Click the “Edit Project” button.

The IP should now be added to the blocking list.

##If your IP address is in a range, for example, 12.345.00.00 to 12.345.99.99 please use the following format, 12.345.*.* – using the asterisk wildcard characters like this allows you to block the full range of IP addresses which could be allocated to you.

Generally, you will *only* have a static IP if you have requested one from your ISP (internet service provider) and in many cases an additional fee will be charged. If you have *not* requested a static IP then it’s unlikely that you have one. You can confirm this by communication with your ISP directly. OR you can try to check yourself via a “trial and error” method. Check your IP using one of the websites mentioned above. Reset your internet connection and check your IP again. Repeat this a few times and note your IP on each occasion. It should quickly become clear if you have a static IP or if your IP is in a static range or indeed if you have a dynamic IP.

The most likely problem is that your IP address has changed from the IP that you blocked. Check the IP address/range that you have blocked in StatCounter. Next check your current IP using one of the sites listed above. You will probably find that your current IP is not blocked by StatCounter. To solve the problem, add your new IP address/range for blocking purposes. If you’re still having trouble – then talk to us.

More about the Blocking Cookie
The Blocking Cookie will *only* be effective so long as the cookie (small text file) remains in your browser. If your browser/antivirus software is set to remove/destroy cookies, then this method will not work for you. In order to effectively use the Blocking Cookie, you must set your browser/antivirus to allow/retain cookies.

Here’s how to set up a Blocking Cookie:

1. Login to StatCounter.

2. On the “My Projects” page click the “Blocking Cookie” link.

3. Click the “Creating Blocking Cookie For All Projects” button.

4. The page will reload and the button will change to “Destroy Blocking Cookie For All Projects”. This indicates that the blocking cookie has been successfully installed.

Blocking Cookie – Your Questions Answered

I’ve set up a Blocking Cookie but my visits are still counted by StatCounter – what’s wrong?

The Blocking Cookie can *only* block your visits while it is stored in your browser. If your browser is set to disallow or remove cookies, then this means that the Blocking Cookie will not be retained in your browser and therefore cannot block your hits. To effectively use the Blocking Cookie you *must* ensure that your browser is set to allow (and retain) cookies. You should also confirm that your antivirus software is not destroying your cookies.

How do I enable cookies in my browser?

The method to enable cookies will vary from browser to browser – here are instructions for a selection of common browsers:

Chrome (PC):
1. Click the Tools menu.
2. Select Options.
3. Click the Under the Hood tab.
4. Click Content settings in the ‘Privacy’ section.
5. Make sure Allow local data to be set is selected to allow both first-party and third-party cookies.

Chrome (Mac):
1. Select Chrome > Preferences on the menu bar.
2. Click the Under the Hood tab.
3. Click Content settings in the ‘Privacy’ section.
4. Make sure Allow local data to be set is selected to allow both first-party and third-party cookies.

If you have any questions about IP Blocking or the Blocking Cookie, please post them below. We’d also welcome any feedback, comments or suggestions… and if you spot any errors in our post (bar the footnote below!) then please do let us know.

FOOTNOTE: Before anyone decides to comment on our example IP address 12.345.67.89 – please note that it’s an ILLUSTRATIVE EXAMPLE ONLY! It’s not *supposed* to be a real IP address, ok? It’s just a “made up” IP for which we used the digits 1,2,3,4,5,6,7,8,9 in that order regardless of whether that sequence of numbers is technically possible or not.

Oh so that was it. I have always updated the IP blocking manually and in fdact it became a nuisance since my internet provider changes IP addresses at will sometimes 2 time a day. Now I know how to do it and have done it.

With IP address blocking, how many parts of that four part number do you usually have to block if you are working from a variety of computers on a home or office network? Just two (ie 100.100.*.*) or three (100.100.100.*) or less?