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 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.
The Google Tag continues to fire every 5 seconds
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??
The text was updated successfully, but these errors were encountered:
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.
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.
The Google Tag continues to fire every 5 seconds
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??
The text was updated successfully, but these errors were encountered: