When people click on the download button that we provide, we should not count that as a bounce. Tracking those as an event will give us insights into clicks that are currentl counted as bounces.
(In reply to Kadir Topal [:atopal] from comment #0) > When people click on the download button that we provide, we should not > count that as a bounce. Tracking those as an event will give us insights > into clicks that are currentl counted as bounces. We looked at this data last week by looking at the mozilla.org profile. I think we decided it was insignificant? If we want to still track this anyway, I think we should open the download link in a new tab as well. Otherwise, the event will be unreliable as the page will get unloaded as soon as they click.
Sorry, this is for sprint 6. It's not huge, but 400k is still big enough to taint the bounce rate numbers in GA. re: opening a new link: as a test that was okay, not so sure as a permanent solution. I guess we have three options: 1. leave it as it is, and live with kinda untrue numbers in GA 2. add event tracking, knowing it's not completely reliable 3. add event traking and open link in new tab to make sure it's reliable. Ricky, the numbers would be unreliable since people might click the link before the GA code is loaded, right?
400k is referring to monthly visits and changing the sprint for real this time.
Can we add a small delay? http://stackoverflow.com/questions/4064783/google-analytics-track-outbound-clicks-how The other option, is as you say...open it in new tab. Ibai
And this article directly from Google: http://support.google.com/analytics/bin/answer.py?hl=en&answer=1136920 As mentioned in the opening but, Google always recommends this to be tracked as an Event...not as a pageview as the SO thread.
We are just adding a new event to track (we've done a few already, they are easy), possibly using some fancy trick from Comment 5 or Comment 6. => 1pt
Deployed to prod now.