Closed Bug 1217883 Opened 9 years ago Closed 8 years ago

Additional Fall Campaign GTM Reqs

Categories

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

Production
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: garethc, Unassigned)

References

Details

(Whiteboard: [kb=1884006] )

We currently have about 90% of the campaign experiences tagged in GTM. We just need a dataLayer push added to some of the interactions so I can hook into via GTM. Below is what I need by page: 1) /firstrun/learnmore/ When the user clicks on the Firefox tab to open /learnmore/, can you please send: window.dataLayer.push({ event: 'firstrun-interactions', interaction: 'tab-visible' }); We'll need this to properly calculate engagement rates on the /learnmore/ page. 2) /whatsnew/ & /whatsnew/b/ Not sure if this page will launch along side another tab, but it if does and the user clicks on the tab to open, can you please send: window.dataLayer.push({ event: 'whatsnew-interactions', interaction: 'tab-visible' }); 3) /smarton/ page Dev page: https://www-demo1.allizom.org/b/en-US/teach/smarton/tracking/ Due to the length of this page, I'd like to measure scroll interactions to see how far users travel down the page and how engagement changes. Can we send the following when a user scrolls through a section? window.dataLayer.push({ event: 'smarton-interactions', interaction: 'scroll', section: sectionIDValue // Eg. sectionIDValues: ask, know, do chat }); Can we also measure interaction with the video and send the following: window.dataLayer.push({ event: 'smarton-interactions', interaction: playState // Eg. playState: play-video, complete-video }); 4) /private-browsing/ page I'd like to measure scroll interactions to see how far users travel down the page and how engagement changes. Can we send the following when a user scrolls through a section? window.dataLayer.push({ event: 'private-browsing-page-interactions', interaction: 'scroll', section: sectionClassValue // Eg. tracking-protection, when-to-use, etc. });
jpetto, is this something you can help with?
Flags: needinfo?(jon)
I can assist on any pages merged to master. For pages currently in development, I will refer the dev to this bug.
Flags: needinfo?(jon)
All of these pages are still in development/PR phase. I've pinged each PR with a link back to this bug, and cc'd all the associated devs.
Events for both whatsnew/firstrun are now on demo2 as per the description in this bug: https://www-demo2.allizom.org/en-US/firefox/42.0/whatsnew/ https://www-demo2.allizom.org/en-US/firefox/42.0/whatsnew/b/ https://www-demo2.allizom.org/en-US/firefox/42.0/firstrun/learnmore/ Note: I included visibility events for both /whatsnew variations. I don't believe either of these pages should be an inactive tab when they open if more than one tab exists (e.g. Windows 10 welcome page is the second tab). Either way, including the GA event for visibility here doesn't really cost us much to be on the safe side.
Thanks Alex. Do you know the status about the other events? Who would be the dev working on those experiences? James, can you please hook into these events via GTM and let me know when that is ready? Thanks.
Flags: needinfo?(james.lorence)
(In reply to Gareth Cull [:garethc] from comment #5) > Thanks Alex. Do you know the status about the other events? Who would be the > dev working on those experiences? Craig is working on the smarton pages, Malena is working on the TP product page. Not sure on the status in terms of GA events for said pages, so best check in the relevant bugs. Thanks!
Gareth, tracking in GTM for these events have all been setup.
Flags: needinfo?(james.lorence)
Whiteboard: [kb=1884006]
James, there was some updates to https://www-demo1.allizom.org/en-US/teach/smarton/tracking/ and I can't see the scroll / link / video events appear on demo1 in GA. Can you please update our rules on the GTM and verify? Thanks. Gareth
Flags: needinfo?(james.lorence)
Old bug, closing.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(luka.cempre)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.