-
Notifications
You must be signed in to change notification settings - Fork 59
Reverting Tag Manager JavaScript Changes #620
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
Conversation
This reverts commit a124b73.
…indow._paq" This reverts commit 827ffb4.
… tracker site and url" This reverts commit e108fb1.
This reverts commit 63ca092.
This reverts commit 1a59c10.
…ckers" This reverts commit 6a1ec34.
…figs are applied" This reverts commit 9fb7e80.
…q functionality" This reverts commit f1e55e6.
@tsteur Could you have a look once ? |
I haven't tested it but looking at the other PRs that looks good 👍 |
Hello @snake14 , |
Hi @utrautmann . Sadly, it was reverting the changes I made to make Matomo Tag Manager and the regular tracker work better together. There was apparently a race condition or something that we missed in our testing. So, for now, it's best not to mix the two. If you have customers that need to call |
@snake14 : Thank you very much for your answer. I actually don't recommend my clients to use both tracking approaches together. In the past I saw often JavaScript errors in this case. |
Description:
Reverting Tag Manager JavaScript Changes because they appear to be preventing some tracking requests.
Review