652572 - [WT] Track newsletter subscription conversion funnel

Status: VERIFIED FIXED

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

Description

[Laura Forrest]

We'd like to know, and track on a continuing basis, how our newsletter signup flow is converting. 

Current Paths:  
1. Signup from within site footer (bug 630638)
2. Signup from main newsletter landing page http://www.mozilla.com/en-US/newsletter/
3. Signup from localized newsletter landing pages (example: http://www.mozilla.com/de/newsletter/)
4. Signup from other pages signup form is on (example: http://www.mozilla.com/en-US/firefox/4.0/whatsnew/)

I see a simple report such as this working well:
Page Name | Visits | Start Signup Flow | Finish Signup | Conversion %

Depending on how this reporting will work, it may or may not be dependent on the tagging done in bug 646992. 

Brad: Please advise on next steps here.

Comment 1

[Bradley Gross]

This report will be dependent upon the completion of bug 646992.  Once your pages are correctly tagged the report shouldn't take long to create.

Comment 2

[Laura Forrest]

(In reply to comment #1)
> This report will be dependent upon the completion of bug 646992.  Once your
> pages are correctly tagged the report shouldn't take long to create.

Hey Brad - the code to enable this report was deployed yesterday, or will be today. Feel free to go ahead and create this new report within Webtrends based on the tagging done in Bug 646992. Thanks!

Comment 3

[Laura Forrest]

Let's limit the scope of this bug to tracking the signup fall-off on the /newsletter page only. 

http://www.mozilla.com/en-US/newsletter/

We want to see the fall-off from the following flow:

Visits | Email Address | Country | Format | PPolicy| Sign Me Up | Conversion Rate

Comment 4

[Bradley Gross]

Tracking each form field of the news-letter sign-up process may be a bit overkill.  I would limit the newsletter sign-up scenario to two steps, the visit and the ‘Sign me up’ action.  The additional tagging of the specified form fields is probably not going to provide much useful information.  Chances are, that if the user completes the visit step but does not sign-up, it's probably due to a disagreement with the privacy policy.  

If we find that there is significant fall-off after the visit step, we can go ahead and add those additional tags to get more detailed information.



The following is the tagging structure for the two step process mentioned above:

Step 1: Visit (add these META tag to the page header)
<meta name="WT.si_n" content="newsletter">
<meta name="WT.si_x" content="1">

Step 2:  Sign me up! (button click event)
onclick=”dcsMultiTrack(
‘DCS.dcssip’,’www.mozilla.com’,
‘DCS.dcsuri’,’/en-US/newsletter’,
‘WT.ti’,’Link: newsletter’, 
‘WT.dl’,99,
‘WT.z_convert’,‘newsletter’, 
‘WT.si_n’,’newsletter’
‘WT.si_x’,’2’);”

Also note that there is no logic preventing the hit being sent to our servers if the form fails validation; however, as long as they show intent to sign-up (by clicking the sign me up button) that’s probably enough.

*In any event if you want to tag the additional fields, let me know and I will provide the necessary dcsMultiTrack calls.*

Comment 5

[Laura Forrest]

Brad: I believe step 2 has been implemented here https://bugzilla.mozilla.org/show_bug.cgi?id=646992#c21 Can you please check and confirm? 

If what is needed was implemented, then just "Step 1" from above should be deployed by WebDev. 

It's fine to track just two steps.

Comment 6

[Bradley Gross]

I took the following code snippet from www.mozilla.com/en-US/newsletter, it is the html for the "Sign me up!" button, it still needs the WT.si_n and WT.si_x parameters specified above:

<input onclick="dcsMultiTrack(
'DCS.dcssip', 'www.mozilla.com',
'DCS.dcsuri', '/en-us/newsletter',
'WT.ti', 'Link: Mozilla Newsletter',
'WT.dl', 99,
'WT.z_convert', 'newsletter');"
                 name="submit" 
                 type="submit" 
                 value="Sign me up!" 
                 class="subscribe">

In addition, the 'inline' newsletter signup widget is not currently tagged either.

Comment 7

[Laura Forrest]

(In reply to comment #6)
> I took the following code snippet from www.mozilla.com/en-US/newsletter, it
> is the html for the "Sign me up!" button, it still needs the WT.si_n and
> WT.si_x parameters specified above:
> 
> <input onclick="dcsMultiTrack(
> 'DCS.dcssip', 'www.mozilla.com',
> 'DCS.dcsuri', '/en-us/newsletter',
> 'WT.ti', 'Link: Mozilla Newsletter',
> 'WT.dl', 99,
> 'WT.z_convert', 'newsletter');"
>                  name="submit" 
>                  type="submit" 
>                  value="Sign me up!" 
>                  class="subscribe">

Great - James - can you please implement the above?

> In addition, the 'inline' newsletter signup widget is not currently tagged
> either.
That's fine for now, thanks for mentioning.

Comment 8

[Laura Forrest]

James - any chance this can get into the 2.8 release?

Comment 9

[James Long (:jlongster)]

Yes, I will do this and a few other small bugs in the morning (my time) so they'll be ready to go by end of day. Spent time on a few bigger bugs today.

Comment 10

[James Long (:jlongster)]

done in r90507

Comment 11

[Bradley Gross]

The following updates have not yet been implemented on http://www.mozilla.com/en-US/newsletter/:

Step 1: Visit (add these META tag to the page header)
<meta name="WT.si_n" content="newsletter">
<meta name="WT.si_x" content="1">

Step 2:  Sign me up! (button click event)
onclick=”dcsMultiTrack(
‘DCS.dcssip’,’www.mozilla.com’,
‘DCS.dcsuri’,’/en-US/newsletter’,
‘WT.ti’,’Link: newsletter’, 
‘WT.dl’,99,
‘WT.z_convert’,‘newsletter’, 
‘WT.si_n’,’newsletter’
‘WT.si_x’,’2’);”

Comment 12

[James Long (:jlongster)]

I was waiting for QA, but as this is such a simple change I'll go ahead and roll it out.

pushed to production r90636

Comment 13

[raymond [:retornam] (inactive)]

verified fixed http://www.mozilla.com/en-US/newsletter/

Comment 14

[Bradley Gross]

The Newsletter Signup scenario analysis report has begun populating with data.  Please have a look and let me know what you think.

Comment 15

[Laura Forrest]

The "Link Tracking" report is exactly what I've always dreamed of. Fantastic. Thanks Brad and David.