GTM Tag Sequencing vs. Firing Priority: What Each Setting Controls

Tag sequencing and firing priority both affect when tags run, but they address different situations. Sequencing expresses a dependency between tags; firing priority influences the order of tags that are eligible on the same event. Neither setting guarantees that a remote request has finished successfully before another tag proceeds.

Use sequencing for dependencies

Sequencing is useful when one tag must run before or after another as part of a defined implementation. A setup tag can initialize a vendor library before a dependent tag runs, while a cleanup tag can run after the main tag’s action. The dependency should be documented and tested because failure behavior can affect the rest of the chain.

If two tags merely need to listen to the same page event, sequencing may add unnecessary coupling. Keep tags independent unless there is a real ordering requirement.

Use priority to influence same-event order

Firing priority can influence which eligible tag is evaluated first when several are triggered by the same event. It does not create a trigger, prove that an earlier tag completed a network request, or replace a setup dependency. High priority should be used sparingly and with a clear reason.

Where actual completion matters, design an explicit event or callback rather than assuming that a numeric priority guarantees a vendor response.

• Write down why the ordering is required.
• Test success and failure paths in Preview.
• Check consent rules and tag sequencing together.

Keep the container understandable

A container with many priority overrides or tag chains is difficult to maintain. Prefer a small number of documented dependencies and verify that unrelated tags still fire. After publication, review the sequence on the live site and check the destination platform’s diagnostics.

Related guides

• GTM Page View vs. DOM Ready vs. Window Loaded Triggers
• GTM Consent Initialization: Set Consent Defaults Before Tags Run