Google\'s detection of Unusual traffic is nice. But how is it handling Dynamic IP addresses?
For example,I do not have ranges of IPs and my ISP provides Dynamic IP which
Better option is to use Google Analytics Opt-Out Browser Plugin found here:
https://tools.google.com/dlpage/gaoptout
FYI, I thought of another approach using HTML5’s localStorage feature. (The advantage over the cookie is that when you clean your browser’s cookies, localStorage values remain.) I’ve written a blog article about it here: Google Analytics: Exclude your own visits
If you are talking about your own computer/network you have several options:
Set up a proxy (Fiddler, or if possible a rule in your router) to block calls to google-analytics.com (the proxy should still return a 200 status code)
per Gaurav's answer use the Google extension to block GA (there are versions for all major browsers)
set a cookie in the format disable-UA-XXXXXX-X where you replace the X with your property id.
The first two options will block all Google Analytics tracking on any site, the last will only stop tracking the property specified in the cookie value.
All of these are IMO better solutions than conditionally including the analytics library. If you have a call to a method from the GA library somewhere in your code and the library isn't loaded this will result in a javascript error. The methods above will at least load a code stub that captures method calls so there are no calls to undefined functions.
There are problems with many of the popular answers to this question...
So, I combined several other solutions into something that works for me...
I keep a "developer cookie" set on my machine at all times just for the domains that I manage. This cookie has a unique value that is specific to me. Then I simply check for this cookie in my scripts before sending any data to Analytics.
Examples of how I put the code into my pages...
JavaScript
if (window.location.host==="mydomain.com" || window.location.host==="www.mydomain.com") {
if (document.cookie.indexOf("COOKIENAME=COOKIEVALUE") === -1) {
// Insert Analytics Code Here
}
}
PHP
if ($_SERVER['HTTP_HOST']==="mydomain.com" || $_SERVER['HTTP_HOST']==="www.mydomain.com") {
if (@$_COOKIE["COOKIENAME"] !== "COOKIEVALUE") {
// Insert Analytics Code Here
}
}
Verifying that the HOST name equals the domain of my live site ("mydomain.com") ensures that the analytics data will never be sent by ANY visitor while viewing from a test domain such as "localhost" or "beta.mydomain.com". In the examples above, "www.mydomain.com" and "mydomain.com" are the two valid domains where I DO want visits to be recorded.
The live site sends data to analytics as expected UNLESS a developer cookie is found with matching values. If it finds that unique cookie set on my device, then my visit will not count towards my totals in Google Analytics (or whatever other analytics tool I might decide to use one day).
But what happens when my cookies get cleared? How do I keep the "developer cookie" set in the background? I created my own Browser Extension for that... https://chrome.google.com/webstore/detail/lknhpplgahpbindnnocglcjonpahfikn
It works just for the specific domains that you choose. You customize your own unique NAME and VALUE for the cookies in the extension's settings.
This method can easily be used by a team of people as long as they use the same NAME/VALUE pair, so developers, content creators, proofreaders, and anyone else in your organization can all view pages without inflating the statistics.
Feel free to share my solution and use my extension to keep those cookies set.
I just had someone ask me this questions and stumbled upon this thread. I found an alternative solution using this Chrome Extension to block yourself from Analytics on sites.
There are two options.
Check for the IP address you have if they are between some range then you can set a range in the IP address filter. Excluding traffic
Setting cookies