4202Re: Odd things noted with Google Analytics
- Nov 21 6:22 AMWe can perhaps agree that it escalated the issue beyond anyone's
expectation. The problem is here in Europe it put website owners into
breaking the law.
causes a cookie to be created in the visitors browser. It appears to
be from the domain, but isn't. Thus an illusion of security as it
peek into the other cookies sent from the same domain. On the other
hand a cookie from a subdomain used for data collecetion would be
under far more control.
For web statistics only 1 cookie is needed, so I would be very
interested to learn why GA creates 4 and what the contents are. That
information is yet to be found. Also it seems that the different
cookies GA uses has the same values even if from to different
--- In email@example.com, "whitingjo" <jo@o...> wrote:
> Johan is correct in saying this problem (web site owners not
> the new free GA service.
> How many business sites pre-GA do we know that set cookies yet
> hopefully the release of GA will educate web site owners...
> Secondly, I am not sure what you mean by 'injecting cookies into
> browser'. There are several methods for setting cookies
> tells your server to set a few cookies in the visitors browser.
> The value of the cookies are also captured by the js code and
> then sent back to Google servers for collection via a call to a
> 1x1 gif file on their servers. There is nothing hiiden or
> surrepticious about this.
> I think the reason that GA 'pushes' the js file to the account
> holders pages, is simply to cut down on support calls - we found
> a lot of users were editing the js themselves!
> Jo Whiting
> --- In firstname.lastname@example.org, "Eric Peterson"
> <eric.peterson@g...> wrote:
> > I'm not up-to-date on cookie legislation overseas but it goes
> > saying that any company deploying ** any ** analytics application
> > I poked around at the Google Analytics site and didn't find any
> > guidance but will suggest it next time I chat with those folks.
> > Based on my research on cookies, the strategy Google Analytics is
> > using is the least likely to be deleted. It is not a third-party
> > cookie, it is not a contractual or mapped first-party cookie, it
> is a
> > true first-party cookie. Whether the cookie comes from the
> > domain or the site domain is a technical decision that each vendor
> > makes and is theoretically able to change.
> > Perhaps from a transparency standpoint this is dodgy, but from a
> > accuracy standpoint, this strategy is the recommendation.
> > I have not seen any published data regarding how many Internet
> > are opting out of tracking domains but given that opting-out
> > you at accept a cookie (so the system knows not to track your
> > right?) and given that cookies are being deleted at some rate, I
> > suspect opting-out is far less likely than consumer use of
> > anti-spyware to "protect" themselves or occassional manual
> > I mean think about it ... if you don't want to be tracked you
> > visit dozens of different opt-out pages (at each of the vendors)
> > every time you delete your cookies you have to repeat that
> > Unlikely, in my opinion.
> > If the GA code is removed, the cookies may remain but are
> > rendered useless.
> > Eric Peterson
> > --- In email@example.com, "webbanalys"
> <webbanalys@y...> wrote:
> > >
> > > I've found some odd things going on with Google Analytics (GA),
> > > one of them is connected to the statement Eric made that GA
> > > party cookie (FPC). It seems that GA DOES NOT send FPC from the
> > > collection domain at all. Instead the code will perform the
> > > of sending cookies looking as if they were from the website
> > > itself! If I am wrong then please correct me.
> > >
> > > It seems as if a massive amount of websites not using cookies
> > > now are sending out 4 new ones and thus as a result not
> following the
> > > law which states the following (at least for us in Europe):
> > >
> > > EU-directive 5.3 on integrity and communication, every visitor
> to a
> > > website containing cookies is entitled information:
> > >
> > > * that the website contains cookies,
> > > * how these cookies are used,
> > > * how cookies can be avoided.
> > >
> > > Even worse is that if users select to opt out to avoid the GA
> > > generated cookies then ALL cookies from the domain in question
> > > be blocked, even the ones that are used to keep user details
> > > enhance website functionality!
> > >
> > > If the GA code is removed the created cookies will remain, and
> > > actually is set to last until 2038. Given the recent coverage
> > > users deleting cookies this adds fuel to the fire, sending
> cookies in
> > > this fashion is rather dodgy.
> > >
- << Previous post in topic Next post in topic >>