Task #2988
Story #2987: Track CI use during release process
Add analytics tracking script to ONEMercury
100%
Description
The tracker id is "UA-15017327-9" and can be enabled by adding the following script:
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-15017327-9']);
_gaq.push(['_setDomainName', 'dataone.org']);
_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);
})();
Need to verify that the script does not interfere with normal operation of the pages.
History
#1 Updated by Skye Roseboom over 12 years ago
UA-15017327-9 is the tracker ID for production use. Not for use in dev, stage, sandbox.
So will need to configure the tracking ID by hostname/domain.
#2 Updated by Dave Vieglais over 12 years ago
For non-production environments, the tracking ID is "UA-15017327-12"
#3 Updated by Skye Roseboom over 12 years ago
- Status changed from New to In Progress
#5 Updated by Skye Roseboom over 12 years ago
Added ga snippet to the following one-mercury ui:
index.jsp (search UI)
brief.jsp (search results UI)
full.jsp (metadata detail view)
myview.jsp (error page)
Committed to trunk. Need to push to 1.0 branch for release in 1.0.2 patch release.
#6 Updated by Skye Roseboom over 12 years ago
Copied to 1.0.0 branch for 1.0.2 patch release.
#7 Updated by Skye Roseboom over 12 years ago
- Status changed from In Progress to Closed
tested with 1.0.2 patch release on sandbox.