MyatThuKo
commented
3 years ago Changes
Added an on-page Global Site Tag (gtag.js) for Google Analytics Support configurable from _config.yml.
How Has This Been Tested?
First, I installed the Ruby version to my MacBook by following this stackoverflow. I used rbenv to set up a Ruby environment to test locally on my MacBook.
As Saksham mentioned above, we used our own Measurement ID to test out the tracking on the Google Analytics Website.
Our code does not have any effect on other code base and does not have any conflicts.
Mentions
@saksham1991999 and @prabalchhatkuli
Types of changes
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
- [x] New feature and improvements (non-breaking change which adds/improves functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] Code Refactoring (an internal change that is not user-facing)
- [ ] Documentation
- [ ] Test, CI, or build
Checklist
- [x] Coding style of this project is followed
- [ ] Change in documentation is required
- [x] Documentation has been updated accordingly
- [ ] Unit tests have been added to cover code change
Korusuke
Changes
Added a on-page Global Site Tag (gtag.js) for Google Analytics Support configurable from _config.yml.
How Has This Been Tested?
Created our own Measurement ID and added the on-page tag to header.js along with the Measurement ID confidurable from config.js
Checked the source code on live server and matched the tag with the instructions provided from Google Analytics. Also was able to track the views on my Google Analytics dashboard successfully.
Our change doesn't affects other areas of code.
Mentions
@prabalchhatkuli and @MyatThuKo
Types of changes
Checklist