AdLintBack to Check Reference
GTM·Google Tag Manager·warning

Excessive Tag Sequencing Depth

A tag in this container has a sequencing chain more than three setup tags deep. Tag A depends on B which depends on C which depends on D. At each link, GTM must wait for the upstream tag to complete before firing the next one, which serializes work that often does not need to be serial and can add hundreds of milliseconds to time-to-fire.

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

Why It Matters

Tag Sequencing serializes execution: GTM does not fire a tag until every declared setup tag has completed. Two or three levels is normal (Consent Mode → Conversion Linker → Conversion Tag), but five-deep chains are usually accidental. Someone added a setup-tag relationship that did not need to be a setup-tag relationship. The cost is page-load performance: every additional level adds the network or compute time of one more tag to the critical path. For conversion tags on confirmation pages where the page often closes immediately after fire, this directly correlates with conversion loss on slow connections. The threshold of 3 is informational guidance; the real test is whether each link in the chain is genuinely a prerequisite or just incidentally configured that way.

How To Fix It

  1. AdLint's details list the deepest tag chains. Walk each chain from leaf to root.
  2. For each setup-tag relationship, ask: does the downstream tag actually require the side effect of the upstream tag?
  3. Where the answer is no, remove the setup-tag declaration. The tags can fire in parallel.
  4. Where the answer is yes (Conversion Linker before Conversion Tag, GA4 Config before GA4 Event), keep the dependency.
  5. Republish and verify time-to-fire improves in Preview mode.

Example

Configuration
Chain depth: 5
  Tag E (depth 5) ← setup: Tag D
  Tag D (depth 4) ← setup: Tag C
  Tag C (depth 3) ← setup: Tag B
  Tag B (depth 2) ← setup: Tag A
  Tag A (depth 1)

Fix: review whether each level is a real prerequisite. Usually one or two are incidental.
For Your Client Report

GTM tag sequencing chains exceeding three levels of depth. Google's Tag Sequencing documentation, each setup-tag relationship serializes execution and adds the upstream tag's firing time to the downstream tag's critical path. Deep chains often contain incidental dependencies and degrade page-load performance, particularly on conversion-confirmation pages where rapid tag fire is essential to avoid loss. Fix: audit each chain link for true prerequisite status and remove incidental setup-tag relationships. Source: support.google.com/tagmanager/answer/6238868.

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

References

  1. [1]Google Tag Manager. Tag sequencing

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