Event Tracking on outbound links to www.mozilla.org from addons.mozilla.org



Web Analytics
4 years ago
4 years ago


(Reporter: garethc, Unassigned)



(Whiteboard: [fxgrowth])



4 years ago
As part of the Firefox growth initiative, we've identified a significant amount of Non-Fx traffic that goes to addons.mozilla.org. I'd like to better understand what that traffic is doing on AMO and would like to know how they are interacting with links that send traffic to mozilla.org.

In particular, can we update the following links?

1) 'Learn More About Firefox' Buttons

See button image on addon page: http://cl.ly/image/3G220F1q3Z1A

Currently these buttons point to getfirefox.com/?src=amo, which is a problem because they then get re-directed and we append the following utm parameters (?utm_source=getfirefox-com&utm_medium=referral) and drop the src parameter. We are currently telling Google Analytics that the referral came from getfirefox.com. Would it be possible to point those button links to the following so we can properly attribute AMO traffic:


Also, if we could place the following event onclick of those buttons: 
_gaq.push(['_trackEvent', 'Learn More About Firefox CTA', 'button click', AddonName]);

where AddonName is the name of the addon (eg. AdBlock Plus).

2) Can we also update the link in the yellow message box 

Message: "To try the thousands of add-ons available here, download Mozilla Firefox, a fast, free way to surf the Web!"

See button image: http://cl.ly/image/3G220F1q3Z1A

Currently this link points to www.mozilla.org/firefox/?src=amo. Unfortunately because of locale redirects we lose the referrer and the majority of the traffic going to this url (70%) is appearing as 'Direct'. Can we please update this href to the following:


Also, add the following event onclick of that link:
_gaq.push(['_trackEvent', 'outbound links', 'link click', href]);

3) Are there any more outbound links to mozilla.org from AMO?




4 years ago
Blocks: 1073115
Whiteboard: [fxgrowth]
You need to log in before you can comment on or make changes to this bug.