This makes sense to me, I agree with the approach.
dharizza β created an issue.
dharizza β made their first commit to this issueβs fork.
This bug should be fixed by https://www.drupal.org/project/google_tag/issues/3491175 π Loading the library gtag.ajax in the header causes issues with other JS Active (which is now merged and a new release has tagged). Updating google_tag to 2.0.7 should help.
This was introduced by https://www.drupal.org/project/google_tag/issues/3452712 π Possibly script loading/placement issue Fixed , but when I was testing it didn't look like I needed to have the gtag.ajax in the header as well, just gtag and gtm makes it for me, so that's why I only moved the ajax one.
This is a Drupal CMS stable blocker. See #3487542-13: Add Google Tag recipe.
dharizza β created an issue.
dharizza β made their first commit to this issueβs fork.
@poker10 The Google Analytics module has been marked as obsolete and its use as deprecated, the recommendation now is to use google_tag. Also, considering the persona we're trying to reach with Drupal CMS is marketers and the market share reflects the majority of them are using Google Analytics for web analytics and Google Tag Manager for tag management, the use of the google_tag module is more future proof as it allows them to keep using both.
dharizza β created an issue.
volkswagenchick β credited dharizza β .
laura.gates β credited dharizza β .
dharizza β made their first commit to this issueβs fork.
dharizza β made their first commit to this issueβs fork.