redirect /newsletter to /newsletter/firefox

RESOLVED WONTFIX

Status

www.mozilla.org
Pages & Content
RESOLVED WONTFIX
a year ago
a year ago

People

(Reporter: jbertsch, Unassigned)

Tracking

Production

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [q4 sprint 4])

(Reporter)

Description

a year ago
Let's redirect /newsletter to /newsletter/firefox since /newsletter/firefox is our highest converting page
Duplicate of this bug: 1316201

Updated

a year ago
Whiteboard: [q4 sprint 2]
Assignee: nobody → mozilianmainak
Status: NEW → ASSIGNED
Assignee: mozilianmainak → nobody
Status: ASSIGNED → NEW

Updated

a year ago
Whiteboard: [q4 sprint 2] → [q4 sprint 4]

Comment 2

a year ago
Decision today was to leave page as-is, no redirects
We will revisit this in a (epic, possibly) user story in a later sprint as page design to make /newsletter the top level landing page with CTAs for multiple (TBD) newsletters.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INVALID

Comment 3

a year ago
Eric - We have a huge drop off in conversions here because it reads like a Mozilla newsletter when it is in fact a Firefox one and it has the most organic traffic to boot.

Our prior discussion was how can improve the user experience, not lose the organic traffic and improve conversions against our 2017 email goal. The alternative was to update it to be more like /newsletter/firefox which is the best performing LP now. 

Unfortunately a landing page with multiple CTA's isn't an option in our current email set-up so that isn't a solid solution so I'd like to discuss/revisit this decision.
Status: RESOLVED → REOPENED
Flags: needinfo?(erenaud)
Resolution: INVALID → ---

Comment 4

a year ago
Gotcha, thank you - it's with your guidance and direction that we'll proceed on the page. This bug was specific to implementing a redirect, which was deemed as something we don't want to do (therefore marked as closed/invalid).

I'm going to send you our work request intake form and will create a new bug with the information provided and we'll figure how best to update /newsletter to leverage the incoming organic search for conversions.
Status: REOPENED → RESOLVED
Last Resolved: a year agoa year ago
Flags: needinfo?(erenaud)
Resolution: --- → INVALID
Woah! Hold yo' horses. Michele and I synced. She didn't realize that we had met about this, nor the options to move forward and the implications of those options.

Big take-aways:

1)  While this page had a lot of traffic - it was all snippet traffic. There's not significant organic traffic on this page to warrant a lot of work.

2) This page shouldn't be redirected b/c of the Basket API code that depends on this /newsletter page.

3) It seemed that this page didn't convert as well as the others - but that's b/c it had a lot of snippet traffic. Now that snippet traffic is pointing to the /newsletter/mozilla and /newsletter/firefox pages, those pages' conversions have gone down, so this page's conversion rate is good.

4) Given points 1-3 above, no redirect needs to happen.

5) What does need to happen to make this page relevant is copy change:


Subscribe to monthly updates and keep current with Mozilla news, including the latest tips and tricks for getting the most out of your Firefox browser. It’s the perfect way for us to keep in touch! 

Change to:

Subscribe to updates and keep current with Mozilla news. It’s the perfect way for us to keep in touch! 


That way we're in line with delivering what we're promising.


Can this copy change happen?

Then if/when we're ready to redesign this page to accommodate other signup forms in the future, we can file a new bug and do the intake form.

Sound like a plan?
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Filed new bug for the new plan:

Bug 1337123 - Update language on /newsletter


I'll file a new bug if/when we go the route of needing a new standalone opt-into everything page.
Status: REOPENED → RESOLVED
Last Resolved: a year agoa year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.