← All guides

GTM tag firing on all pages? Scope it before it inflates your data

Last updated 17 September 2026 · 3 min read

When an event or conversion tag in Google Tag Manager fires on an "All Pages" trigger, it runs on every page load — not just where the event actually happens — inflating events and conversions and polluting your GA4 data. Scope the trigger to the specific action or page instead. Here's how to spot it and fix it.

This one is easy to miss because the tag works — it just works everywhere, which for an event tag is the whole problem.

What this finding means

The All Pages trigger (and the Initialization and Consent Initialization triggers) is the right choice for tags that must load on every page — the GA4 configuration tag, consent setup. It's the wrong choice for event and conversion tags, which should fire on a specific action: a click, a form submission, a purchase confirmation. A conversion tag left on All Pages records a conversion on every single page view.

Why it matters

Over-broad firing inflates your event and conversion counts, which feeds wrong optimization signals to Google Ads and Meta — their bidding algorithms then optimise toward noise. It also distorts GA4 reports, so key events stop meaning what you think they mean. The data looks healthy at a glance and is quietly wrong.

How to fix it

1. Find event and conversion tags on All Pages

Filter your tags and note any GA4 event, Google Ads conversion, or pixel event tag whose firing trigger is All Pages, Initialization, or Consent Initialization.

2. Identify the real firing condition

Decide what should actually trigger the tag — a specific click, a form submission, a page path, or a custom dataLayer event.

3. Replace it with a scoped trigger

Swap All Pages for a trigger that matches that condition, using conditions such as Page Path, Click Element, or a custom event to narrow it to the right moment.

4. Test in Preview

Walk the journey in GTM Preview and confirm the tag now fires only on the intended action, and only once.

Key takeaways

  • All Pages is for tags that must load everywhere — configuration and consent — not events or conversions.
  • An event or conversion tag on All Pages counts on every page view, inflating your data.
  • Scope each event tag to the specific action or page that should fire it.
  • Verify in GTM Preview that it fires only where intended.

Frequently asked questions

Want to catch over-broad triggers automatically? Run a free check

Start free assessment