On Thursday, May 1, 2014 10:58:43 AM UTC-4, Stormy Peters wrote: > On Wed, Apr 30, 2014 at 3:09 PM, Florent Fayolle < > > florent.fayoll...@gmail.com> wrote: > > > > > The question about using GA or not is crucial but rather a long-term > > > question [1]. > > > What worries me the most here is the AJAX requests made at each click on > > > that page. > > > > > > I agree with Benoit: we can't reassure our users by some little clauses > > > accessible on some page on the web, because they won't read it. The users > > > will focus on the screenshot of the tweet I posted above, think that > > > Mozilla is tracking everything they do on that page, and laugh at what we > > > say about Mozilla doing for their privacy. So, at least, that's bad for our > > > image (especially in this time where Prism has been revealed). > > > > > > Also, I wonder the purpose of collecting this data and especially by this > > > way (that is, sending for each click). It looks like you would like to know > > > how the user navigates in the tutorial. Maybe you (or the team in charge of > > > this page) could clarify this? Wouldn't knowing the number of people going > > > through the tutorial be enough? > > > > > > > +1 to sharing what we are trying to measure. Gareth is the right person to > > help us and the web productions team also has a blog where they could share > > info like this. > > > > Stormy
Hi Florent / Benoit, I work on the Web Productions team as our Web Analytics and Optimization Engineer and can provide you with some context around what and why we track what we do on the whatsnew page. First, I'd like to thank you for being an active community member and for engaging with Mozilla on this topic. Privacy is very important to Mozilla and me personally, and hopefully my explanation here will give you some insight as to how we leverage Google Analytics to improve the user experience on the web. Let me start off by saying that we do not track or send any personally identifiable information to Google. Doing so would not only be against our internal policies, but also that of Google. As an Analytics professional, this is also a line I would not cross. And to re-enforce our commitment to privacy, we actively anonymize ip address data along with any requests that are being sent back to Google. This was actually a community driven suggestion that we implemented. You can read up more on this here: https://bugzilla.mozilla.org/show_bug.cgi?id=946705 So to answer your questions: What are we tracking? We are tracking engagement with links and buttons as the user navigates through the on boarding flow, which we analyze in aggregate. Why are we tracking this? Ultimately, we want our users to be able to get the most out of their experience with the Firefox browser. So we created an onboarding flow that educates the user about some new features and how to use the product. The content within the flow was developed and presented in 4 steps and we used event tracking to understand if people were dropping off at specific stages within the flow. If we were to find out that we were losing a significant number people at the first step in the tutorial, we would go back and review the content presented in that section and see if we can tweak or re-work it. Ultimately, the end goal of this flow is to present content that a user can understand and successfully navigate their way through an onboarding process and be more educated about the changes we made to the new Firefox. If we can do that, then hopefully we have created a more satisfying experience for the user as they browse the web. If anything is not clear, please let me know. I'll be happy to respond back. We are just trying to leverage the data from this to improve our user's experience with our product. Thanks, Gareth _______________________________________________ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
