You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We tend to have to setup at least Google Tag Manager on most of our apps, and while the snippiet is always the same we usually do it slightly differently each time - sometimes we just have it in layouts/application.html.erb, sometimes its in layouts/_google.html.erb, and so on.
It would be good if we could have an established pattern for structuring analytics in views, and had support out of the box for enabling Google Tag Manager by just setting an env variable.
We could also hopefully use this to help encourage good practices around analytics.
The text was updated successfully, but these errors were encountered:
Given that analytics are sometimes a contentious topic, I'm hesitant to make it part of every app. I think we should make this a variant that devs opt-in to via the YAML config. That would make the path clear for templating other kinds of analytics too.
We tend to have to setup at least Google Tag Manager on most of our apps, and while the snippiet is always the same we usually do it slightly differently each time - sometimes we just have it in
layouts/application.html.erb
, sometimes its inlayouts/_google.html.erb
, and so on.It would be good if we could have an established pattern for structuring analytics in views, and had support out of the box for enabling Google Tag Manager by just setting an env variable.
We could also hopefully use this to help encourage good practices around analytics.
The text was updated successfully, but these errors were encountered: