620705 - Add Webtrends tracking to main product and site pages

Status: RESOLVED FIXED

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

Description

[Laura Forrest]

Attachment: Technical Documentation

Documentation attached.

Comment 1

[Laura Forrest]

Attachment: Tag Names

Comment 2

[Laura Forrest]

The goal here is to accurately track our promotional site content so that we can easily see what our users are most interested in. This will help us change and optimize content accordingly. 

Please implement the Webtrends "Ad-tracking" functionality. Details attached.

Comment 3

[James Long (:jlongster)]

In the "Tag Names" attachment, are the tag names what is passed to the "WT.ti" parameter?

So the tracking code for each link looks something like:

dcsMultiTrack('DCS.dcsuri', '/path/to/page', 'WT.ti', 'tag name');

Comment 4

[Laura Forrest]

Correct. 

Adding Wes from Webtrends to this to verify.

Comment 5

[James Long (:jlongster)]

On the page with the spinner wheel
(http://www.mozilla.com/en-US/firefox/fx/), the attachment says that the 3
sections on the wheel (mobile, personas, addons) are each supposed to be tagged
with tracking code.  Is it supposed to track when the user clicks the wheel to
spin?  All that happens when the user clicks any part of the wheel is it spins.

Comment 6

[John Slater]

(In reply to comment #5)
> On the page with the spinner wheel
> (http://www.mozilla.com/en-US/firefox/fx/), the attachment says that the 3
> sections on the wheel (mobile, personas, addons) are each supposed to be tagged
> with tracking code.  Is it supposed to track when the user clicks the wheel to
> spin?  All that happens when the user clicks any part of the wheel is it spins.

How about tagging clicks on the links that appear after you click the wheel...I think that's the most relevant thing to track here.

Thanks!

Comment 7

[James Long (:jlongster)]

That sounds good.  Can someone list the exact tag names those links should be?(In reply to comment #6)
> (In reply to comment #5)
> > On the page with the spinner wheel
> > (http://www.mozilla.com/en-US/firefox/fx/),...
>
> How about tagging clicks on the links that appear after you click the wheel...I
> think that's the most relevant thing to track here.
> 
> Thanks!

Sounds good.  Can someone list the exact tag names those links should have?

Comment 8

[Laura Forrest]

I agree with John. 

For the exact names please use:

Mobile Wheel
Personas Wheel
Addons Wheel

Comment 9

[Laura Forrest]

(In reply to comment #8)
> I agree with John. 
> 
> For the exact names please use:
> 
> Mobile Wheel
> Personas Wheel
> Addons Wheel

I'm also curious to see what the clickthrough is like on the wheel itself since we've never done something like this before. Lets track clicks to the wheel to make it spin, and call it "Wheel Spin". 

Thanks!

Comment 10

[James Long (:jlongster)]

Thanks Laura.  The only problem with tracking the wheel spin is that it's not really a "click-through" since it doesn't take you to a new page.

Can anyone who's more familiar with the Webtrends service comment on tracking non-click-through events?  I've never even seen the Webtrends interface, and if it's heavily based on URLs, I'm not sure how to track the wheel spin.

More technically, what happens if I call dcsMultiTrack without the URI parameter?

Comment 11

[Laura Forrest]

(In reply to comment #10)

I think that should be fine James but lets wait to double check with Wes, Cc-ed here. He's a Webtrends technical pro.

Comment 12

[James Long (:jlongster)]

With regards to adding the tags in the footer, the footer is already abstracted out as an include file across all the pages, so adding the tracking codes there once will affect all pages and shouldn't slow the site down at all.  (The attachment "tag names" poses a question of affecting site performance)

Comment 13

[James Long (:jlongster)]

In the panel that shows up for "personas" on the wheel, this page is loaded in an iframe:

http://www.getpersonas.com/en-US/external/mozilla/firstrun.php

It shows some sample personas.  If you want clicks to these to be tracked, I think a new bug should be filed because it's a separate site and I think other pages load this page too.

Comment 14

[John Slater]

(In reply to comment #13)
> It shows some sample personas.  If you want clicks to these to be tracked, I
> think a new bug should be filed because it's a separate site and I think other
> pages load this page too.

Laura, what do you think?

Comment 15

[Laura Forrest]

Tracking the Persona previews within the wheel not necessary, but clicks to the "many more this way" link should be.

Comment 16

[Wes Contreras]

Based on what I know so far, I'd recommend not tagging clicks on the 'click to spin' button, but we probably do want to track clicks on the calls to action that come up after you spin the wheel. Since these all lead to different sites, that would best be done with an onclick event for those clickthroughs.

Comment 17

[Laura Forrest]

(In reply to comment #16)
> Based on what I know so far, I'd recommend not tagging clicks on the 'click to
> spin' button

This is fine.

Comment 18

[Laura Forrest]

Hey James, how is this coming along? Let us know when you're done and Wes can take a look in the spirit of QA before we push. Thanks!

Comment 19

[James Long (:jlongster)]

This will be finished in the next couple hours.

Comment 20

[James Long (:jlongster)]

Attachment: patch for integrating all the tags

Comment 21

[James Long (:jlongster)]

The new attachment should integrate all the tags.

One thing to note in the tagging of the Firefox download button.  This buttons appears on a few pages bu each page copies the code for the button.  My current changes just tags the button on the page with the wheel spinner, do you want it to be tracked on every page it appears?

Comment 22

[Wes Contreras]

Reviewing the code on this patch, while I can't test it directly, the code looks good to me.

Comment 23

[Laura Forrest]

Thanks Wes!

James - feel free to push this live, or push to the next step.

Comment 24

[Wes Contreras]

Slight adjustment - after reviewing the plan for digesting the data, there are some adjustments that we'll want to make. More info to come, hopefully by end of day today.

Comment 25

[James Long (:jlongster)]

I have already pushed these changes to staging, but they are not live yet.  Can we apply your tweaks as adjustments and is it ok if the current implementation goes live (If someone requests for staging to go live, it will go)?

Comment 26

[Laura Forrest]

Wes - Thanks for catching this. We'll want to make sure this is implemented correctly. 

These changes should be able to easily be applied as adjustments to staging.

Wes please provide more directions when you have it.

Comment 27

[Laura Forrest]

Seems like getting these technical details for next steps from Wes at Webtrends may take longer than we expected. This may be at risk for making 1.0, but won't be the end of the world if we push it to 1.1. 

Lets see what happens today.

Comment 28

[James Long (:jlongster)]

Still want to make it clear - the current patch is staged to go live in the next push (next tuesday).  If these adjustments don't make it in before the freeze, is everyone ok pushing out the current changes, and making the adjustments in the next push?

Comment 29

[Laura Forrest]

Hi James, 

Thanks for clarifying. Yes, pushing out the current changes then making adjustments later is fine. Thanks!

Comment 30

[James Long (:jlongster)]

I realized I never added the push information.

r80234 | [e-mail] | 2011-01-05 18:02:02 -0500 (Wed, 05 Jan 2011) | 2 lines

Comment 31

[James Long (:jlongster)]

Wes, I'm marking this bug as resolved since the current changes are going out on Tuesday.  If you come up with adjustments to the code, you can file a new bug.  Thanks!