I've been working on tagging implementations for a number of new sites recently, so this has caught me out more than once. Incidentally having Shields Up will also block any other Google endpoints, including Google Ads, Google Analytics and Optimize. Having 'Shields Up' on a website (which is the default) will absolutely prevent Tag Assistant from connecting. However if, like me, you use Brave as your browser of choice, the culprit is likely to be Brave's 'Shields' feature. Julius Fedorovicius at Analytics Mania has done a good job in rounding up many of the other reasons. For example, the Tag Manager help community reported that it was sometimes a result of "Chrome putting background tabs to sleep" and that there was a fix in the works for that particular issue. There are lots of reasons this connection problem might happen. Reasons for the 'Could not connect' error And then, 20 seconds or so later, you get that frustrating 'Could not connect' timeout error. The blue connecting bar gets half way across the screen before grinding to a halt. That's right: you hit Preview in Google Tag Manager, enter your URL, and click Start. However if you have used it more than just a little bit, you will probably have already encountered this error: The new Preview mode is better in many ways, not least because it now appears in its own tab rather than in an iFrame on the page being debugged. In October Google introduced a new version of Google Tag Manager's Preview and Debug mode, making it part of Google Tag Assistant at the same time. 4 Is Brave the wrong tool? Introducing the new Preview mode
0 Comments
Leave a Reply. |