Google Analytics

[karimkawambwa]

Description

Initial Track different page usages.

• [x] Track indicator action buttons
• [x] Track Analysis page share and download
• [x] Track Scroll percentage

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• [ ] New feature (non-breaking change which adds functionality)

Screenshots

Checklist:

• [ ] My code follows the style guidelines of this project
• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation

[kilemensi]

PS: I think we also need to track actions on Data by Topic side of things in charts.js

[karimkawambwa]

PS: I think we also need to track actions on Data by Topic side of things in charts.js

I knew i was forgetting something

PS: It is sugested that the actions be unique eventAction

cc @kilemensi

[karimkawambwa]

PS: It is sugested that the actions be unique eventAction

@kilemensi let me expand on that

if a user clicks download on two different indicators but you use same action name ‘Download’, then in that case Google Analytics will report only one unique event

[kilemensi]

PS: It is sugested that the actions be unique eventAction

This is one of the examples in the documentation @karimkawambwa:

ga('send', {
  hitType: 'event',
  eventCategory: 'Videos',
  eventAction: 'play',
  eventLabel: 'Fall Campaign'
});

play can not be unique there. I think eventLabel is what makes it unique in this case & in our case, we're using unique eventLabels as well.

[karimkawambwa]

PS: It is sugested that the actions be unique eventAction

This is one of the examples in the documentation @karimkawambwa:

ga('send', {
  hitType: 'event',
  eventCategory: 'Videos',
  eventAction: 'play',
  eventLabel: 'Fall Campaign'
});

play can not be unique there. I think eventLabel is what makes it unique in this case.

Hmm... Lets implement your suggestions and edit as we go

[karimkawambwa]

@kilemensi this is ready, I think the video tracking should go in a separate PR because tracking the youtube click will need api. I was looking into ?enablejsapi=1 if its not deprecated we could use that in the iframe and get a state change when play is clicked then send google analytics.But youtube has its play count so we could still tell if people are playing it or not.

[kilemensi]

@kilemensi this is ready, I think the video tracking should go in a separate PR because tracking the youtube click will need api. I was looking into ?enablejsapi=1 if its not deprecated we could use that in the iframe and get a state change when play is clicked then send google analytics.But youtube has its play count so we could still tell if people are playing it or not.

My thinking ìs enablejapi=1 is still supported, have you heard anything to the contrary @karimkawambwa ? Because then tracking play becomes a simple matter of creating the player scriptand attaching events: https://developers.google.com/youtube/iframe_api_reference#Examples

[karimkawambwa]

cc @kilemensi tested