Closed
Bug 1127905
Opened 10 years ago
Closed 10 years ago
Create HTML pages on AMO for Firefox First Run Add-On Testing
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cmore, Assigned: jpetto)
References
Details
Attachments
(3 files)
We are going to be creating a few Firefox First Run variations and testing the impact of usage on people who install add-ons during their onboarding experience. Since we want these to be one-click, the button will have to be an iframe on addons.mozilla.org, because of the existing whitelisting in Firefox.
Jon Petto will be working on two small HTML pages similar to bug 1063170. We can store these HTML pages in a /static/html/mozorg/ directory.
We are on a tight deadline here and need to get this test launched on Feb 12th thus these pages need to be coded, reviewed, merged, and pushed to AMO the week of Feb 9th for testing.
Reporter | ||
Updated•10 years ago
|
Assignee: nobody → jon
Assignee | ||
Comment 1•10 years ago
|
||
PR marked as "do not merge" in case Lightbeam XPI URL changes in the next day or so.
Reporter | ||
Comment 2•10 years ago
|
||
clouser: The next AMO push is Feb 11th. We want to launch our test for 2 weeks so we have enough data before Firefox 36 comes on at the end of the month. Is it possible to get the AMO push changed to Feb 10th (or earlier) so that we can QA the entire test? Let me know. Thanks.
Flags: needinfo?(wclouser)
Reporter | ||
Comment 3•10 years ago
|
||
Pages are pushed to prod! Thanks AMO team.
https://addons.mozilla.org/static/html/mozorg/lightbeam.html
https://addons.mozilla.org/static/html/mozorg/ghostery.html
Flags: needinfo?(wclouser)
Reporter | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•10 years ago
|
||
We are going to have to add GA to these HTML pages to get conversion rates for these buttons. Without GA, we will have no idea on how many people interact with them.
Add this GA AMO tag in the head of these pages:
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-36116321-7']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
Then onclick of each of the "add to Firefox buttons", push the following events for each page:
_gaq.push(['_trackEvent', 'add-on installs', 'mozorg iframe clicks', 'lightbeam']);
_gaq.push(['_trackEvent', 'add-on installs', 'mozorg iframe clicks', 'ghostery']);
We should also create a generic function onclick to push back to the parent frame so that we can switch content on the www.mozilla.org page after someone interacts with them. I would probably pass along in the function which add-on was clicked so we can tell if one or both have been clicked and if we want specific content on the parent frame page to change.
jpetto: I would pause your current work and get these changes out to the AMO team to do on their next push since they were so kind on doing an out-of-cycle push already.
Status: RESOLVED → REOPENED
Flags: needinfo?(jon)
Resolution: FIXED → ---
Comment 5•10 years ago
|
||
code freeze is friday (2 days)
Reporter | ||
Comment 6•10 years ago
|
||
(In reply to Wil Clouser [:clouserw] from comment #5)
> code freeze is friday (2 days)
Ok, jpetto is working on it now. It is a quick change and we should have added it before, but we thought we could capture the event from the parent frame, but that's a browser no-no.
Assignee | ||
Comment 7•10 years ago
|
||
Flags: needinfo?(jon)
Reporter | ||
Comment 8•10 years ago
|
||
jpetto: your testing on -dev is fine?
clouserw: will this be pushed out on the 11th?
Flags: needinfo?(wclouser)
Flags: needinfo?(jon)
Assignee | ||
Comment 10•10 years ago
|
||
:cmore - Yep, tested locally iframing the buttons from addons-dev and cross-frame communication is happening. I also saw GA events firing on the buttons. You can confirm the GA stuff on dev for double-check purposes:
https://addons-dev.allizom.org/static/html/mozorg/ghostery.html
https://addons-dev.allizom.org/static/html/mozorg/lightbeam.html
Flags: needinfo?(jon)
Reporter | ||
Comment 11•10 years ago
|
||
Verified in GA!
Reporter | ||
Comment 12•10 years ago
|
||
These were pushed yesterday and verified:
https://addons.mozilla.org/static/html/mozorg/ghostery.html
https://addons.mozilla.org/static/html/mozorg/lightbeam.html
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•