Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recent issues with Google Tag manager? #37

Open
broeker opened this issue Aug 13, 2019 · 1 comment
Open

Recent issues with Google Tag manager? #37

broeker opened this issue Aug 13, 2019 · 1 comment

Comments

@broeker
Copy link

broeker commented Aug 13, 2019

Greetings:

We had a perfectly working implementation of Riveted using Google Tag Manager that was working fine, but nobody had checked analytics for awhile and suddenly we're not seeing any Riveted data coming in to Google Analytics.

  1. The Google Tag continues to fire every 5 seconds

  2. However in a debugger we are seeing Command ignored. Unknown target: undefined every time the Google Analytics function tries to run. It seems to be incrementing each call e.g. gtm13.set, gtm15, gtm17.set and so on.

See attached screenshot. We have not made any configuration changes to Tag Manager or Analytics since this was last working.

Anybody else seeing this??

undefined

@drorsnir
Copy link

As far as I can tell, this isn't a problem with Riveted. From personal knowledge (and looking at the source code, too), Riveted doesn't create GA trackers, which is what your issue seems to stem from

From the log you're showing, it looks like a new tracker is created every time [ga( "create") ], but for the same property, and then you're getting a "duplicate tracking name" error there, and the tracker is not set.
After that, any command you try to issue to it will fail, including Riveted's events.

So it looks to me you need to look at those "duplicate tracking name" errors and see what causes them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants