Closed chrisblakley closed 8 months ago
For this issue it was that a second GA tag was added by a third-party to GTM which conflicted with the Nebula GA4 tag. This appears to be a non-Nebula issue, but I want to review this to see if we can detect/avoid these kinds of conflicts in the future.
Not sure if this console error is related:
I don't think it is because the error is present in both the initial page load and subsequent page load, but still worth looking into.
The current solution is if both GA4 and GTM Nebula Options exist, then we'll delay loading GTM by 1 second.
Confirming this works given the situation on this website. Could dial in the setTimeout to lower it from 1 second eventually.
I noticed that a website sends the GA4 page_view on initial load, but didn't have any of the page view properties that Nebula usually sets... Then on reload, they were all there.
Initial Load:
Subsequent Load (simply refreshing the same page a moment later):