With the new release of ga.js this is possible. In the old days a fired event immediately after a trackPageview would cause Google Analytics to report a 0% bouncerate for that visit. But sometimes you don't want that behavior because the event is not always triggered by the visitor.
For instance: I track page load times the same way Google Analytics does, but in an unsampled way (Google only meausures 10%). To do that I fire an event immediately after the trackPageview, but I do that in another profile with a different UA-XXXX-Y number so it won't affect my bouncerates. But now we have an extra parameter:
_trackEvent(category, action, opt_label, opt_value, opt_noninteraction)
If you set this opt_noninteraction (boolean) to true it wil not affect bouncerates!!! That makes it possible to:
I can't believe it. Google just announced a new 'feature' for their search results pages. If a user is logged in he will be redirected to the secure (SSL) version of their search engine. The main reason (so they claim) is the user's privacy... when a user does a search and navigates to a site, that site will only be able to see it's a visitor from Google Organic...yes, without the keyword.
Why does this suck?
- If Google really had a clear focus on a user's privacy they also wouldn't send the keyword along with an AdWords click (as Yoast tweets). Right now only half of the results are privacy-protected and the other (paid) half not.
- Google claims it will not affect a lot of users, that could be right on average. But for some sites a lot of their target groups are logged in to their Google Analytics, Google Reader, Youtube, Gmail, etc. All those visitors will also be logged in on the search results, and that could mean serious loss of information about the used keywords.