Debug Adobe Analytics in Chrome DevTools

What Adobe Analytics traffic looks like

Every Adobe Analytics hit contains /b/ss/ followed by the report suite ID. The host varies by setup age, the path does not.

Endpoint pattern

/b/ss/<rsid>/ on legacy .2o7.net domains, standard .sc.omtrdc.net endpoints, or a first-party CNAME typically starting smetrics. or metrics. on the site's own domain; a comma-separated RSID list means multi-suite tagging. The library loads as AppMeasurement.js (legacy: s_code.js)

Key parameters

pageName / g (page URL) / ch (site section) page context · events comma-separated event list (event1, purchase, scAdd…) · v1…vN eVars and c1…cN props: the custom dimensions where most implementation bugs live

Link tracking

pe/pev2 on s.tl() calls: pe=lnk_o custom link, lnk_d download, lnk_e exit link; no pe means a full page view (s.t())

E-commerce

products: the semicolon-delimited product string (category;name;quantity;price;events;merch eVars), a format compact enough that off-by-one field errors are routine

Debugging Adobe Analytics with Event Watcher

• Matches all the collection variants, including smetrics. CNAME setups that hide behind the first-party domain.
• The Adobe parser labels each hit as Page View, Custom Link, Download, or Exit Link.
• eVars and props decode into a Custom Data table, and the products string unpacks into per-product rows. A malformed merchandising eVar shows as a misaligned field instead of unreadable semicolon soup.
• Session and visitor IDs, plus cookies set and sent, appear alongside.

Adobe Analytics and consent

The extension checks Adobe Analytics against analytics consent. AppMeasurement has no Google Consent Mode equivalent. Whether a hit fires pre-consent depends entirely on how the implementation (usually Adobe Launch rules or Tags) gates the library.

A common failure: the page-view beacon fires at document_ready while the CMP is still open. Event Watcher marks it pre-consent. First-party smetrics. collection changes only the cookie's party, not the consent picture.

Common debugging scenarios

• An eVar is empty in reports. Find the hit, open Custom Data, and check whether vN was ever on the wire, or was sent on the wrong hit type (link call instead of page view).
• Revenue mismatch. Inspect the parsed products string field by field; a missing semicolon shifts price into the quantity slot silently.
• Double page views. Filter to Adobe Analytics and look for two /b/ss/ hits without pe, then compare their pageName values.
• Which suite is this firing to? Read the report suite ID straight out of the /b/ss/<rsid>/ path. Multi-suite tagging shows as a comma-separated list.
• Beacon fires before the banner is answered. The consent badge shows pre-consent; use the pixel audit workflow to see whether other tags share the same trigger.