Closed
Bug 1208073
Opened 9 years ago
Closed 9 years ago
Funnelcake: Non-Fx users acquired through /hello/
Categories
(www.mozilla.org :: Analytics, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: garethc, Unassigned)
References
Details
(Whiteboard: [kb=1861961] )
I'd like to be able to understand retention among users that come in and download Firefox through our /hello/ product page.
Testplan: https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=52265141
Optimizely Test: https://app.optimizely.com/edit?experiment_id=3547462185
I'll place the Optimizely code from the test in a gist for code review. Will update the bug when ready. Thanks.
Gareth
Gareth
Reporter | ||
Comment 1•9 years ago
|
||
Josh,
Can you please turn on the waffle flag for Optimizely on /hello/?
Thanks.
Flags: needinfo?(jmize)
Comment 2•9 years ago
|
||
Gareth: you'll also need to create a release engineering bug like bug 1191472 to get a funnelcake created. You'll just need one since it isn't an A/B test.
Reporter | ||
Comment 3•9 years ago
|
||
Thanks Chris. I created a release engineering bug like the one you mentioned.
Since the non-fx user clicks on the download button from /hello/ and goes to scene 2. How do we trigger the correct build to download?
Depends on: 1208634
Comment 4•9 years ago
|
||
(In reply to Gareth Cull [:garethc] from comment #3)
> Thanks Chris. I created a release engineering bug like the one you
> mentioned.
>
> Since the non-fx user clicks on the download button from /hello/ and goes to
> scene 2. How do we trigger the correct build to download?
We'll have to add a URL parameter to the download link on /hello/ and then do an experiment on /new/ second scene that changes the URL to the save-as of Firefox to point to the funnelcake build.
Do we even have enough non-fx people that download from /hello/ to even run an experiment? How many per day go through this link now?
Comment 5•9 years ago
|
||
(In reply to Gareth Cull [:garethc] from comment #1)
> Josh,
>
> Can you please turn on the waffle flag for Optimizely on /hello/?
Based on the discussion so far in this bug, this test isn't ready to be enabled in production yet. I'm going to go ahead and clear my NI now, leafing the 'firefox-hello-optimizely' switch off in staging and production. Once all the prerequisites for enabling optimizely in prod on this page have been satisfied, please ping me again.
Flags: needinfo?(jmize)
Updated•9 years ago
|
Whiteboard: [kb=1861961]
Comment 6•9 years ago
|
||
I'm closing due to inactivity. Let's re-open when we are ready to work on this one. Thx.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•