We need optimizely to work on the new splash page so we can A/B test the call to action. What did we do/learn in https://bugzilla.mozilla.org/show_bug.cgi?id=1053817 that we can use? What's missing? How big of a hack is it?
I have a hack solution, given that fixing angular and optimizely isn't a good use of effort just before we drop angular (and EOY is eating all of my hours). If you can spin up duplicate homepages on alternative URLs with the content variations, we can still get optimizely to work for routing traffic between them and measuring conversion. (The existing optimizely/angular challenge is with modifying content on the fly). Once the URLs are in place on prod, ping me and it's quick for me to build out the test. @Bobby, as discussed on call just now. If you could check-in with Jbuck just to double check that when we ship the new login, the existing conversion tracking is still in place. This is the line of code in the existing auth client: https://github.com/mozilla/webmaker-auth-client/blob/702e98aa41ae60a841424d8e7a6511523839c70f/webmaker-auth-client.js#L320
jbuck says it should be working. @andrew: this feels like a good enough solution to ship this week. what do you think?
Flags: needinfo?(bobby) → needinfo?(andrews)
We're going to go with Adam's plan for now. Closing this.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.