Redirect *unsupported* browser traffic

ASSIGNED
Assigned to

Status

www.mozilla.org
Pages & Content
ASSIGNED
2 months ago
2 months ago

People

(Reporter: Eric Renaud, Assigned: pmac)

Tracking

(Blocks: 1 bug)

Production

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 months ago
Ask is to redirect all visitors coming from a URL that contains the word "supported" to a unique page. We see about 50K visitors referred to our us by sites that tell their users their browser is not supported. Out of these 50K, only 37% download. A healthy referral conversion rate is about 60%. If we can increase this avg conversion rate we'd gain 10K downloads per month.

We will develop the page in tandem with this work and file the dependency (the page relying depending on this work).

Per email, pmac suggested the following possible solutions: " . . . it would need to be done client side. A small percentage of traffic actually hits our servers, the rest are served by middle-tier caches and our CDN. Anything like this that would target individual users on a page needs to be done in JS. The JS method should work great though since JS is the tech collecting those stats in the first place."  " . . . we could do something custom or enhance Traffic Cop to be able to do this."
(Reporter)

Comment 1

2 months ago
Paul - could you please take the lead on this one, delegating as needed should implementation not require your own efforts? In the mean time, we'll get to work on creating the landing page for this.
Flags: needinfo?(pmac)
(Reporter)

Updated

2 months ago
Blocks: 1392379
Sure. What's the timeline on this? And are we talking about visitors to every page on the site, or just a few specific ones? Seems like trying this on a few hi-priority pages first would be a good start. Being redirected when trying to go to a non-firefox page might be pretty jarring.
Assignee: nobody → pmac
Status: NEW → ASSIGNED
Flags: needinfo?(pmac)

Comment 3

2 months ago
(In reply to Paul [:pmac] McLanahan ⏰ET needinfo? me from comment #2)
> Sure. What's the timeline on this? And are we talking about visitors to
> every page on the site, or just a few specific ones? Seems like trying this
> on a few hi-priority pages first would be a good start. Being redirected
> when trying to go to a non-firefox page might be pretty jarring.

Nearly all of this traffic is landing on one of three pages. We can stick to these:

/en-US/firefox/new/
/en-US/firefox/
/en-US/firefox/all/

So the request is to have any incoming URL that contains the word "supported" or "unsupported" AND is linking to one of the above pages and instead redirect them to this page: https://www.mozilla.org/en-US/firefox/new/?xv=unsupported-browser
You need to log in before you can comment on or make changes to this bug.