Can we please add a Google Analytics Event to bedrock Firefox Download buttons for when a user downloads a Firefox Browser on click, or when a user lands on the download page from an external referrer. Please set the event with the following information: _gaq.push(['_trackEvent', category = 'Firefox Downloads', action = 'click' or 'auto', label = 'Firefox' OR 'Firefox Beta' or 'Aurora' OR 'Nightly' OR 'Firefox for Android']); Note: Where action = 'auto'. This pertains to cases where a user lands directly on a download page (download.html) and the download starts. We would need to determine if page load was from an external referral in this case. Also, there is secondary links underneath the button that we would also like to track with the following: _gaq.push(['_trackEvent', category = 'Firefox Links Under DL Button', action = 'click', label = 'System and Languages' OR 'Whats New' or 'Privacy']);

See also Bug 891562. The /new page creates a virtual page view for the firefox download. Should that be entirely replaced with events?

From Gareth on Bug 891562: > For clicks on the 'Firefox for Android Button', please call > window._gaq.push(['_trackEvent','Firefox Downloads','click','Firefox for Android']);

Gareth replied via IRC that the event tracking should replace the virtual page views currently used on /new.

Thanks, Mike! Gareth: would you consider keeping the virtual page view in temporarily and adding the events until it is live and we compare the data? I would hate to lose the download data if there was a problem.

Sure. That's not a problem Chris. Let's do that. Thanks!

Hi gauthierm, Just wondering if you have an update on this? I'm not seeing any event data being passed to GA when I test this. Can you please confirm the events mentioned above are implemented along side the virtual page view? Thanks. Gareth

Gareth, this bug has not been worked on yet. None of the events are being set for download button clicks. The virtual page view is still being sent on the /new page.

Added this bug into Kanbanery backlog...

Taking.

:garethc Do you need the platform info for desktop and the channel name for Android? We could have 12 labels for now: * Firefox Aurora for Windows * Firefox Aurora for Linux * Firefox Aurora for Mac OS X * Firefox Aurora for Android * Firefox Beta for Windows * Firefox Beta for Linux * Firefox Beta for Mac OS X * Firefox Beta for Android * Firefox for Windows * Firefox for Linux * Firefox for Mac OS X * Firefox for Android

Hey Kohei, Thanks for picking this up. I don't need the platform info as I can get this already in GA. Gareth

(In reply to Gareth Cull [:garethc] from comment #11) > Thanks for picking this up. I don't need the platform info as I can get this > already in GA. Okay!

I also want to make sure that these events are added to all Bedrock download buttons that are generated on any page and not just /firefox/new/. We should keep the virtual page view on /firefox/new/ for the time being until the event has been in production for a period of time. Thanks!

(In reply to Chris More [:cmore] from comment #13) > I also want to make sure that these events are added to all Bedrock download > buttons that are generated on any page and not just /firefox/new/. We should > keep the virtual page view on /firefox/new/ for the time being until the > event has been in production for a period of time. I got it. BTW, I just noticed /products/download.html was not yet migrated to Bedrock (Bug 850753). I'm afraid it makes the event tracking complicated. Should I tackle it first?

I rather mean Bug 874913.

(In reply to Kohei Yoshino [:kohei] from comment #14) > (In reply to Chris More [:cmore] from comment #13) > > I also want to make sure that these events are added to all Bedrock download > > buttons that are generated on any page and not just /firefox/new/. We should > > keep the virtual page view on /firefox/new/ for the time being until the > > event has been in production for a period of time. > > I got it. > > BTW, I just noticed /products/download.html was not yet migrated to Bedrock > (Bug 850753). I'm afraid it makes the event tracking complicated. Should I > tackle it first? We are not migrated download.html as bug 850753 is wontfix. Bug 874913 describes we want to do and that includes changing all download buttons to point to the second scene of /firefox/new/, e.g. #download-fx. Once all download buttons point to /firefox/new/, download.html will be deleted and redirected to /firefox/new/. Can you add the event and keep the button pointing to download.html or does it make sense to change the target for the download buttons and then add the tracking?

(In reply to Kohei Yoshino [:kohei] from comment #15) > I rather mean Bug 874913. Yes, that. :) If you think that changing the targets for the buttons would make the event tracking easier, then yes, I think that is better to do first. It would get the traffic away from download.html even quicker!

If a GA tracking won't added to download.html, it should be okay... I was thinking such a case where 2 events could be logged: 1. A user clicks a download button on /firefox/features/ _gaq.push(['_trackEvent', 'Firefox Downloads', 'click', 'Firefox']); 2. The download will be started automatically on /products/download.html _gaq.push(['_trackEvent', 'Firefox Downloads', 'auto', 'Firefox']);

OK this is not up on demo1, Gareth can you please test GA events are coming through as expected on all download buttons? https://www-demo1.allizom.org/en-US/ Given the custom behavior on the download button on /firefox/new, this one button needs it's own logic that is separate to the rest of the site. We need to make sure this page is specifically working correctly, as well as all other download buttons on other pages. Once we're happy with the GA data, I would like to get QA to give this a run through on various operating systems before we merge.

(In reply to Alex Gibson [:agibson] from comment #20) > OK this is not up on demo1, Gareth can you please test GA events are coming > through as expected on all download buttons? Sorry for the typo, I meant "now up on demo1"

Great. Thanks Alex! I'll check it out and will update the bug.

Still testing, but one thing i noticed so far (in both Chrome and Safari) is that we are not firing an event when the visitor lands on: https://www-demo1.allizom.org/en-US/firefox/new/#download-fx Can we please fire the following if the visitor lands on the second scene of the download page? _gaq.push(['_trackEvent', 'Firefox Downloads', 'auto', 'Firefox']); Gareth

I've together a test scenerio spreadsheet which we can add to here: https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AqvoOaUZL-jwdGFMV25jdHNsQ2tkamRDbzlwTXNxbkE#gid=0 Also, i was wondering about some events....it looks like in chrome, after i click on the download button on /performance (and others so far), that the event gets triggered on load of the download.html?product page. I'd like to be able to have this on click of the /performance btn. This would enable me to run a site wide report to see where all of our downloads are originating from. Can you please confirm?

My bad, looks like I have dropped the auto-started event at some point. I'll add it soon.

(In reply to Gareth Cull [:garethc] from comment #23) > Can we please fire the following if the visitor lands on the second scene of > the download page? > _gaq.push(['_trackEvent', 'Firefox Downloads', 'auto', 'Firefox']); Fixed! (In reply to Gareth Cull [:garethc] from comment #24) > Also, i was wondering about some events....it looks like in chrome, after i > click on the download button on /performance (and others so far), that the > event gets triggered on load of the download.html?product page. I'd like to > be able to have this on click of the /performance btn. This would enable me > to run a site wide report to see where all of our downloads are originating > from. Can you please confirm? Hmm, when I debug with Chrome's console, the _trackEvent looks processed on click. Same on Safari and Firefox. I haven't made any change on /products/download.html, so the event should be triggered on the download button...

Gareth, Kohei's updated PR is now on demo1 so you should be able to test the auto-started event: https://www-demo1.allizom.org/en-US/ (In reply to Gareth Cull [:garethc] from comment #24) > Also, i was wondering about some events....it looks like in chrome, after i > click on the download button on /performance (and others so far), that the > event gets triggered on load of the download.html?product page. I'd like to > be able to have this on click of the /performance btn. This would enable me > to run a site wide report to see where all of our downloads are originating > from. Can you please confirm? The GA tracking logic on the download buttons should be working just like any other piece of tracking on the site. As soon as a button is clicked, the event is tracked. Then when the callback fires the download is processed. If you compare the download button on the home page of demo1 to the tracking already on the home page button on prod, do you see any difference?

I ran a quick test using this Chrome extension for debugging GA events: https://chrome.google.com/webstore/detail/google-analytics-debugger/jnkmfdileelhofjcijamephohjechhna?hl=en This is the data I see from clicking the download button on both demo1 and the current version on prod: www-demo1.allizom.org --------------------- Account ID : UA-36116321-1 Page Title : Home of the Mozilla Project — Mozilla Host Name : www-demo1.allizom.org Page : /en-US/ Referring URL : - Hit ID : 1292005640 Hit Type : event Event Name : Firefox Downloads Event Type : click Event Label : Firefox Visitor ID : 1228822537 Session Count : 5 Session Time - First : Thu Oct 10 2013 07:13:01 GMT 0100 (BST) Session Time - Last : Tue Jan 21 2014 17:40:09 GMT 0000 (GMT) Session Time - Current : Wed Jan 22 2014 09:35:33 GMT 0000 (GMT) Campaign Time : Thu Oct 10 2013 07:13:01 GMT 0100 (BST) Campaign Session : 1 Campaign Count : 1 Campaign Source : (direct) Campaign Medium : (none); Campaign Name : (direct) Language : en-us Encoding : UTF-8 Flash Version : 12.0 r0 Java Enabled : true Screen Resolution : 1440x900 Browser Size : 1299x364 Color Depth : 24-bit Ga.js Version : 5.4.6d Cachebuster : 999389425 mozilla.org ----------- Account ID : UA-36116321-1 Page Title : Home of the Mozilla Project — Mozilla Host Name : www.mozilla.org Page : /en-US/ Referring URL : - Hit ID : 1404539559 Hit Type : event Event Name : Firefox Downloads Event Type : download click Event Label : Firefox Desktop Visitor ID : 1146350297 Session Count : 34 Session Time - First : Thu May 09 2013 14:39:36 GMT 0100 (BST) Session Time - Last : Tue Jan 21 2014 17:10:35 GMT 0000 (GMT) Session Time - Current : Wed Jan 22 2014 09:37:04 GMT 0000 (GMT) Campaign Time : Thu Oct 10 2013 15:45:16 GMT 0100 (BST) Campaign Session : 25 Campaign Count : 5 Campaign Source : facebook Language : en-us Encoding : UTF-8 Flash Version : 12.0 r0 Java Enabled : true Screen Resolution : 1440x900 Browser Size : 1299x320 Color Depth : 24-bit Ga.js Version : 5.4.6d Cachebuster : 375540528

Hi Chris / Gareth, We discussed this PR at our weekly triage meeting and thought we would bring up the progress working toward bug 874913. Seems we are now pretty close to being able to point the download buttons to the second scene of /firefox/new/. In light of this, we think it might be a better option to postpone this PR until after bug 874913 is fixed, in order to minimize the amount of code-shuffle related to the download buttons. Should this PR land first, the code here would likely need to be refactored and retested again. Would just like to get your thoughts on this before we proceed with either route. Thanks

If it saves you time in the long run, I'm fine with waiting. What is the ETA on bug 874913 being fixed? Chris, you ok with this?

(In reply to Gareth Cull [:garethc] from comment #30) > If it saves you time in the long run, I'm fine with waiting. What is the ETA > on bug 874913 being fixed? Chris, you ok with this? Yes, let's wait until the buttons point to the second scene. Thx

Closing this bug as we've refactored all of our download events as part of the last GTM implementation project.