[Q2 FX Landing Page Testing] Project Tracking Bug - Glow Integration

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
8 years ago
7 years ago

People

(Reporter: christine.brodigan, Assigned: christine.brodigan)

Tracking

unspecified
x86
macOS
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Assignee)

Description

8 years ago
Objective:

We would like to test a new landing page design that integrates geo-location data gathered from glow.mozilla.com http://www.mozilla.com/firefox/new

There are a number of ways to do this, some ideas include:

* A user living in Portland Oregon would land on http://www.mozilla.com/firefox/new and receive custom messaging about the number of downloads from Portland, Oregon

* A user living in the UK would land on http://www.mozilla.com/firefox/new  and receive custom messaging about the number of downloads across all of the UK

* Glow creators Jeff & Potch cc'd for ideas/advice

Some conditions:

* Data should be impressive (no less than …), so a user from a tiny city wouldn't get messaging, "No one has downloaded Firefox in your city" or "less than 100 people" etc.
* Use case for obscure or less popular locations should be included in design, so we're able to serve an equally interesting page even when the data is less fun on the surface
* Design can include variations, because we're using this as a test, so have fun!
* Design should be conducive to a user clicking into glow.mozilla.org and exploring more data
* Design should use the existing template http://www.mozilla.com/firefox/new elements (navigation, colors, heading, sub-heading - but integrate new imagery/ux for geo-data) - the experience from the download page to glow should feel like they belong together:)
* Design should include a specific privacy notice that covers any personal information being collected from users (e.g. Every website can tell where you are located, we're just being transparent and showing you your data…..)  to inform users about our data practices and provide a link to our privacy policy. Legal & Liz C. will provide the notice text.
* Design should NOT add weight to current lightning-fast download time

Other Relevant Information:

Wiki:
https://intranet.mozilla.org/Metrics/Websites#2011_Q2_Test_Plan

Etherpad: 
http://etherpad.mozilla.org:9000/jHnA3hSqD4
On the backend glow sees location data like Country:State/Region:City:Latitude:Longitude. We're not keeping lat/long in our region totals on the frontend since it's not useful to us. And specific region data is buried in a huge JSON dump for the whole world, so our current data sources won't be useful here.

A better API would take the user's lat/long and return specific numbers for their continent, country, region, city. The client can then decide what it wants to show.

How is the geolocation going to happen? Will it be based on IP or will it use navigator.geolocation?
(Assignee)

Updated

8 years ago
Depends on: 657725
(Assignee)

Updated

8 years ago
Depends on: 657730
(Assignee)

Comment 2

8 years ago
(In reply to comment #1)
> On the backend glow sees location data like
> Country:State/Region:City:Latitude:Longitude. We're not keeping lat/long in
> our region totals on the frontend since it's not useful to us. And specific
> region data is buried in a huge JSON dump for the whole world, so our
> current data sources won't be useful here.
> 
> A better API would take the user's lat/long and return specific numbers for
> their continent, country, region, city. The client can then decide what it
> wants to show.
> 
> How is the geolocation going to happen? Will it be based on IP or will it
> use navigator.geolocation?

Over to you James/Steven, can you reply back to Jeff?
Assignee: nobody → jlong
The whole point of the Geolocation API is to let the user choose to be located or not. So I think we should use this. It will only be available on recent browsers and only IE9+ though.

But it might also be less effective in terms of convertions than IP detection because it won't display the results right away but after a user interaction. Some users might also decide to leave the website because they are afraid by us asking geoloc information. But we'll see when testing.
(In reply to comment #3)
> The whole point of the Geolocation API is to let the user choose to be
> located or not. So I think we should use this. It will only be available on
> recent browsers and only IE9+ though.

What is the normal browser+version spread for this page?
 
> But it might also be less effective in terms of convertions than IP
> detection because it won't display the results right away but after a user
> interaction. Some users might also decide to leave the website because they
> are afraid by us asking geoloc information. But we'll see when testing.

I'd expect IP detection to be more effective since they don't have to interact with the page before we hit them with impressive data.
I'm copying Alex and Doug Turner because they know more about geolocation privacy issues than I do, but I'm uncomfortable with the idea of identifying where a website visitor is coming from and displaying that without their prior consent.

Updated

8 years ago
Target Milestone: --- → 2.7
(In reply to comment #5)
> I'm copying Alex and Doug Turner because they know more about geolocation
> privacy issues than I do, but I'm uncomfortable with the idea of identifying
> where a website visitor is coming from and displaying that without their
> prior consent.

Sorry I'm late to the game. I was initially thinking this could show some stats on their country based on locale. More general information that doesn't feel as intrusive.

But I'd love to hear more from folks who specialize in privacy. Technically, a lot is feasible hear so it just depends on what we feel is appropriate.
I talked to Alex about this briefly. I think our preference would be not to do this, but if you feel it has real value, then it may need to be opt in, depending on how we're getting the info. That could be done, for example, by displaying the generic landing page with a message or pop-up that says something like "Would you like to see Firefox download numbers for your area? Click here to enable us to see your location. More Info [link to section of privacy policy on geolocation]."

If we do this, whether opt-in or opt-out, we'll have to update the websites privacy policy, it doesn't address geolocation. That will take some time - the wording has to be drafted and reviewed and then posted to governance for comment.

Maybe it would be good to have a meeting to talk through the options and what each would require. If you'd like to set something up, make sure Alex Fowler is included.
(Assignee)

Comment 8

8 years ago
Hey Liz! Thanks for adding Alex, I've actually had a separate bug open under legal for him to address this more privately for a few weeks now: Bug 652900

I will set up a meeting, but we would like to proceed in a very general way and with a very targeted and limited testing audience (e.g. starting with the continent or just picking 7 major cities like New York, Columbia, London, etc.). I think there is an elegant and friendly way to do this to test the idea out and if it does increase conversion and create a highly positive experience, we could then figure out how or if to scale.

Something to also consider is how Firefox is very clear on privacy and location-aware browsing: http://www.mozilla.com/en-US/firefox/geolocation/

Unlike a lot of companies and browsers we aren't using or selling the user's data and in fact, any website on the web is able to detect where a user is coming from, it's the challenge of being transparent about it and doing something useful with the information.

Meeting invites incoming!
Thanks Chrissie, I'd forgotten about the other bug.
Assigning to nobody until we figure out how we're actually going to do this.
Assignee: jlong → nobody

Updated

8 years ago
Assignee: nobody → cbrodigan
Target Milestone: 2.7 → 2.8
(Assignee)

Comment 11

8 years ago
Closing this bug, we'll revisit geolocation outside of Glow at a later time.

Thank you all!
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
Component: www.mozilla.org/firefox → www.mozilla.org
Product: Websites → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.