Closed Bug 1165453 Opened 10 years ago Closed 10 years ago

Optimizely test on Pocket button color for /whatsnew 38.0.5

Categories

(www.mozilla.org :: Analytics, defect)

Production
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ckprice, Assigned: ckprice)

References

Details

(Whiteboard: [engagement-fxGrowth-2015])

In bug 1162757 comment 5 final designs were approved for /whatsnew. This bug is to track implementation on TWO variants of the dark blue color we see in the final approved design. Variants are TBD, but should stick to the extended Mozilla color palette. :ckprice to implement the test
I'll make sure to include a waffle switch on the base template in Bug 1162759 to facilitate this.
Also, 60kb of render blocking JS to test a button color *swoon*. Thankfully this is only temporary ;)
Hey Ty, We'd like to do a limited test of changing this button color. ALT 1 - same flat green we use for the download buttons ALT 2 - Pocket red, or a different red from our extended palette if that's preferred. Thanks!
Flags: needinfo?(tflanagan)
Sorry, the ask for you Ty is to confirm you're okay with a limited test for these two options, and supply a recommendation for the ALT 2 color.
Out of curiosity, what's the reasoning for wanting to test 2 CTA colors here? Im hesitant to introduce a different color for a CTA when the dark blue is what we have been using lately on this blue background. Has the dark blue CTA not being performing well on other pages?
Flags: needinfo?(tflanagan)
Matej cleared up the confusion. I do want to make sure though going forward that we dont venture into testing too many different CTA colors. For this pocket WN page, we can use our bikeshed magenta color: Normal state: #E14164 Hover state: #FA5176
Test complete https://app.optimizely.com/results2?experiment_id=2976370185&token=5e5298978e4454f8b0e8#view=2 No improvements with the Red or Green buttons. No recommended action items.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Waffle flag has been switched off.
You need to log in before you can comment on or make changes to this bug.