During analysis of some activity on our organization website, we have discovered that some activity from button clicks are not being tracked by some browsers. Most often, this appears to be for Safari and Mozilla/Firefox but not related to privacy blocking because some activity is tracked with no issues but not some button clicks (triggered by a specific CSS data attribute).
The action triggers the following in console: Loading failed for the <script> with source “https://assets.adobedtm.com/ ... . Clicking on the link provides another message reading in part
// For license information, see `https://assets.adobedtm.com/
This is followed by the rule action that was not fired. Has anyone else encountered this or have any idea why or how to work around this situation?
Yes, @yuhuisg, this activity is to other pages on our site; however, would this be expected to happen for a large number of pages (about 100) only on certain browsers? We did have the same thought and have tested this since I submitted the original query. For our testing, we set a long timeout (1500ms) in our Launch rule. This did not have any effect. The loading failed message was displayed in console immediately upon the click of the button.
Are these click tracking coming from clicks that cause a new page to be loaded in the browser? If so, it could be that you're facing the issue where the browser redirects to that next page before the click tracking has had a chance to complete successfully.