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
What I'm seeing at the moment is that a named tracker is created by default. I'm not doing anything to set a named tracker anywhere, I don't make any ga() call in my code. I'm merely including the tracking code.
<!-- Global site tag (gtag.js) - Google Analytics -->
<scriptasyncsrc="https://www.googletagmanager.com/gtag/js?id=MY-ACCOUNT-ID"></script><script>window.dataLayer=window.dataLayer||[];functiongtag(){dataLayer.push(arguments);}gtag('js',newDate());gtag('config','MY-ACCOUNT-ID');</script>
If in fact the default tracker is no longer the t0 one and an account specific one is used, then the plug-in should probably be updated to handle this.
If not everyone is seeing this behavior, then it would seem that we need some way of setting the default account name to use.
I'm OK with submitting a PR for this but I need more input on what others are seeing for behavior
The text was updated successfully, but these errors were encountered:
What I'm seeing at the moment is that a named tracker is created by default. I'm not doing anything to set a named tracker anywhere, I don't make any
ga()
call in my code. I'm merely including the tracking code.What I see when the app loads is
Note that the tracker name created is gtag_my_account_id. This is done in line 4049 of the gtag code (after formatting in chrome).
I have to call
For any of the tracking events to show show up in google analytics.
The problem is that there are redundant calls being made to the default tracker as well, which simply go into thin air.
If in fact the default tracker is no longer the t0 one and an account specific one is used, then the plug-in should probably be updated to handle this.
If not everyone is seeing this behavior, then it would seem that we need some way of setting the default account name to use.
I'm OK with submitting a PR for this but I need more input on what others are seeing for behavior
The text was updated successfully, but these errors were encountered: