Technical fix guide
GTM Tag Conflict Detection
Connected GTM data reveals potential tag conflicts: multiple tags firing on the same trigger, race conditions, or deprecated tags.
Issue ID: ANALYTICS-GTM-CONFLICTS-001
Severity: moderate
Impact: Med
Effort: M
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
Connected GTM data reveals potential tag conflicts: multiple tags firing on the same trigger, race conditions, or deprecated tags.
Why it matters
Connected GTM data reveals potential tag conflicts: multiple tags firing on the same trigger, race conditions, or deprecated tags. This affects crawlability, rendering, and whether the site can be interpreted correctly by search engines.
How we detect it
- FreeSiteAudit flags this issue when the rule for ANALYTICS-GTM-CONFLICTS-001 fails and the page evidence points to Dom body.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Review tags firing on the same triggers for conflicts
- 2Use tag sequencing for dependent tags
- 3Remove deprecated or unused tags
How to re-check it
- No conflicting tags fire on the same trigger without sequencing
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.