Skip to content

Guide 118 · Container · GA4 + Tag Manager

Add a tag exception: stop a tag firing on one page without touching the tag

Checked 11 November 2026 · Verification: container fragment validated structurally (14 checks, all passed) · Steps traced to Tag Manager Help, opened 11 November 2026 · 5-minute read

A tag on All Pages fires everywhere, and sometimes everywhere is one page too many: a survey tag that must not appear on checkout, a chat widget that must not load on the payment page. The fix is not a narrower firing trigger — it is an exception. Google's firing-triggers page defines it: a trigger exception, also known as a blocking trigger, is a kind of trigger that can be used to block another trigger's ability to fire under certain conditions. The tag keeps its firing trigger, and the exception carves out the page. The worked example carves the checkout page out of a site-wide tag on a 6-page site.

Expected signal

After step 3, Preview mode shows the tag under Tags Fired on the homepage and the other four pages, and under Tags Not Fired on the checkout page — 5 firings out of 6 page loads, with the one missing firing being exactly the page named in the exception.

Download the container fragment: the tag exception fragment (JSON) (export format version 2, 1230 bytes, MD5 c6850907a482a338204078da4dabb089). It holds a tag on All Pages with a blocking trigger for the checkout page, plus the exception trigger itself. The file is a hand-built import template, validated structurally — it was not exported from a live container.

What you need

  • A tag that fires too broadly. The worked example is a survey tag on All Pages. If the tag already fires narrowly, there is nothing to except.
  • The page or condition to carve out. The worked example is the checkout page, matched by Page Path. The exception is a trigger like any other, so it needs a condition.
  • Edit access to the container. Adding an exception is a tag edit.

The trace

  1. Build the exception trigger first. Go to Triggers, click New, and build a Page View trigger that fires on Some Page Views where Page Path equals /shop/checkout. Name it Exception - checkout page. A trigger used as an exception is still a trigger — it has an event type and a condition, and it can be reused as an exception on other tags.
  2. Open the tag and click Triggering. Open the survey tag, click Triggering at the bottom of the tag configuration, and find the Add Exception control next to the firing triggers.
  3. Add the exception trigger and save. Pick Exception - checkout page and save the tag. The tag now fires wherever All Pages says it should, except where the exception matches. On the worked 6-page site the arithmetic is 6 pages − 1 excepted page = 5 pages where the tag fires. A tag fires when any one of its firing triggers is met, and an exception blocks it when the exception's conditions are met — both at once means the exception wins.

Dead ends

DEAD END — AN EXCEPTION THAT MATCHES THE FIRING TRIGGER. An exception whose condition matches every page the firing trigger matches blocks the tag everywhere. The tag is not broken; the exception is just the firing trigger written again. Check the exception's condition before you save.

DEAD END — EXPECTING THE EXCEPTION TO FIRE THE TAG. An exception never fires a tag — it only blocks one. A tag with no firing trigger and one exception fires nowhere. The firing trigger is what starts the tag; the exception is what stops it.

DEAD END — FORGETTING THE EXCEPTION WHEN THE TAG IS COPIED. Exceptions travel with the tag when it is copied or exported, but a trigger used as an exception can be edited or deleted on its own. Deleting the exception trigger removes the block from every tag that used it, and the survey tag appears on checkout again.

End state

One tag on All Pages with one exception, firing on 5 of the 6 pages and silent on checkout. The tag's reach is now the firing trigger minus the exception, and the exception trigger can be reused on any other tag that must skip the same page.

Sources

Checked 11 November 2026. The click paths above are the ones in Google's help pages, opened 11 November 2026. No step in this guide was run inside a live Analytics property or a live Tag Manager container, because both need a Google sign-in and this site does not sign in as anyone. The container file was validated structurally instead: export format version 2, every tag's firing trigger resolves, every variable the tags reference exists in the file, and the tag types are the documented ones. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map. The container fragment for this guide is 1230 bytes (1.20 KB, 0.60% of the reported 200 KB container size limit), MD5 c6850907a482a338204078da4dabb089, and passed 14 structural checks.