Skip to content

Guide 117 · Container · GA4 + Tag Manager

Tag sequencing and firing priority: the order tags fire in, under your control

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

Tags fire asynchronously, which means the order two tags fire in is not guaranteed unless you set it. Tag Manager gives you two controls, and they do different jobs. Firing priority is a number on a tag: tags with higher values fire before those with lower values, and the priority defaults to 0. Tag sequencing is stronger: it names one tag to fire immediately before the primary tag — a setup tag — or immediately after it — a cleanup tag. Google's prioritization page gives the priority rule and points to sequencing for precise control, and the sequencing page says the setup tag fires before the primary tag and the cleanup tag fires immediately after. The worked example orders three tags with priorities 10, 5 and 0, then chains two of them with sequencing.

Expected signal

After step 4, Preview mode shows the three tags firing in priority order — 10, then 5, then 0 — and the sequenced pair firing setup first, primary second, every time, on every page load.

Download the container fragment: the sequencing and priority fragment (JSON) (export format version 2, 1892 bytes, MD5 c745cef212f58731986030b770fee552). It holds three tags with priorities 10, 5 and 0, with the conversion tag sequenced after the setup tag and set not to fire if the setup tag fails. The file is a hand-built import template, validated structurally — it was not exported from a live container.

What you need

  • Three tags that must fire in an order. The worked example is the Google tag, a consent setup tag and a conversion tag. When any of them can fire in any order, neither control is needed.
  • A reason the order matters. The worked example's conversion tag reads a value the setup tag writes to the data layer. If the conversion tag fires first, it reads the old value or nothing.
  • Edit access to the container. Priority and sequencing are tag settings, and changing them is a container edit.

The trace

  1. Open the first tag and expand Advanced Settings. Both controls live in Advanced Settings on the tag configuration page: Tag Firing Priority near the top, and Tag Sequencing below it.
  2. Set the priorities: 10, 5 and 0. Give the setup tag a priority of 10, the Google tag a priority of 5, and leave the conversion tag at the default of 0. Google's rule is that a priority 3 tag fires before a priority 1 or 2 tag, so 10 fires before 5, and 5 before 0. The three tags sort as 10, then 5, then 0 — a strict order with 10 − 5 = 5 and 5 − 0 = 5 between each step.
  3. Sequence the conversion tag after the setup tag. Open the conversion tag, go to Advanced Settings, then Tag Sequencing, and check Fire a setup tag before this tag fires. Pick the setup tag. The conversion tag now ignores its own triggers and fires as part of the sequence instead — after the setup tag finishes.
  4. Choose whether a failed setup tag blocks the primary tag. With the setup tag picked, the checkbox Don't fire this tag if the setup tag fails or is paused decides the failure mode. Check it when the primary tag's data depends on the setup tag — a conversion tag that reads a value the setup tag writes must not fire on the old value.

Dead ends

DEAD END — PRIORITY IS NOT A SEQUENCE. A priority of 10 fires before a priority of 0, but both still fire asynchronously — the 0 tag is not guaranteed to wait for the 10 tag to finish. Priority orders the start, not the completion. When one tag must finish before another starts, that is sequencing, not priority.

DEAD END — A SEQUENCED TAG THAT STILL HAS ITS OWN TRIGGER. When a tag is fired as part of a sequence, it ignores its own triggers. A sequenced tag with a trigger that looks right can mislead: the trigger is not what fires the tag any more. The sequence is.

DEAD END — SEQUENCING A PAUSED SETUP TAG. A paused setup tag fires nothing, and a primary tag that depends on it either fires on stale data or does not fire at all, depending on the checkbox in step 4. Pausing a setup tag pauses everything chained behind it.

End state

Three tags with priorities 10, 5 and 0, and a conversion tag sequenced after its setup tag. The order is now set on purpose instead of left to the browser, and the failure mode — what happens when the setup tag fails — is a choice, not an accident.

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 1892 bytes (1.85 KB, 0.92% of the reported 200 KB container size limit), MD5 c745cef212f58731986030b770fee552, and passed 20 structural checks.