Tag found too low on page
Tag Diagnostics found the Google tag placed far down the page, where it loads late and can miss visits that leave early. Find the tag's script in the page source and note how far down it sits. Move it up into the page head, or move the Tag Manager tag so it fires from the head. Use one loader only, then publish and check the diagnostic again.
At a glance
- Where it shows
- The Diagnostics tab in the Google tag settings.
- What stops
- Nothing stops. A visit that leaves before a late tag loads is not recorded.
- How serious
- A diagnostic, not a penalty. The cost is visits and clicks that go unrecorded.
What it means
A script placed low in the body waits for everything above it to load before it starts. Google's diagnostic flags that delay and the signal loss that comes with it. The message is about where the tag starts, not whether it is on the page.
Because the message concerns position, a tag can be on every page and still show it. The check is the page as a visitor's browser receives it, which is not always the same as a copy fetched by a tool.
What actually triggers it
A snippet added in the footer or near the closing body tag
A footer edit or a plugin that places the script at the bottom of the page is one route to this message. In the page source, find the script's address. If it sits after the main content, this is the cause.
A container that loads only after the visitor scrolls
Not on Google's help page
In one real site, the Tag Manager container loaded only after the visitor scrolled. A fetched copy of the page showed no tag at all, even where the tag worked. Read the live container or check in a real browser before deciding the tag is missing.
Fix it in this order
- Open the page in a browser, view the page source, and find the Google tag's script address. Note how far down the page it sits.
- Check the live container, not the workspace, or load the page in a real browser, so you are reading what visitors receive.
- Move the snippet into the page head through the site template, or move the Tag Manager tag so it fires from the head. Use one loader, because the same script loaded from both places only loads twice.
- Create a version of the container and publish it, or deploy the site change, then check the status again in Tag Diagnostics.
Often confused with
Some of your pages are not tagged
Pages without the tag at all. This message is about where the tag sits on pages that already carry it.
The tag is present, but an event runs before its config call. Check the order of calls in the source, not the position of the tag.