Closed
Bug 698329
Opened 13 years ago
Closed 13 years ago
add bugzilla.mozilla.org to webtrends
Categories
(Websites :: Web Analytics, task)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: glob, Assigned: brad.gross)
References
Details
we'll like to use webtrends to monitor bugzilla.mozilla.org. would it be possible to get bmo added to webtrends?
Assignee | ||
Comment 1•13 years ago
|
||
Laura - Will bmo be tracked under its own profile?
Assignee | ||
Comment 2•13 years ago
|
||
Please include the following javascript just above the closing body tags for pages that you wish to track (this tag is configured to sample at 100% and has automatic link tracking turned off): <script type="text/javascript" src="http://mozcom-cdn.mozilla.net/includes/min/min.js?g=js_stats"></script> <script type="text/javascript"> //<![CDATA[ var _tag=new WebTrends({"dcsid":"dcsqjgr30wz5bd6zokoukhwj3_7z7z","rate":100,"fpcdom":"mozilla.org"}); _tag.dcsGetId(); //]]> </script> <script> //<![CDATA[ _tag.dcsCollect(); //]]> </script> <noscript> <div><img alt="DCSIMG" id="DCSIMG" width="1" height="1" src="//statse.webtrendslive.com/dcsqjgr30wz5bd6zokoukhwj3_7z7z/njs.gif?dcsuri=/nojavascript&WT.js=No&WT.tv=8.6.2"/></div> </noscript>
Assignee | ||
Comment 3•13 years ago
|
||
I created a profile entitled buzilla.mozilla.org. Please let me know when your pages are tagged and I will enable analysis on the profile.
Comment 4•13 years ago
|
||
It has been committed and will be in the next code update. This normally happens on Thursdays each week and as I don't feel this is critical, we can just wait til then to let you turn this on. Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.0 added extensions/BMO/template/en/default/hook/global/footer-end.html.tmpl Committed revision 7930. dkl
(In reply to David Lawrence [:dkl] from comment #4) > It has been committed and will be in the next code update. this code triggers mixed content warnings as the mozcom-cdn script is served via http not https. switching to https causes the script to fail to load due to a certificate error. i've backed this out - will track this in bug 689086.
Assignee | ||
Comment 6•13 years ago
|
||
You should be able to reference the following script as well (although they point to different files, the content of each should be the same): <script src="/js/webtrends.js" type="text/javascript"></script>
Assignee | ||
Comment 7•13 years ago
|
||
here is the full path: http://www.mozilla.org/js/webtrends.js
thanks brandley. we've gone with maintaining our own copy of webtrends.js on the bmo servers. you should start getting data on in about 12 hours time.
Assignee | ||
Comment 9•13 years ago
|
||
Please verify that it is the same JavaScript that is located here (hosting it 'locally' is fine): http://www.mozilla.org/js/webtrends.js We're trying to maintain tagging continuity across domains (given that the webtrends.js being used by the majority of .org sites is customized)
Assignee | ||
Comment 10•13 years ago
|
||
err sub-domains.
Assignee | ||
Comment 11•13 years ago
|
||
err sub-domains.
Reporter | ||
Comment 12•13 years ago
|
||
(In reply to Bradley Gross from comment #9) > Please verify that it is the same JavaScript that is located here (hosting > it 'locally' is fine): > http://www.mozilla.org/js/webtrends.js i'm using the javascript from the you originally provided (http://mozcom-cdn.mozilla.net/includes/min/min.js?g=js_stats). the mozcom-cdn version is the same as mozilla.org/js/webtrends.js, but has all comments and unnecessary whitespace removed. hrm, http://www.mozilla.org/js/webtrends.js is being served with the wrong content-type, i wonder if that will cause any problems.
Assignee | ||
Comment 13•13 years ago
|
||
(In reply to Byron Jones ‹:glob› from comment #12) > (In reply to Bradley Gross from comment #9) > > Please verify that it is the same JavaScript that is located here (hosting > > it 'locally' is fine): > > http://www.mozilla.org/js/webtrends.js > > i'm using the javascript from the you originally provided > (http://mozcom-cdn.mozilla.net/includes/min/min.js?g=js_stats). This should be fine. > > the mozcom-cdn version is the same as mozilla.org/js/webtrends.js, but has > all comments and unnecessary whitespace removed. > > > hrm, http://www.mozilla.org/js/webtrends.js is being served with the wrong > content-type, i wonder if that will cause any problems.
Assignee | ||
Comment 14•13 years ago
|
||
I took a look at https://bugzilla.mozilla.org/ and noticed that it wasn't tagged with Webtrends yet. When is this expected to go live? Is there a staging site I can access for testing?
Comment 15•13 years ago
|
||
We normally push code on Thursdays unless it is a security or other critical fix. We can try to get this out before the US holiday tomorrow. dkl
Reporter | ||
Comment 16•13 years ago
|
||
sorry about the delays bradley; the webtrends code is now live on bugzilla.mozilla.org.
Assignee | ||
Comment 17•13 years ago
|
||
Verified. You should see the bugzilla.mozilla.org profile begin to populate in a few hours.
Reporter | ||
Comment 18•13 years ago
|
||
the bugzilla.mozilla.org profile appears to be attached to the demos.mozilla.org site on webtrends. is this correct? (the two sites are not related).
Reporter | ||
Comment 19•13 years ago
|
||
i haven't seen any data in the profile yet: "There is no data for this profile"
Reporter | ||
Comment 20•13 years ago
|
||
profile data has started populating now :)
Assignee | ||
Comment 21•13 years ago
|
||
I'm going to close this bug for now. Possible next steps would include onsite-search tracking and such.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Updated•11 years ago
|
Component: Webtrends → Web Analytics
You need to log in
before you can comment on or make changes to this bug.
Description
•