Gradual feature rollout: This feature is being rolled out gradually and may not be available in your account yet.You can use the Tag Diagnostics tool to find and fix issues with your website's tags, ensuring your data collection is accurate. You can access the Tag Diagnostics tool from the Google tag sections of both Google Ads and Google Analytics, and through Google Tag Manager.
Open the Tag Diagnostics tool
- Open the Google tag settings.
Where are the Google tag settings? - In the Google tag settings, go to the Tag quality subsection of the Your Google tag section.
- View the tag quality status, then click to find and fix tag detected issues.
Tag quality statuses
The Tag Diagnostics tool shows the following tag quality statuses to highlight detected issues, their severity, and how to fix them. When you fix an issue, the status updates to show the improved tag quality.
Excellent
Excellent means that no issues have been detected with the Google tag. You won’t see any issues for this data quality status as your tags are considered fully optimized. However, be sure to continue to check the tag quality status as the status might change when new issues are detected.
Good
Good means that no issues have been detected with the Google tag, but we've provided at least one recommendation to improve your tag quality.
Needs attention
Needs attention means an issue with the Google tag needs your attention. The issue should be fixed, but the issue isn't critical.
Urgent
Urgent means that an urgent issue has been detected with the Google tag that you must fix immediately to preserve measurement.
Diagnostics
We may show you one or more of the following diagnostics to help you identify issues with your tagging setup:
- Additional domains detected for configuration: This diagnostic appears when we've detected one or more additional domains that you haven't specified in your Google tag settings. To fix this issue, specify all of your domains that use the Google tag.
- Config command out of order: This diagnostic appears when your gtag event commands are sent before your gtag config commands. This may result in unexpected behavior while routing and processing those events. To fix this issue, verify that the code on each page correctly positions the config command before any event commands.
- Missing conversion linker: This diagnostic appears when you have a Floodlight and/or Google Ads tag, but you have not added a conversion linker tag to your Google Tag Manager container. To fix this issue, add a conversion linker tag to your container.
- Some of your pages are not tagged: This diagnostic appears when pages on your website are untagged, which may impact the performance of your measurement. To fix this issue, visit the Tag coverage summary to find and fix the untagged pages.
The following diagnostics are being rolled out gradually and may not be available in your account yet:
- Consent missing for EEA users: This diagnostic appears when the data sent through the Google tag in the European Economic Area (EEA) is not labeled with consent and we haven't been able to determine that you've blocked tags. To fix this, verify that the data is labeled with consent.
- Some pages missing consent for EEA users: This diagnostic appears when the data sent through the Google tag in the European Economic Area (EEA) is not labeled with consent on some pages of your website and we have not been able to determine that you've blocked tags on these pages. To fix this, verify that the data is labeled with consent.
- Update your consent settings: This diagnostic appears when the data sent through Google tags in the European Economic Area (EEA) is not labeled with consent and we have been able to determine that you block tags for your entire website. To fix this issue, read Manage default consent settings to attest to sending data as consented.
- Website/App missing EEA consent for ads personalization: This diagnostic appears when the data sent through the Google tag in the European Economic Area (EEA) is not labeled with consent for ads personalization. You either have a consent mode v1 implementation and have been auto-delegated (ad_user_data reads from ad_storage) or you've implemented consent mode v2 but haven't implemented personalization consent. To fix this issue, upgrade to consent mode v2.
- Consent mode installation out of order: This diagnostic appears when some of your web pages are loading consent mode commands in the wrong order, which can lead to inaccurate consent signals. To fix this issue, verify that you've positioned the consent mode commands in the correct order.
- Verify consent mode set up as 0% consent rate detected: This diagnostic appears when we detect that you always send an ad_user_data denied signal regardless of geo settings, which would result in a 0% consent rate. To fix this issue, troubleshoot your consent setup.
- 0% consent rate detected in some regions: This diagnostic appears when we detect that you're always sending ad_user_data denied signals in non-EEA regions. This would result in 0% consent rate outside of EEA indicating that you may have implemented a EEA only consent set up globally. 0% consent rate can lead to loss in measurement and can break remarketing outside of the EEA where it isn’t required. To fix this issue, troubleshoot your consent setup.
