What is the Google Tag Manager Container Quality Warning?

Overview

Follow this guide to learn about the new "Container Quality" warning and feature in Google Tag Manager (GTM), which provides a status update on your tag implementation and container.

The warning status can range from "Excellent" to "Urgent," each indicating different levels of concern regarding your tags. It includes guidance on how to view and address issues identified in the GTM container and how to handle false positives.


Understanding the Google Tag Manager Container Quality Warning:

On the Google Tag Manager homepage, you may see a warning titled “Container Quality.” In addition to the warning, you will see a status of either "Excellent", "Good", "Needs Attention", or "Urgent".

Step 1 screenshot

Tag Quality Statuses:

  • Excellent: No issues have been detected with the Google tag. Your tags are fully optimized, and you should not experience any issues related to tag implementation.
  • Good: No issues have been detected with the Google tag, but at least one recommendation has been provided to improve your tag quality.
  • Needs Attention: There is an issue with the Google tag that requires your attention. While the issue needs to be addressed, it is not critical.
  • Urgent: An urgent issue has been detected with the Google tag that must be fixed immediately to preserve measurement accuracy. Immediate action is required to rectify this issue.

Viewing the Issue:

  • To view the issues within your container that may be causing this warning, click on the "View Issue" button located within the warning on the Google Tag Manager homepage.
  • Here you will be able to see a list of the issues identified by Google Tag Manager under the section titled "Action items".
    • (See Figure 1)

Step 2 screenshot

Figure 1

Resolving False Positives:

False positives can occur when correctly tagged pages are mistakenly flagged as untagged.

False Positives

False positives can occur when correctly tagged pages are mistakenly flagged as untagged. Common reasons include:

  • Low Traffic: Pages with minimal traffic might not trigger tag detection frequently.
  • Redirects: Pages serving as redirects might be flagged incorrectly if the final destination page is tagged.
  • Trailing Backslashes: Differences in URL formatting (e.g., trailing slashes) can cause duplicate flags for the same page.
  • Capitalization: Variations in URL capitalization can result in the same page being flagged as separate untagged pages.

Steps to Resolve False Positives:

  • Verify that the tags are correctly implemented on the flagged pages using the Tag Assistant. If Tag Assistant confirms the correct implementation, the warning should resolve itself within 24 hours.
  • If a page is falsely flagged and not relevant for tracking, you can choose to ignore it in the summary. This removes the alert from your diagnostics but allows you to revisit it later if necessary.

GA4 Error:

  • Some users might encounter a false error in Google Analytics 4 - GA4 after the Elevar configuration.
  • This issue often appears as a false warning because the pageview event is not executed on the "All Pages" trigger in GTM. Instead, the pageview event is triggered with Elevar's dl_user_data event, which passes all cart and user-related information to the pageviews and tags.
  • This setup means that the GA4 warning could incorrectly flag pages as untagged, even though the Elevar configuration is correctly implemented.

❗️

Note: Wait 24 hours after making any adjustments

After making adjustments or ignoring certain pages, allow up to 24 hours for the Tag Coverage Summary to update.

This waiting period helps ensure that the warning status reflects the latest tag implementation status.