558105 - SUMO: Add WebTrends Tags

Status: VERIFIED FIXED

(support.mozilla.org :: Knowledge Base Software, task, P2)

Description

[Paul Craciunoiu [:paulc]]

Spin off of bug 556384. Looking at the docs posted by Blake in that bug, we would need to:

1) Remove old Omniture tracking code
2) Add the inline JS from webtrends.html to the bottom of our pages
3) Modify webtrends.js and set (from the .docx):
    this.dcsid="dcskot6d000000w0qxqho15rf_7r6o";
    this.rate="50";
    this.fpcdom="mozilla.com";
4) Load webtrends.js on all SUMO pages.

Blake, does this look good? Any other tracking params to set?

According to bug 556384, this would be nice to have in a week or so. Tentatively targeting for 1.5.4.

Comment 1

[Blake Cutler]

Looks great.  I'll need to talk with Cheng before we push the change live.

Comment 2

[Paul Craciunoiu [:paulc]]

Good! I wasn't clear in comment 0 so I'll ask -- which pages do we want to track? Wiki pages, forum threads, search pages?

Comment 3

[Blake Cutler]

We'll track everything (unless you can think of a reason we shouldn't).

Comment 4

[Blake Cutler]

Cheng requested that we keep both the Omniture and WebTrends tags for 1-2 weeks.  This will slight increase page load time, but I think it makes sense for our transition. 

Can I get an ETA?  Thanks!

Comment 5

[Paul Craciunoiu [:paulc]]

I could file a patch adding WebTrends on Monday. When it will be live depends mostly on IT. What do you think, James? Maybe Thursday?

Comment 6

[James Socol [:jsocol, :james]]

1.5.4 is planned for the week of the 19th right now. I don't see anything here that would force us to push early.

Comment 7

[Blake Cutler]

sound good. thanks.

Comment 8

[[:Cww]]

We'll need to keep Omniture up and running for at least 3 weeks while we make the change so that we can compare metrics and we don't lose stuff while we're adapting.  So if there's a hard stop on the Omniture stuff, we may want to pull this forward, otherwise, whenever.

Also retitling the bug to focus on adding web trends, we'll take off the omniture stuff after we're done migrating.

Comment 9

[Paul Craciunoiu [:paulc]]

Attachment: add webtrends, v1

This adds the webtrends inline code to our footer and the external JS. I preferred using Wenzel's version to pass in options to the WebTrends constructor.

Comment 10

[James Socol [:jsocol, :james]]

Been following a conversation outside Bugzilla, and it looks like we might have some new, better JS to embed soon.

Comment 11

[Paul Craciunoiu [:paulc]]

Attachment: no document.writes, follows AMO's example

This follows AMO's example from attachment 441820 [details] [diff] [review] and uses a similar webtrends.js (with the updated dcsid & co).

Comment 12

[James Socol [:jsocol, :james]]

Looks like this patch contains two copies of the JS. Did you not rm the file and then reapply the patch at some point?

Comment 13

[Paul Craciunoiu [:paulc]]

Attachment: fixed double-patched webtrends.js

Yes. That's because I ignorantly applied the patch over at some point.

Comment 14

[Paul Craciunoiu [:paulc]]

r? for Kitsune at http://github.com/pcraciunoiu/kitsune/commit/ca0d63460477d729b2de3252f2295a2a4abbd831
Uses the webtrends.js from Tiki.

Comment 15

[James Socol [:jsocol, :james]]

Comment on attachment 441939 [details] [diff] [review]
fixed double-patched webtrends.js

Looks good to me.

Comment 16

[Paul Craciunoiu [:paulc]]

r66525 on trunk
minify.conf.php is not updated automatically, so I filed bug 562192.

Kitsune:
http://github.com/jsocol/kitsune/commit/d9cf12081bd5f3873facec9503a75547b03dfae2

QA: please hold off on verifying until bug 562192 is fixed.

Comment 17

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified FIXED:

<script defer src="/js/webtrends.js"></script>
<noscript>
    <img id="DCSIMG" width="1" height="1" src="http://statse.webtrendslive.com/dcskot6d000000w0qxqho15rf_7r6o/njs.gif?dcsuri=/nojavascript&amp;WT.js=No&amp;WT.tv=8.6.2"/>
</noscript>