3 ms·
How is that identity made available to anyone via GA? Google does not allow user identifiable PII in GA. Are you conflating the aggregate anonymized data in GA
by shostack 6y ago
How is that identity made available to anyone via GA? Google does not allow user identifiable PII in GA.
Are you conflating the aggregate anonymized data in GA with the user level visibility Google has into the raw data?
- hyperdimension 6y ago"...conflating the aggregate anonymized data in GA with the user level visibility Google has into the raw data?" Isn't that kind of the point? I see no difference. Who cares what individual site owners happen to be able to see if Google is going to monitor, track, send back (telemeter?) way more data and be able to analyze and store it forever? It's all about who might possibly get the data at a later date than who happens to house it presently. EDIT: In fact, come to think of it, why are there two things being 'conflated' here? Why is Google collecting more information about Google Analytics-using sites than it's exposing to site owners?
- sigmaml 6y agoI am not sure if you use and know how Google Analytics works. You are conflating two things here.
- lmkg 6y agoIn GA4, with Google Signals enabled, the "identity signal" is a psuedonymous identifier unique to your Google Account. I don't know exactly if it's a hash or a join key or what, but the point is it's stable across devices and domains. It does not directly contain PII. Google can join it to PII, website owners cannot. It is not aggregate. You can pull the hit-level data from GA, including the identifiers being used.