1245208 - Implement three variations of plugins page for increased newsletter signup

Status: RESOLVED FIXED

(Plugin Check Graveyard :: UI, defect)

Description

[Schalk Neethling [:espressive]]

Wanting to increase newsletter signup, we want to explore three variations of the current plugincheck page.

1) Form at the top
2) form in between results and FAQ with unknown plugins collapsed by default
3) form in between results and unknown plugins pushed down into it's own section below the newsletter but, above the FAQ(this variation also has the requirement of adding in page links to the unknown plugins and FAQ in the top results section.)

URL pattern for these will be:

1) /plugincheck/ (current)
2) /plugincheck/?v=b (variant b)
3) /plugincheck/?v=c (variant c)
4) /plugincheck/?v=d (variant d)

Comment 1

[Jennifer Bertsch [:jbertsch]]

Additional details:

1.  test is en-us only

2.  copy:  
Firefox + You
Get Firefox tips, tricks, news and more
Sign me up »

3.  test distribution:  40% en-US traffic, 10% to each variation
1) /plugincheck/ (current)
2) /plugincheck/?v=b (variant b)
3) /plugincheck/?v=c (variant c)
4) /plugincheck/?v=d (variant d)

4.  demo server links:
http://www-demo4.allizom.org/plugincheck/
http://www-demo4.allizom.org/plugincheck/?v=b
http://www-demo4.allizom.org/plugincheck/?v=c
http://www-demo4.allizom.org/plugincheck/?v=d

Comment 2

[Jennifer Bertsch [:jbertsch]]

v=b is form at top of page
v=c is form in between results and FAQ with unknown plugins collapsed by default
v=d is form in between results and unknown plugins pushed down into it's own section below the newsletter

Comment 3

[Jennifer Bertsch [:jbertsch]]

These all look correct to me, Schalk.

Michael and Troy - could you please review?  Thx.

Comment 4

[Troy Palmer]

(In reply to Jennifer Bertsch [:jbertsch] from comment #3)
> These all look correct to me, Schalk.
> 
> Michael and Troy - could you please review?  Thx.

Copy looks good, but we still have Mozilla branding at the top of the page -- should be Firefox, right?

Comment 5

[Michael Ham]

(In reply to Troy Palmer from comment #4)
> (In reply to Jennifer Bertsch [:jbertsch] from comment #3)
> > These all look correct to me, Schalk.
> > 
> > Michael and Troy - could you please review?  Thx.
> 
> Copy looks good, but we still have Mozilla branding at the top of the page
> -- should be Firefox, right?

All variations look good to me – each appears to be functioning properly. Troy is correct – looks like the page just needs the Firefox branding at the top.

Comment 6

[Schalk Neethling [:espressive]]

Thanks everyone! I completely forgot about the Fx logo change. Will implement that.

Comment 7

[Schalk Neethling [:espressive]]

Attachment: Link to Github pull-request: https://github.com/mozilla/bedrock/pull/3838

Comment 8

[[github robot]]

Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/c348e9e3556cf263c594921802d2480c513fedfb
Fix Bug 1245208, add plugincheck layout variations for newsletter signup testing

https://github.com/mozilla/bedrock/commit/e350b454b8df634dc4f560dcf7108749370ffad1
Merge pull request #3838 from schalkneethling/bug1245208-plugincheck-layout-variants-for-increased-newsletter-signup

Fix Bug 1245208, add plugincheck layout variations for newsletter signup testing

Comment 9

[Jonathan Petto [:jpetto]]

Optimizely experiment created:

https://app.optimizely.com/projects/246059135/experiments/4947131245

When ready to go live, URL targeting regex will be updated to:

^.*www\.mozilla\.org\/en\-US\/plugincheck\/?$

:cmore - r?

Comment 10

[Chris More [:cmore]]

(In reply to Jon Petto [:jpetto] from comment #9)
> Optimizely experiment created:
> 
> https://app.optimizely.com/projects/246059135/experiments/4947131245
> 
> When ready to go live, URL targeting regex will be updated to:
> 
> ^.*www\.mozilla\.org\/en\-US\/plugincheck\/?$
> 
> :cmore - r?

Changes:

* appended variation letters to the start of each variation name to make reporting more understandable 

Questions:

* For the URL target: ^.*www\-demo4\.allizom\.org\/en\-US\/plugincheck\/?$, is the ? at the end for matching the literal ? or that the optional trailing slash?

Everything else looks good and another simple traffic cop experiment with no goals. Is the goal not measurable within Optimizely or are you exclusively measuring it within GA?

Comment 11

[[github robot]]

Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/5083c4984b25a47d270a125119ec3a899f5915fc
[bug 1245208] Temporarily skip plugincheck newsletter test on non-Firefox browsers

https://github.com/mozilla/bedrock/commit/c57befe1f7e6e763a2884fad75a5844fac25220e
Merge pull request #3842 from alexgibson/disable-plugincheck-tests

[bug 1245208] Temporarily skip plugincheck newsletter test on non-Firefox browsers

Comment 12

[Jonathan Petto [:jpetto]]

(In reply to Chris More [:cmore] from comment #10)
> 
> Changes:
> 
> * appended variation letters to the start of each variation name to make
> reporting more understandable 
> 
> Questions:
> 
> * For the URL target: ^.*www\-demo4\.allizom\.org\/en\-US\/plugincheck\/?$,
> is the ? at the end for matching the literal ? or that the optional trailing
> slash?
> 
> Everything else looks good and another simple traffic cop experiment with no
> goals. Is the goal not measurable within Optimizely or are you exclusively
> measuring it within GA?

Thanks for renaming the variations - will remember that for future experiments.

The ? at the end was to optionally match trailing slash. Since we add trailing slashes in bedrock, I removed that bit of the regex for easier comprehension.

Thanks cmore!