You should be able to see it fairly instantly if you set the Analytics date range to today.Awesome, installed and waiting data to flow in. Thank you very much!!!
7. Privacy.
You will not (and will not allow any third party to) use the Service to track, collect or upload any data that personally identifies an individual (such as a name, email address or billing information), or other data which can be reasonably linked to such information by Google. You will have and abide by an appropriate Privacy Policy and will comply with all applicable laws and regulations relating to the collection of information from Visitors. You must post a Privacy Policy and that Privacy Policy must provide notice of Your use of cookies that are used to collect traffic data, and You must not circumvent any privacy features (e.g., an opt-out) that are part of the Service.
I was implementing this a while before, and asked the analytics team, the answer was that I cannot track someone individually, and a username identifies a person (from that, mapping to the email is trivial). So I just settled for tracking usergroups (visitors, registered, moderators, admins) and not individual users. They seem to be fine if you aggregate users by any category that you can come up with, but not if you track them on an individual basis.Hmm... Will check into it. Although not sure a username which the user sets to anything they want is personally identifiable or not. Of course a user can choose to set their username to their real name, but that ultimately is a choice of the user, and is something they are knowingly exposing publicly already... Just like a user could set their user agent to their real name too.
But either way, will get better clarification.
Removed user name tracking per Google Analytics terms of service.
For now, yes... still trying to decide if I want to go through the complexities of generating unique identifiers that allows you to cross reference which user it is. It's either going to be some cross-referencing thing or just a registered/guest thing.Meh, does that mean we can't track members VS guests anymore? Is there a way to add this?
Nope... you lose functionality with universal analytics at this point...Is this working for new universal analytics tracing code ? Because i was using universal tracing code on modified google_analytics template, but for now your doubleclick .js is different than universal code
The dc.js JavaScript library is not supported in Universal Analytics during this phase. Users who need the following related features should wait until Phase 3 to upgrade:
- Remarketing
- Google Display Network Impression Reporting
- DoubleClick Campaign Manager Reporting
- Google Analytics Demographics and Interests Reports
Would a simple MD5 or similar hash do?Ya, I got clarification... You *can* use something to track an individual user, but it would have to be some non-public identifier you use to cross reference which user it is.
Might not be worth the effort of generating unique IDs for this purpose.
We use essential cookies to make this site work, and optional cookies to enhance your experience.