Closed
Bug 1118933
Opened 11 years ago
Closed 10 years ago
GA events tracking for Privacy Day pages on Mozilla.org
Categories
(www.mozilla.org :: Analytics, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: malexis, Assigned: garethc)
References
Details
(Whiteboard: [kb=1623657] )
Gareth,
This is a new section on Mozilla.org, four new pages similar layout to the Firefox tips.
Here are the mockups:
https://drive.google.com/a/mozilla.com/file/d/0B2n1FR7dq3CmamNUWnNYQXJJRFBXQVRVNFVlaldOQWJyTXZr/view?usp=sharing
Steven is starting implementation this week.
Go live date is Jan 28
Updated•11 years ago
|
Whiteboard: [kb=1623657]
Comment 1•11 years ago
|
||
There's also a related home page promo we'll want to put some GA goodness on. Implementation tracking in bug 1112324 but we can keep all the GA stuff in this bug.
| Assignee | ||
Comment 2•11 years ago
|
||
Here are the GA requirements based on the pdf that was provided:
1) On click of each tab, please set the following event:
_gaq.push(['_trackEvent', '/privacy/ Interactions', Tab, 'Tab Click']);
where Tab is:
1. Ask
2. Learn
3. Act
4. Discuss
5. Support
2) On click of any text links, can you please record the active tab and set the following event:
_gaq.push(['_trackEvent', '/privacy/ Interactions', ActiveTab, href]);
where ActiveTab is:
1. Ask
2. Learn
3. Act
4. Discuss
5. Support
3) On click of any next / previous buttons, can you please record the active tab and set the following event:
_gaq.push(['_trackEvent', '/privacy/ Interactions', ActiveTab, buttonClicked]);
where ActiveTab is:
1. Ask
2. Learn
3. Act
4. Discuss
5. Support
and buttonClicked is:
Next
Previous
4) On click of the 'Why Privacy Matters Button' can you please record the active tab and set the following event:
_gaq.push(['_trackEvent', '/privacy/ Interactions', ActiveTab, state]);
where ActiveTab is:
1. Ask
2. Learn
3. Act
4. Discuss
5. Support
where state is:
start video - button click
complete video
5) Can you re-use event tracking for the share button and newsletter sign-ups? Do you need these reqs as well?
Any questions, let me know. Thanks.
Gareth
Comment 3•11 years ago
|
||
Gareth, these are implemented on demo1 (https://www-demo1.allizom.org/en-US/privacy/tips/). Can you confirm?
Regarding 4), this isn't an embedded video player - just a link to an external site. I presume we can just rely on the generic tracking for this one?
Flags: needinfo?(garethcull.bugs)
| Assignee | ||
Comment 4•11 years ago
|
||
Thanks Steven. I'll review and will confirm that the metrics are coming in correctly. Regarding #4, since we can't track the video completions, just leave that out and only track the button clicks. Thanks!
Gareth
Flags: needinfo?(garethcull.bugs)
| Assignee | ||
Comment 5•11 years ago
|
||
Hey Steven,
Thanks for your help on the GA implementation. Here's the results of my tests:
1) I'm seeing multiple events firing on click of the buttons at the bottom of the page. For example, the #1 Ask tab is active and when I click on the 'Learn More about Privacy >>' Button, 2 events fire. One where the event label is "NEXT" and another where it is "#learn" (http://cl.ly/image/3e000Q251U0i). Can you please combine these two events into one event?
2) Can we differentiate between the button click of 'Why privacy matters' vs. the text link above it? On click of the button, can you call the following:
_gaq.push(['_trackEvent', '/privacy/ Interactions', ActiveTab, 'Why Privacy Matters CTA Btn']);
3) I'm not seeing any events trigger on the social share in the top left hand corner of the nav. Can we also set the event value for these to be: Facebook, Twitter and Google+.
4) I noticed that when i clicked on the twitter share was pointing to the Independent page. Can we please point this to the /privacy/ page and update the utm parameters to the following:
https://www.mozilla.org/privacy/tips/?utm_source=twitter&utm_medium=social&utm_campaign=privacy2015&utm_content=WebsiteShare
You may also need to update the urls for the Facebook and G+ sharing.
Any questions, let me know. Thanks.
Gareth
Comment 6•11 years ago
|
||
The issues from comment #5 should be addressed on demo1. Please re-test, thanks. I am still waiting on a short-link for the twitter content and will update when I have it.
| Assignee | ||
Comment 7•11 years ago
|
||
Thanks Steven.
#1 & #2 look good now. Could you please tweak the events for both social sharing buttons so they are consistent with each other.
On click of a social icon, please call:
_gaq.push(['_trackEvent', '/privacy/ Interactions', ActiveTab, socialShare]);
where socialShare is:
Twitter
Facebook
Google+
That's about it. Thanks for the quick fixes!
Gareth
Comment 8•11 years ago
|
||
Alex, we need to over-ride the labels in the gaTrack call from the mozilla-share-cta script. Any idea how best to over-ride that per page?
Flags: needinfo?(agibson)
Comment 9•11 years ago
|
||
(In reply to Steven Garrity [:sgarrity] from comment #8)
> Alex, we need to over-ride the labels in the gaTrack call from the
> mozilla-share-cta script. Any idea how best to over-ride that per page?
The relevant code is here: https://github.com/mozilla/bedrock/blob/master/media/js/base/mozilla-share-cta.js#L73
You could probably adjust it to pass in a custom label if needed - just need to make sure it doesn't break in other places this is used.
I would question just how vital this is to do though - we currently track events for this widget globally instead of a per-page basis, just like we do for newsletter signups. Gareth, is there no way to tell which page these events come from irrespective of the label?
Flags: needinfo?(agibson)
| Assignee | ||
Comment 10•11 years ago
|
||
I just noticed the other social share functionality was grouped under the /privacy/ interactions category and was looking to have all share functionality events under a common hierarchy, which helps with analysis. Its not a huge deal for this particular case and i can make a note of it when I pull the numbers. So just leave as is. Thanks.
Gareth
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•