Closed Bug 808937 Opened 13 years ago Closed 13 years ago

Please provide Google Analytics code for: mozillaignite.org

Categories

(Websites :: Web Analytics, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: davida, Assigned: cmore)

Details

Full website address: mozillaignite.org Explain the goal and use-case of having web analytics on this website. - tracking traffic to and from the site, evolution over time, etc. Do you have requirements to track user interactions on your website? For example, how many people have clicked a button on a page, filled out a form, or went through a pre-defined funnel? no Define the people who should have access to the reports. - MoFo engagement & webdev ryan@mozillafoundation.org rebeccah@mozillafoundation.org ross@mozillafoundation.org (note: we just need the snippet/code, MoFo devs will implement).
Created profile and waiting for Google to enable for premium.
Assignee: nobody → chrismore.bugzilla
Status: NEW → ASSIGNED
Here are the instructions for implementing Google Analytics on our website. For more information, see http://code.google.com/apis/analytics/docs/tracking/asyncTracking.html Copy the following code, then paste it onto every page you want to track immediately before the closing </head>tag. <script type="text/javascript"> var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-35433268-3']); _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>
Google Analytics enabled for premium on 11/9/2012
Has this been added to the website yet?
Not yet no - it's caught up waiting to be pushed to staging along with https://bugzilla.mozilla.org/show_bug.cgi?id=813192
Now live!
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.