GTM tag noscript error

This forum is for all Flare issues not related to any of the other categories.
Post Reply
LesiaZ
Jr. Propeller Head
Posts: 2
Joined: Fri Sep 08, 2017 2:20 am
Location: Lviv, Ukraine

GTM tag noscript error

Post by LesiaZ »

Hey all! Need your expertise here :)
We're getting a noscript issue when implementing Google Analytics for our help system.

We set up GTM on our Top Nav project using this guide from Google.
https://developers.google.com/tag-manager/quickstart

Basically, we inserted several lines of code into the master page (<head> and <body> sections - see #1 on the screenshot).

Google Analytics seems to be tracked fine, but we keep getting the noscript section see #3 on the screenshot.
GTM no-script code not found: either missing or not in <body>
Meaning that analytics is not collected from browsers that don't support javascript or have it turned off.
I contacted the Flare support did not come up with a solution so far.

The reason why it's happening is because when building the output, Flare puts the noscript session into div within div within div ( see #2 on the screenshot).
Any ideas how can make that piece of code stick right under the <body> tag?
Or perhaps other ways to fix this?
You do not have the required permissions to view the files attached to this post.
NorthEast
Master Propellus Maximus
Posts: 6363
Joined: Mon Mar 05, 2007 8:33 am

Re: GTM tag noscript error

Post by NorthEast »

I'd say the problem is with GTM, if it can't detect its own noscript code.
I don't know of any way to move the position of the noscript section (without using scripts).

Just to note, if a browser hasn't got javascript support, then the HTML5 help will not work.
LesiaZ
Jr. Propeller Head
Posts: 2
Joined: Fri Sep 08, 2017 2:20 am
Location: Lviv, Ukraine

Re: GTM tag noscript error

Post by LesiaZ »

Thanks Dave!

The GTM tag seems ok - at least, the analytics are gathered as expected.

Regarding javascript - yeah, it's a pain.
Thankfully, as far as I know, only old browsers don't support it - IE7 or so.
Post Reply