Debug Adobe Tags (Launch) in Chrome DevTools

What Adobe Tags traffic looks like

An Adobe Tags (formerly Launch) property ships as one compiled library, and the filename alone tells you the build environment.

Endpoint pattern

assets.adobedtm.com, filename shaped launch-<hash>.min.js; non-production builds carry a suffix (launch-<hash>-development.min.js or -staging.min.js), so spotting a -development build on a live page is a finding in itself. Larger properties pull additional chunks from the same path as rules and extensions load on demand

Transport

Script loads only: the library is a build artifact of the property's rules and extensions, exposed at runtime as the _satellite global (_satellite.track() is the common custom-event entry point)

Payload

Little of its own: the traffic it orchestrates (Adobe Analytics /b/ss/ beacons, AEP Web SDK calls to edge.adobedc.net, Target requests, third-party pixels) shows up attributed to those platforms

Debugging Adobe Tags with Event Watcher

• The library load appears in the stream named and categorized as Adobe Tags, with the request URL and its parsed components, enough to read the build environment straight off the filename.
• The Script Tree view shows the launch library as the parent of everything it injected: Adobe's own SDKs and any third-party tags deployed through rules, each with the events it sent.
• That parent-child mapping is the practical answer to "is this pixel hardcoded or deployed through Tags."

Adobe Tags and consent

Tag-management infrastructure: Event Watcher assigns it no consent category. In the Adobe stack, consent enforcement typically lives in the property's configuration: a CMP extension or custom rule conditions gate rule execution.

The AEP Web SDK carries its own consent handling downstream.

What the extension checks is the traffic Tags actually fires: each Adobe Analytics beacon, Web SDK call, or third-party pixel is marked granted, denied, or pre-consent.

A rule firing marketing tags before the CMP records a choice surfaces in the stream.

Common debugging scenarios

• Staging build on production. Check the loaded filename for a -development or -staging suffix: the single most common Tags misdeployment, and visible without opening the Adobe interface.
• Unknown pixel provenance. Walk the Script Tree from the launch library down: if the pixel's loader chain starts at launch-*.min.js, a rule deployed it; if not, it is hardcoded or came from another script.
• Double collection during a Web SDK migration. Properties mid-migration often fire both legacy /b/ss/ beacons and edge.adobedc.net calls for the same interaction. The Grouped view pivoted by Event Name or Endpoint exposes the duplication.
• Rule fires before consent. Find the downstream event marked pre-consent, then use its script badge to trace which Tags-injected script produced it.
• Full inventory of what a property loads. Useful before a cleanup or audit. See auditing all tracking pixels.