Missing Google tags
Tag Manager has event tags, such as a conversion or form event, with no Google tag in the container to send them. Google's fix is to add a Google tag for each measurement product in use, such as Google Ads, Google Analytics or Floodlight. Add the tag, publish a new container version, then check Tag Assistant to see the events go through it.
At a glance
- Where it shows
- The Diagnostics tab in the Google tag settings, under Tag quality.
- What stops
- The events from the event tags that depend on a missing Google tag. They do not reach the product they were built for.
- How serious
- Medium. The events are missing from the measurement product, and the page itself shows no warning.
What it means
Google's diagnostic checks whether each event tag in the container has a Google tag it can send through. A Google tag is the base code for a product such as Google Ads, Google Analytics or Floodlight. An event tag with no matching base tag has nowhere to send its events, even though the tag itself is present and fires.
Google's page gives one fix: add a Google tag for each measurement product in use. The message is about the container, not the website's code, so the container is where to look first.
What actually triggers it
Event tags built in a container that never got a Google tag
Not on Google's help page
Conversion or event tags were set up in Tag Manager, but the base Google tag for the product they report to was never added. The tags look finished, so nobody looks for the missing one.
A measurement product added to the site and not the container
Not on Google's help page
A second Google Ads account, Floodlight or Analytics property is wired with an event tag, but the base tag for it was not added.
A base tag removed in a cleanup
Not on Google's help page
A tidy-up removes a base Google tag that looks unused, while the event tags that depend on it stay in place.
Fix it in this order
- Open the Diagnostics tab in the Google tag settings and read the Missing Google tags message.
- List each event tag that sends to Google Ads, Google Analytics or Floodlight, and the product each one reports to.
- Add a Google tag in the container for each product on that list that has no base tag yet.
- Publish a new version of the container. A tag added in a workspace does nothing for visitors until the version is published.
- Check the Diagnostics tab again, and use Tag Assistant to confirm the event tags now send through the Google tag.
If the message stays after publishing, the version did not include the change. Open the live version in the container to see what visitors run.
Often confused with
The base tag is present, but its configuration code is wrong or missing from the page, so automatic events are not measured. The fix is code placement on the page, not a missing tag in the container.
A Google Ads or Floodlight tag exists, but the container has no conversion linker. Adding a Google tag does not fix that.