I am in particular concerned with legal implications due to strong privacy legislations. However, I was also thinking about performance and false results by users blocking it.
7 Answers
I'm not a lawyer, take my advice as only that. You might want to speak to one about this issue.
However, as long a you provide a good privacy policy on your site, normally in the footer of your site, you should be good to go.
Also, as with all JavaScript, you want the benefits of your tracking to out weigh the costs. Basically, is the information producing profits over cost.
Google analytics can slow your page load time, just like every element on your pages does.
As far as false results go, there is not much you can do. The best thing to do is to really analyze the results you get back, over time. However, getting perfect data collection is not the point of tracking software. The software is made to help you make more objective decisions about your website. This is opposed to not having any data at all.
The software is made to help you optimized your content and know what pages work best.
Don't let numbers be the only thing you look at.
- 2,036
- 1
- 18
- 19
Google Analytics does not collect any personally identifiable information and it breaks their terms of use to modify the code to do that.
Google have always recommended putting their code at the bottom of the page specifically so that downloading the script doesn't hold up the page loading and display. They've also recently introduced asynchronous tracking code which should pretty much eliminate these kind of problems.
As mentioned elsewhere, web analytics is not about absolute numbers but about making useful comparisons (leading to actionable insights) so unless you think your audience is predominantly made up of Google/Javascript blockers, it won't prevent you getting useful insights.
- 298
- 2
- 8
Anybody who blocks JavaScript won't show up on Google Analytics. I don't know of that many people who deliberately block Google Analytics itself, but I do know that Analytics under-reports traffic. On one Ajax-based site I run, it is almost accurate, but on another static HTML/CGI site I run it is under-reporting (only (very approximately) 80% of actual visitors show up in Google Analytics), so somehow or other it is getting blocked a lot. Another thing is that it doesn't show up any web crawler or robot traffic, and doesn't show up hotlinked images and other kinds of abuse.
As for delaying the load, loading the same piece of JavaScript again and again on each page won't slow things down since the JavaScript will be cached anyway. It is detecting the time on the page somehow, so it must also be phoning home on page load and unload, which has to involve a short delay. However I honestly cannot detect that or notice it at all.
As far as I know, there is no requirement to have a privacy policy in order to use Analytics (unlike Adsense).
I strongly recommend comparing the output of any analytics service to your server side stats. More often than not, you'll find that they don't agree. This is mostly (as you said) due to people blocking JS, or just outright sending GA requests to localhost.
As far as the legal ramifications, I can only offer this advice:
When in doubt, don't.
You really need to discuss this with an attorney, who can:
- Advise against it
- Help you write a privacy policy
Its a unique enough issue to raise here, but you should really seek legal advice from legal professionals :)
- 6,586
- 39
- 46
You site will be a little slower but it should be relatively unnoticed to most if not all users. Google works very hard to keep their footprint small.
As for legal implications, contacting a lawyer is a good idea. I am not a lawyer so take my advice as is. Most sites use Google Analytics because it is free, unobtrusive, and works well. Also, Google doesn't collect any info you enter into a site just what and where you click.
- 12,778
- 4
- 42
- 62
Like others have answered before, I am not a lawyer.
Regarding performance, Google recently introduced a new async tracking script which makes the performance issues mostly noticeable to the users (obviously it is still using resources, but since the page loads first the user can't tell).
I have tried the new script and it is faster.
http://code.google.com/apis/analytics/docs/tracking/asyncUsageGuide.html
- 301
- 1
- 5
Another item you may want to consider is whether Google is providing you with enough value to pay for the information you are giving them about your site's data, relevance of specific pages, etc.
They already own a large proportion of this for your landing pages because of their overwhelming search domination, but by installing Analytics you're giving them ALL of it.
Google says that they don't use the information to determine your site's rankings, but they're measurement geeks, and of course they're analyzing the data in aggregate to improve their services.
- 4,133
- 3
- 27
- 30