494296 - Update Urchin tracking code on www.mozilla.org

Status: RESOLVED FIXED

(www.mozilla.org :: General, defect, P2)

Description

[David Boswell]

Can we confirm if we need to upgrade our Urchin tracking code being used on www.mozilla.org?  The instructions listed in bug 483804, comment #2 for setting up Urchin on another site don't match our configuration.  

One difference is the js file.  We're using __utm.js and it's a file from 2004.  The urchin.js file mentioned in the other bug is from 2007.  

http://mxr.mozilla.org/mozilla-org/source/html/__utm.js

I haven't done a diff, so a don't know how similar these files are but it is possible that we need to switch to the more recent files to take advantage of new features in the version of Urchin we're using.

The other difference I noticed is the script that is included in the <head> tag.  We're using the following on our pages now:

 <script src="/__utm.js" type="text/javascript"></script>

Maybe this doesn't matter, so please confirm if we should update or not.

Comment 1

[Deepa]

As tracked by an add on utility that helps web analytics professionals, It seems that the current urchin code is not tracking all info. 
https://secure.urchin.com/helpwiki/en/Urchin_Installation_Guide_(Windows) maybe an useful guide to making sure code is up-to-date. 
An example of an Urchin6 site that is tracking visitor level session correctly is 
crash-stats.mozilla.com and similar mozilla.com site pages

Comment 2

[David Boswell]

Just to follow up with some more information Deepa found:

The old __utm.js tracking javascript has been replaced with a GoogleAnalytics-compatible urchin.js tracking javascript (existing sites will need to upgrade)

http://groups.google.com/group/urchin-help/web/urchin-software-from-google---official-faq

Considering this I've updated the summary for the bug.  Next steps are to create a patch for the change and then have someone review it.

Comment 3

[Reed Loden [:reed]]

Removing html/__utm.js;
/www/mozilla-org/html/__utm.js,v  <--  __utm.js
new revision: delete; previous revision: 1.1
done
RCS file: /www/mozilla-org/html/urchin.js,v
done
Checking in html/urchin.js;
/www/mozilla-org/html/urchin.js,v  <--  urchin.js
initial revision: 1.1
done
Checking in tools/wrap.pl;
/www/mozilla-org/tools/wrap.pl,v  <--  wrap.pl
new revision: 1.63; previous revision: 1.62
done

Comment 4

[David Boswell]

Thanks Reed.  I'm reopening though since there's also code on the home page.  I believe that's the only page that wrap.pl doesn't cover (except for the handful of pages that don't have any wrapping at all -- I think we can ignore these for now since most, if not all, of those are going to get archived or migrated).

Comment 5

[David Boswell]

I just checked the home page and it looks like Reed has updated the Urchin code there.  Closing as fixed.

Deepa, can you verify that things are now working correctly with our Urchin reports now?

Comment 6

[Deepa]

It does take around 2 days for data to get analyzed and show up in the Urchin system. I will keep an eye on it...It hasnt shown up yet..I am guessing its just early..

Comment 7

[Deepa]

Does not show the data in the urchin system yet. would like to reopen the bug

Comment 8

[David Boswell]

Raising priority.

Comment 9

[Reed Loden [:reed]]

Going to go ahead and re-close this. If you can find issues still, feel free to reopen, and I'll take another look.