AdLintBack to Check Reference
GTM·Google Tag Manager·warning

Trigger Conflicts

One or more tags in this container fire on multiple triggers of different types. For example, both a Page View trigger and a Custom Event trigger. The tag will fire on every match across all triggers, which can produce duplicate conversions or fires in contexts the tag was not designed for.

CL
By Christopher LandaverdeCreator of AdLint · ad-tech tracking specialistUpdated

Why It Matters

GTM evaluates each firing trigger independently. A tag attached to both a Page View and a Custom Event trigger fires every time either trigger matches. This is sometimes intentional (a GA4 Configuration tag firing on All Pages plus on a session-start custom event), but is more often a misconfiguration: someone added a trigger to "make sure" the tag fires and accidentally created a duplicate-fire path. The damage depends on the tag type. a configuration tag firing twice is harmless; a Google Ads conversion tag firing twice doubles the reported conversion. The check is strict. it flags any tag with mixed trigger types because the configuration intent cannot be inferred. But every flagged tag deserves a manual review.

How To Fix It

  1. In GTM, open each flagged tag and review the Firing Triggers list.
  2. Ask: was this tag intentionally configured to fire on multiple trigger types, or did the second trigger get added accidentally?
  3. If only one trigger is correct, remove the others.
  4. If multiple triggers are intentional (e.g. For a tag that must fire on initial page load and on subsequent route changes in a SPA), document the intent in the tag's Notes field and add a description that future audits can recognize.
  5. Use Preview mode to walk the most common user journeys (page load, form submit, navigation) and confirm the tag fires only the expected number of times per journey.

Example

Configuration
Tag: Google Ads. Purchase
Firing triggers:
  - Custom Event - purchase
  - Page View - /thank-you (legacy, not removed)
Fix: remove the Page View trigger; the custom event is the canonical signal.
For Your Client Report

GTM tags configured with firing triggers of conflicting types. Google's Tag Manager trigger documentation, every trigger that matches the page event causes the tag to fire, which can produce duplicate or contextually-incorrect fires when triggers of different types are combined unintentionally. Fix: audit each flagged tag, remove unintended triggers, and document multi-trigger configurations that are intentional. Source: support.google.com/tagmanager/answer/6106961.

Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.

References

  1. [1]Google Tag Manager. About triggers

Audit your own files for this check

AdLint runs this check (and 177 others) against your GTM, Google Ads, Meta, TikTok, LinkedIn, Pinterest, Twitter/X, and Snapchat exports. Everything stays in your browser. No uploads, no accounts.

Run a free audit