Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

404 error for Google Tag Manager

People also ask

Why is my Google Tag Manager not firing?

Sometimes a tag is not firing where it should because of multiple triggers or multiple rules within a trigger. The Solution: As all tags fire as a result of trigger configurations, this is normally the best place to start when tags are not firing as intended. Start by double checking your trigger settings.

How do I track 404 errors in Google Analytics?

Go to the “Behavior” option in Google Analytics, click on “Site Content,” and then “All pages.” After that, type 404 or a similar identifier in the search box. You should be able to get information about 404 errors on your website from there.

What is Google Tag Manager error?

Google Tag Manager's JavaScript error trigger is used to fire tags when an uncaught JavaScript exception ( window. onError ) occurs. This tag may be used to log error messages in an analytics tool. Use a JavaScript error variable to capture the error message and send the value of that variable when a tag fires.


You need to publish a version of your container. If it is not published, the request will return a 404 error.

To publish your current workspace:

  1. Click Submit at the top right hand side of the screen. The Submit Changes screen will appear, with options to publish the container and save a version of your container.
  2. Select Publish and Create Version if it is not already selected.
  3. Review the Workspace Changes section to see if your configuration appears as you expect.
  4. Enter a Version Name and Version Description.
  5. If you have Tag Manager configured to use multiple environments, use the Publish to Environment section to select which environment you'd like to publish to.
  6. Click Publish.

I had the same issue even after publishing and got it fixed by simply deleting the subdomain "www" from the tag manager domain "https://googletagmanager.com" instead of "https://www.googletagmanager.com"

Seems the problem is that the DNS is blocking www. or the subdomain doesn't reroute properly to our region!


My issue was that had AdBlock enabled.


In my case it helped when I leave Preview and lunch it again. As I figured out my preview "outdated" somehow...