Debug Tealium Collect in Chrome DevTools

What Tealium Collect traffic looks like

Tealium Collect is the beacon that ships the client-side data layer to Tealium's server side: EventStream, AudienceStream, and DataAccess.

Endpoint pattern

collect.tealiumiq.com or a regional variant like collect-eu-1.tealiumiq.com, most commonly a POST to /event, or the legacy image form /vdata/i.gif with account and profile in the path

First-party variants

Sites running first-party CNAMEs produce the same /i.gif path shape on their own domain

Transport

POST using the multipart form encoding of the Tealium Collect tag (template ID 20010 in iQ), or the legacy GET image request

Key parameters

tealium_event event name · tealium_account / tealium_profile / tealium_visitor_id routing identity · every data layer variable the site set at send time

Payload

A flattened dump of utag_data, plus utag.js system keys added automatically: cp.* cookie values (including CMP consent cookies) · dom.* page context · ut.* library internals

Debugging Tealium Collect with Event Watcher

• The Tealium parser decodes the Collect payload, including the multipart form encoding the tag uses for POSTs.
• Your data layer variables are grouped apart from the auto-injected cp.* / dom.* / ut.* system keys. Review what the site actually sent without scrolling past infrastructure noise.
• Events are named from tealium_event; the detail view breaks out account/profile routing, the visitor ID, session state, and consent-relevant values found in the payload.
• Because Collect carries the whole data layer, this is often the fastest answer to "what exactly does AudienceStream receive for this event?"

Tealium Collect and consent

Event Watcher checks Collect against analytics consent. Collect is the on-ramp to server-side distribution, so one pre-consent beacon can fan out to many downstream connectors leaving no client-side evidence. A violation outweighs one on a single pixel.

Tealium's own Consent Manager state travels in the payload via cp.* consent cookies, so you can verify recorded values against the CMP. A Collect hit before the CMP resolves is marked pre-consent. Check the tag's load-rule gating in iQ.

Common debugging scenarios

• AudienceStream attributes are wrong. Open the Collect event for the page and read the decoded data layer. If the variable is wrong at the beacon, fix the site or iQ extension, not the server-side mapping.
• Collect fires before the consent banner. Check the first Collect event's consent state; an ungated Collect tag is a common iQ misconfiguration.
• Visitor stitching breaks across pages. Compare tealium_visitor_id across captured events. A changing ID points at cookie problems on the first-party domain.
• Regional endpoint surprises. A collect-eu-1 hostname confirms (or refutes) an EU data-residency requirement without opening iQ.
• Duplicate events server-side. Group by Event Name and check whether two Collect beacons fire per tealium_event, typically the tag firing on both the view and a link event.