Tag Manager Troubleshooting and Configuration FAQ
Google Tag Manager plays a central role in most analytics setups, yet it is often the source of issues that lead to inaccurate data in GA4. Problems with triggers, sequencing, consent tools, legacy scripts or container structure can cause missing events, duplicate data or broken attribution. This FAQ explains the issues organisations most often encounter and what they usually mean.
Preview mode and firing issues
Why is Tag Manager preview mode not working
Preview mode can fail when browser extensions block cookies or scripts, when privacy settings prevent debugging or when site caching serves an older version of the container. Consent tools, network restrictions and cookie banners can also interrupt the connection to the preview environment. Clearing caching or disabling blockers often resolves the issue.
Why are my tags not firing
Tags may not fire when trigger conditions do not match the actual behaviour of the page or when the GA4 configuration tag does not load before other events. Hard coded scripts can override Tag Manager and prevent tags from loading. Consent tools may delay or block tags on the first pageview, which can make it appear as if the tag is not working.
Why do I see duplicate events
Duplicate events occur when the same code exists both in Tag Manager and hard coded on the site, or when multiple tags share the same trigger. Legacy analytics code, misplaced HTML snippets and repeated container injections often lead to this problem.
Event and trigger configuration
Why are my events firing at the wrong time
Events fire too early when triggers activate before the data layer is ready, and too late when triggers depend on unpredictable user actions or page states. Incorrect sequencing between the GA4 configuration tag and event tags can also cause events to fire out of order or with incomplete parameters.
Why are some events not appearing in GA4
An event may fire in Tag Manager but fail to appear in GA4 when the event name is not recognised, when required parameters are missing or when consent tools block transmission. Conflicts between legacy scripts and Tag Manager can also prevent events from reaching GA4.
Why is my data layer not working
Data layer issues occur when the object is overwritten by other scripts, when pushes happen before Tag Manager loads or when developers use inconsistent variable names. Page builders and JavaScript frameworks sometimes inject scripts that disrupt the intended data layer sequence.
Consent, cookies and sequencing
How do consent tools affect Tag Manager
Consent banners can block or delay analytics scripts until a user gives permission. When this is not configured correctly, Tag Manager may fire tags out of order, resulting in missing pageviews or incomplete events. This often leads to inflated direct traffic, unassigned channels or missing conversions in GA4.
Why are my marketing tags not firing
Marketing tags often rely on consent states, data layer variables and specific sequencing rules. If consent is not granted or if the data layer is incomplete, these tags may not fire at all. Issues with auto tagging or redirects can also prevent marketing platforms from receiving the correct parameters.
Container structure and performance
How do I know if my Tag Manager setup is too complicated
A container becomes difficult to manage when it contains multiple tags performing similar jobs, outdated test tags, poorly named triggers or legacy scripts that were never removed. Complex containers are more prone to errors and conflicts that reduce data accuracy.
Why is Tag Manager slowing down my site
Slow performance can occur when multiple third party scripts load at the same time, when duplicate libraries are injected or when tags call external services without conditions. Cleaning up and sequencing tags correctly often improves overall site performance.
Why does Tag Manager show errors in the console
Console errors point to syntax problems in custom HTML tags, missing variables, blocked scripts or incorrect data layer references. Some errors are harmless, but many indicate underlying issues that affect the accuracy of your analytics.
Measurement accuracy and reliability
Why does incorrect Tag Manager setup cause GA4 issues
Nearly all GA4 issues can originate in Tag Manager. If tags fire in the wrong order, if parameters are missing or if scripts are blocked, GA4 receives incomplete or misleading data. This often results in inflated direct traffic, unassigned channels, missing events or inconsistent reporting.
Why do different platforms receive different data
When Tag Manager does not fire tags consistently across all pages, or when consent rules differ between tags, platforms such as GA4, Ads, Meta and LinkedIn receive different versions of the user journey. Aligning triggers and sequencing resolves these differences.
When should I get a Tag Manager audit
An audit is valuable when data looks inconsistent, when events go missing, when the site has recently been redesigned or when several people have added scripts over time. It is also recommended after CMS changes, consent tool updates or analytics migrations.
If you are seeing inconsistent data or uncertain tracking behaviour, an audit can help highlight what needs attention. You can learn more about our GA4 and Tag Manager audits and how they support reliable reporting.