Most problems with Google Tag Manager configurations arise from the issues listed here. Consider these issues as you troubleshoot your containers. In all cases, use preview and debug to help identify any problems.
- Unpublished changes: Make sure that you have published your container with the tag changes in question, and that your trigger is configured properly to allow the tag to fire on the page you are testing. Note that it can take a few seconds for the container to publish. When testing, reload the page or clear your web browser's cache to ensure that your latest changes are loaded.
- Wrong trigger configuration: Double check that the conditions you have targeted are indeed present for the expected trigger behaviors.
- Triggers too specific: Check that your trigger isn't unnecessarily specific.
Example: A URL trigger that is set to fire on "http://www.example.com" will not fire if the URL is "https://www.example.com" (using "https") or "http://example.com" (without the "www"). The best practice is to use a common fragment for the trigger criteria, such as "example.com".
- Unexpected site or app changes: If your website or app code changes, it is possible that your triggers no longer work. This is especially common for web page triggers that depend on elements being present, such as HTML IDs and class attributes. A best practice to help avoid this problem is to leverage a data layer.
- Too many HTTP requests: Google Tag Manager can only fire tags within the capabilities of the browser. Web browsers will not open more than six to eight HTTP requests to a single domain at a time. If you have a high number of tags on the same domain firing under the same conditions, tags will only fire within this browser limitation.
- Container snippet problems: The Tag Manager container snippet might be installed incorrectly on your site. Use Tag Assistant to help verify installation. The best solution for this problem is to reinstall the snippet.
- Users leave the page before a tag fires: Proper installation of the Tag Manager snippet will help to minimize the window in which data loss is possible. Follow the installation guidance to make sure your tags fire optimally.
- Inappropriate tag types: Tag manager works best with asynchronous tags that are used for tracking and analytics purposes. Do not use Tag Manager to deploy tags that are associated with in-page structure (such as ad placement tags), or tags that require a delay in page load.