additional “GT-5R49QC5” visible on the website

Thanks for reaching out @sp2023. The GT- reference you’re referring to is a Google tag snippet, as per this guide. Site Kit uses the new Google tag to connect a site with a users chosen Google Analytics 4 (GA4) property. This is why you won’t see your GA4 property printed when checking your sites source code.

Let me know if you have any further questions on this.

Google tag assistant extension is giving this error for the actual one , GTM-PN9T5Q2M

From inspecting your site I can see this Google Tag Manager container has been added via Site Kit and is functioning fine. This Tag Manager snippet differs to the new Google tag, and I can confirm all is working as expected with your site.

Hi,
Thankyou for the reply!

So, can we ignore this message showing on the google tag assistance legacy extension for GTM-PN9T5Q2M
Google Tag Manager Errors : “Invalid or missing account ID”

@sp2023 Rather than using the legacy Chrome extension, you can use it’s successor, the tagassistant.google.com service. When I was checking your site I used this service and there are no issues with your Site Kit placed snippet, see below:

I did notice that your Google Tag Manager container is not published, however, this is something that must be addressed from Tag Manager, and not Site Kit. This may be why your Chrome extension is showing a “Google Tag Manager Errors : “Invalid or missing account ID” error, I can’t be sure.

Let me know if you have any further questions on this.

Thank you again!

yes, there are changes in the google tag manager, but I was getting this error message before I started making changes to the GTM.

But everything seems to be working, so I will ignore it.
Thanks again
===========

one last question please, why are there two scripts on the site?
I can see these two. and the i believe the first script is the issue for the error message
<script async=”” src=”“https://www.googletagmanager.com/gtm.js?id=GTM-PN9T5Q2M&#8221;“></script>

<script>
			( function( w, d, s, l, i ) {
				w[l] = w[l] || [];
				w[l].push( {'gtm.start': new Date().getTime(), event: 'gtm.js'} );
				var f = d.getElementsByTagName( s )[0],
					j = d.createElement( s ), dl = l != 'dataLayer' ? '&l=' + l : '';
				j.async = true;
				j.src = 'https://www.googletagmanager.com/gtm.js?id=' + i + dl;
				f.parentNode.insertBefore( j, f );
			} )( window, document, 'script', 'dataLayer', 'GTM-PN9T5Q2M' );
			
</script>

• This reply was modified 1 year, 8 months ago by sp2023.
• This reply was modified 1 year, 8 months ago by sp2023.

But everything seems to be working, so I will ignore it.
Thanks again

No problem, happy to help

one last question please, why are there two scripts on the site?
I can see these two. and the i believe the first script is the issue for the error message

You have both an Analytics tag placed via Site Kit (using Google tag), and also a Google Tag Manager snippet placed via Site Kit. These are normal if you’ve connected both modules within Site Kit, and you’ll notice there is a comment before and after each snippet to indicate they are placed via Site Kit. You’ll find out more on these snippets and how Site Kit places them by visiting this guide on the plugin website. If you’re only using Analytics, you can disconnect the Tag Manager module if you wish.

Let me know if you have any further questions with the above.

Hi thanks, this issue is resolved.

In this link, they have mentioned that the error message can be ignored.

https://support.google.com/tagassistant/answer/3207128?hl=en#invalid_id

NOTE:?If your container ID (i.e. what’s referenced here as ‘account ID’) is of format GTM-XXXXXXX, where the portion after ‘GTM-’ is longer than 6 characters, you may see this error unnecessarily. This false error will be resolved in a future update. In the meantime, as long as your container ID follows the correct format as described below, you may ignore this error.

Glad to hear it @sp2023. Be sure to reach out if you have any further queries. If you have a moment free be sure to also share your thoughts on the plugin after you’ve tested out the features and the plugin dashboard.