Replace Google Analytics Code with Google Tag Manager Code #257
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
Osprey
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
resilience
Tom's Wishlist
type: bug
type: discussion
type: error handling
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/spee.ch#257
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Re: handlebarsHelpers.js - Google Analytics
The Google Analytics (GA) code is best being removed and replaced with Google Tag Manager (GTM).
Google Tag Manager
Google Tag Manager acts as a container you can put your Google Analytics code in, and any other code you want.
This means you can update, add or remove code without touching the site as well as having many more options in the GTM interface.
There are many other benefits for GTM over GA.
Here's some further information about GTM.
10 Reasons to Start Using Google Tag Manager Right Now
Tag Manager Quickstart
How to use Facebook Pixel with GTM...
Facebook Pixel with GTM
Google Tag Manager is a good idea, agreed. But we dont currently
add/remove a lot of tags.
On Thu, Nov 9, 2017 at 10:16 AM, Mark Firth notifications@github.com
wrote:
--
Josh Finer
COO/LBRY
I'll have to read up on GTM but I am interested in making this change. Off the top of my head, I am wondering if it will work with content that gets served directly. I have an npm package that allows me to send analytics directly to GA if needed, and I use that to log 'events' for assets that are served directly.
I would think so. It's just a container. Therefor; the GA code remains on the site, but is brought in dynamically. If you need to send analytics directly to GA, this can still be done regardless. :)