Skip to main content
Vendor reference · Analytics

Adobe Analytics

Adobe's enterprise analytics product. Data is sent by the AppMeasurement library or by the Experience Platform Web SDK.

Adobe Analytics at a glance

Company
Adobe
Category
Analytics
Tag script
https://assets.adobedtm.com/<property-path>.js
Sends data to
<company>.data.adobedc.net *.omtrdc.net
JavaScript object
s alloy
Cookies
4 attributed to Adobe Analytics in the TagPipes Vendor Registry

The s and alloy objects and the data.adobedc.net tracking server are from Adobe's documentation. The assets.adobedtm.com tag host, the omtrdc.net hosts and the /b/ss/ request path are commonly found on sites using Adobe Analytics.

What Adobe Analytics is

Adobe Analytics is Adobe's enterprise web analytics product. Data is sent either by the older AppMeasurement library, which exposes an s object, or by the Experience Platform Web SDK, which exposes alloy and sends data to Adobe's Edge Network.

It identifies visitors with Experience Cloud ID cookies such as AMCV_<org-id>.

What marketers use it for

Enterprise marketing teams use it for traffic, campaign and conversion reporting with custom variables. It is usually deployed through Adobe Experience Platform tags.

How to recognize Adobe Analytics on a site

  1. Open the site in Chrome, open DevTools (F12, or Cmd+Option+I on a Mac) and go to the Network tab.
  2. Reload the page and type /b/ss/ into the filter box. AppMeasurement hits usually contain /b/ss/ followed by the report suite ID. Sites on the Web SDK send requests to an /interact path on their edge domain instead.
  3. In the Console tab, type window.s && s.version and press Enter. If it returns a version string, AppMeasurement is loaded. Sites on the Web SDK expose alloy instead.
  4. In Application, then Cookies, look for AMCVS_*, AMCV_*, s_cc, s_fid. Some cookies only appear after a consent choice or a specific action.

Cookies associated with Adobe Analytics

Attributed to Adobe Analytics by the TagPipes Vendor Registry: AMCVS_*, AMCV_*, s_cc, s_fid.

What TagPipes observed

0.48%

of sites scanned had Adobe Analytics detected

TagPipes scanned 41,162 public websites between August 11, 2026 and September 13, 2026, loading up to three pages per site in a real browser as a first-time visitor, and matched what loaded against the TagPipes Vendor Registry. That is how TagPipes recognizes Adobe Analytics: by the hosts its tag loads from and the cookies attributed to it.

Observed TagPipes scan data, not a figure published by Adobe. Websites of TagPipes customers are excluded and no individual site is named. Snapshot dated September 13, 2026.

Sources

What it is, what it is used for, and its scripts, hosts and JavaScript objects were checked against the vendor documentation above on . The detection rate is TagPipes scan data from September 13, 2026, not a value published by the vendor. Browse all vendors.

Know when a tag stops firing

TagPipes Auditor checks with real browsers that your marketing pixels fire with the right parameters, and alerts you when tracking breaks. Pulse checks how marketing tags behave against your consent banner.

See Auditor See Pulse

TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.