GA4 script returning 404 on sGTM

[wiral1]

Hi,

I’m facing an issue where the GA4 tracking script (gtag.js) is returning a 404 Not Found status when requested from our custom tagging server URL, while other scripts (like GTM and Google Ads) load perfectly with a 200 OK status. I’m using Stape with GTM-KIt For Wordpress

Serwer Container

[Roman_Kaliniichuk]

Hi,
It seems that this issue is related to the GA4 property itself. As you can see, I loaded a different Google tag, and everything worked correctly.

Please try creating a new property within the same GA4 account and using the new Measurement ID.

[wiral1]

Hi,

Thank you for the suggestion. However, we managed to identify and resolve the root cause of the issue without having to create a new GA4 property.

The issue was not with the GA4 property itself, but rather with the Google Tag routing/destination configuration. Both the GA4 Measurement ID (G-KR3SX5XRSK) and the Google Ads Tag (AW-18098495874) were combined under the same Google Tag destination loader. When requesting the gtag script, this combination caused routing conflicts on Google’s servers, resulting in the 404 errors we observed.

We resolved this by isolating the destinations. We moved the GA4 Measurement ID (G-KR3SX5XRSK) to a new, dedicated Google Tag (GT-PHCH94GP) in the Google Tag settings interface.

Since separating them, both scripts load successfully. We noticed that some of the script requests return a 304 Not Modified status. We assume this is just normal browser caching behavior, but could you please confirm if this is correct and expected?

Best regards,

[Roman_Kaliniichuk]

Yes, that’s correct. A 304response is normal and expected. This is standard browser caching behavior and is not an issue.