[WT] Track offsite campaign link to newsletter subscriptions

VERIFIED FIXED in 2.6

Status

www.mozilla.org
General
VERIFIED FIXED
7 years ago
6 years ago

People

(Reporter: Laura Forrest, Assigned: jlongster)

Tracking

unspecified
x86
Windows XP
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

117.17 KB, application/octet-stream
Details
(Reporter)

Description

7 years ago
This tracking code was implemented on  but conversions aren't showing up in the respective Webtrends reports. 

Code implemented on button submission:
<META NAME="WT.si_n" CONTENT="Main Newsletter Subscribe">
<META NAME="WT.si_x" CONTENT="1">
<META NAME="WT.si_cs" CONTENT="1"> 

Goal: track successful email signups from this page. Note: we'll also want to apply this same tracking to the inline signup forms like on this page: http://www.mozilla.com/en-US/firefox/3.6.11/whatsnew/

Comment 1

7 years ago
I clicked the 'sign me up!' button but the hit didn't contain the specified parameters.  I searched the page source for the parameters as well and couldn't find them either.  

An alternative approach would be to implement automatic link tracking and create a custom report for all clicks that result in an email sign-up.

I took a look at the core Webtrends JavaScript you are using and it doesn't look like it's currently set up to use link tracking.  

Is this something you are interested in exploring?
(Reporter)

Comment 2

7 years ago
(In reply to comment #1)
> I clicked the 'sign me up!' button but the hit didn't contain the specified
> parameters.  I searched the page source for the parameters as well and couldn't
> find them either.
Interesting...thanks for checking.   
> 
> An alternative approach would be to implement automatic link tracking and
> create a custom report for all clicks that result in an email sign-up.
I like the sounds of "automatic." To back up a bit, we're basically looking to track two things: 
1. which marketing campaigns result in the highest Newsletter signup conversion. We're doing this now for Download Conversion in the "Campaign Conversion" report (check that out as a reference)

2. Get a better sense of how the newsletter signup page is working. For instance, how many people that come to that page end up signing up? Since there's no confirmation page it's hard to tell now. 

Winston - does this sound right?
> 
> I took a look at the core Webtrends JavaScript you are using and it doesn't
> look like it's currently set up to use link tracking.  
> 
> Is this something you are interested in exploring?

Yes - I'm very interested in exploring any technical solution that will enable us to measure the two facets I stated above. 

Note: whatever we come up with here would be great to apply to other conversion events too :)

Thanks!
Assignee: lforrest → brad.gross

Comment 3

7 years ago
Thanks Laura!  yes - your description of our goals is dead on.
(Reporter)

Comment 4

7 years ago
Brad - any updates here?

Comment 5

7 years ago
Let's chat a bit more about this tomorrow. I will present a few options and then we can solidify a strategy for tracking events in general.

(In reply to comment #4)
> Brad - any updates here?
(Reporter)

Comment 6

7 years ago
Let's do DCS multi-track. Does this code look okay? Where should it be placed?

<META NAME="WT.si_n" CONTENT="Main Newsletter Subscribe">
<META NAME="WT.si_x" CONTENT="1">
<META NAME="WT.si_cs" CONTENT="1">
(Reporter)

Comment 7

7 years ago
Note: we want to limit the scope of this bug to just tagging the /newsletter page and being able to attribute that signup with a marketing campaign.
(Reporter)

Comment 8

7 years ago
Brad - Given my last comment above, and our discussion yesterday, can you please update this bug with the exact code that should be added to http://www.mozilla.com/en-US/newsletter/?
Target Milestone: 2.1 → 2.2

Comment 9

7 years ago
I'm currently testing how we would add that to a form button.  It is slightly different on the "download now" button because that's actually an anchor tag while the 'sign me up!' button is a form submit button.
Target Milestone: 2.2 → 2.1
(Reporter)

Updated

7 years ago
Target Milestone: 2.1 → 2.2
(Reporter)

Comment 10

7 years ago
(In reply to comment #9)
> I'm currently testing how we would add that to a form button.  It is slightly
> different on the "download now" button because that's actually an anchor tag
> while the 'sign me up!' button is a form submit button.

Great - thanks for letting me know. In terms of timing, it would be good to get the final tracking code to our engineers by Wed of this week (4/20) so it can make it into our next release in time.
(Reporter)

Comment 11

7 years ago
(In reply to comment #10)
> (In reply to comment #9)
> > I'm currently testing how we would add that to a form button.  It is slightly
> > different on the "download now" button because that's actually an anchor tag
> > while the 'sign me up!' button is a form submit button.
> 
> Great - thanks for letting me know. In terms of timing, it would be good to get
> the final tracking code to our engineers by Wed of this week (4/20) so it can
> make it into our next release in time.

Hey Brad - Any updates here?

Comment 12

7 years ago
I have added the following code to the 'Sign me up!' form button on the newsletter page (I included the <div> tags for reference):

 <div class="field" id="submit-field">
          <input onclick="dcsMultiTrack('DCS.dcssip', 'www.mozilla.com', 'DCS.dcsuri', '/en-US/newsletter/', 'WT.ti', 'Link: Mozilla Newsletter', 'WT.dl', 99, 'WT.nv', 'Content', 'WT.ac', 'Newsletter', 'WT.si_x', 2);" name="submit" type="submit" value="Sign me up!" id="subscribe">
        </div>

I have tested it on my end and it functions correctly.

Please let me know how it works for you.
(Reporter)

Comment 13

7 years ago
Fantastic! I'll pass this to our devs now to implement. Two quick questions first - I apologize in advanced if you've already answered them but know this can get pretty complex fast: 

1. Can we also apply this same tracking code in Comment 12 to the intra-page newsletter signup flows, for example, when people signup within our site footer? 

2. Will implementing the above allow us to track the sign-up action as if it were a page itself? For example, that would allow us to see through a path analysis how many people landed on mozilla.com/firefox/new and then successfully signed up for the newsletter from that page, which would be great.
(Reporter)

Updated

7 years ago
Blocks: 651587
(Reporter)

Comment 14

7 years ago
(In reply to comment #13)
> Fantastic! I'll pass this to our devs now to implement. Two quick questions
> first - I apologize in advanced if you've already answered them but know this
> can get pretty complex fast: 
> 
> 1. Can we also apply this same tracking code in Comment 12 to the intra-page
> newsletter signup flows, for example, when people signup within our site
> footer? 
Brad - any updates on this? Would be good to have dev only touch these buttons once instead of twice. 
 
> 2. Will implementing the above allow us to track the sign-up action as if it
> were a page itself? For example, that would allow us to see through a path
> analysis how many people landed on mozilla.com/firefox/new and then
> successfully signed up for the newsletter from that page, which would be great.

To simplify this bug, I'm going to file a separate bug around question #2.
(Reporter)

Comment 15

7 years ago
(In reply to comment #14)
> (In reply to comment #13)

> 
> To simplify this bug, I'm going to file a separate bug around question #2.

Done in bug 652572
(Reporter)

Updated

7 years ago
Target Milestone: 2.2 → 2.3
(Reporter)

Comment 16

7 years ago
Brad - any updated on Comment 14? Don't know how to deploy until then.
(Reporter)

Updated

7 years ago
Summary: [WT] Track newsletter subscriptions → [WT] Track offsite campaign link to newsletter subscriptions

Comment 17

7 years ago
Several bugs are dependent upon the completion and implementation of a new tagging strategy that is currently in the works.  I hope to have this complete prior to Wednesday of next week.
(Reporter)

Updated

7 years ago
Target Milestone: 2.3 → 2.4

Comment 18

7 years ago
Created attachment 531630 [details]
Event Tracking Documentation
(Reporter)

Updated

7 years ago
Target Milestone: 2.4 → 2.5
(Reporter)

Updated

7 years ago
Target Milestone: 2.5 → 2.6
(Reporter)

Comment 19

7 years ago
Hi James - Please implement the following on all the newsletter signup click events on Mozilla.com: 

Include this dcsMultiTrack call on the ‘Sign me up!’ button onclick event throughout the site. For mainstream newsletter only. 

onclick=”dcsMultiTrack(
‘DCS.dcssip’,’www.mozilla.com’,
‘DCS.dcsuri’,’/en-us/newsletter’,
‘WT.ti’,’Link: Mozilla Newsletter’, 
‘WT.dl’,1,
‘WT.z_convert’,‘newsletter_signup’
);”

Let Brad or I know if you have any questions.
Assignee: brad.gross → jlong
(Reporter)

Updated

7 years ago
Blocks: 652572

Comment 20

7 years ago
I took a look, it’s basically correct except I would set WT.dl to 99 and the WT.z_convert value to just ‘newsletter’.  Basically WT.z_convert parameter should match the WT.z_ad_name value for the given ad.
(Reporter)

Comment 21

7 years ago
Sounds good. In that case, James use this:

onclick=”dcsMultiTrack(
‘DCS.dcssip’,’www.mozilla.com’,
‘DCS.dcsuri’,’/en-us/newsletter’,
‘WT.ti’,’Link: Mozilla Newsletter’, 
‘WT.dl’,99,
‘WT.z_convert’,‘newsletter’
);”
(Assignee)

Comment 22

7 years ago
Do you realize that people can press the button, but if there are errors on the form they will not be subscribed?
(Assignee)

Comment 23

7 years ago
done in r89656
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Keywords: qawanted
Resolution: --- → FIXED
(Assignee)

Comment 24

7 years ago
pushed to production r89685
(Reporter)

Comment 25

7 years ago
(In reply to comment #22)
> Do you realize that people can press the button, but if there are errors on
> the form they will not be subscribed?

Yes - that's fine. Thanks for mentioning.
verified fixed http://www.mozilla.com/en-US/newsletter/
Status: RESOLVED → VERIFIED
Keywords: qawanted
Component: www.mozilla.org/firefox → www.mozilla.org
Product: Websites → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.