Debug Tealium iQ in Chrome DevTools

What Tealium iQ traffic looks like

Tealium iQ announces itself in its URLs: the utag.js path carries account, profile, and environment, so the path itself is diagnostic.

Endpoint pattern

tags.tiqcdn.com/utag/{account}/{profile}/{environment}/utag.js, plus utag.sync.js loaded synchronously in the head for pre-DOM tags (typically A/B testing), and numbered tag files like utag.14.js / utag.47.js (one per tag template, the number being the tag's UID inside iQ); hits to collect.tealiumiq.com are not iQ: that is Tealium Collect, classified separately

Transport

Script loads only: the tags iQ fires then send their own vendor traffic under their own platform names

Key parameters

path segments: account / profile identify the iQ workspace · environment (prod, qa, dev, or custom) tells you which publish target is actually serving the page

Data layer object

Data flows in through the utag_data page object and utag.view() / utag.link() calls

Debugging Tealium iQ with Event Watcher

• Every utag* load appears in the stream named and categorized as Tealium iQ, with account, profile, and environment readable per file from the parsed URL.
• The Script Tree view maps utag.js to the numbered tag files it loaded, and from each of those to the vendor scripts and hits they produced.
• That mapping is how you translate an opaque utag.47.js into "the tag that loaded this pixel and sent these events."

Tealium iQ and consent

As tag-management infrastructure, iQ carries no consent category itself. It is a relay that decides which tags load based on consent, whether that comes from Tealium's own Consent Manager or a third-party CMP wired into load rules.

Enforcement is simple: consent-gated tags should never load their utag.N.js until the category is granted. Event Watcher checks the vendor events iQ fires against CMP state, so an early marketing tag shows pre-consent and counts toward the violations counter.

Common debugging scenarios

• Wrong environment in production. The environment segment in the utag.js path says dev or qa on a live page: an unpublished or misconfigured deployment; one glance at the parsed URL settles it.
• Which vendor is utag.23.js? Follow it in the Script Tree: its children and the events it sent identify the vendor without opening the iQ interface.
• A consent-gated tag fires anyway. Find the vendor's events in the stream, check their consent verdict, then walk the Script Tree back to the numbered tag file that loaded pre-consent.
• iQ or Collect? Sites often run both; if the traffic you are chasing goes to collect.tealiumiq.com, you are debugging the Collect tag, not a client-side iQ tag.
• Flicker or pre-DOM logic misbehaving. Check whether utag.sync.js loaded at all, and what it loaded. Synchronous head tags are easy to lose during template or CSP changes.