How to Tell If a Website Uses Adobe Analytics

Adobe Analytics — known for years as Omniture SiteCatalyst — is the enterprise measurement platform behind a large share of the world's biggest retail, media and finance sites. Detecting it can be confusing because it is usually deployed through Adobe's tag manager, but it leaves an unmistakable signature: an image beacon to a /b/ss/ path on an Adobe collection domain. Here is the full detection guide, the implementation pattern that hides it, and why the find is so valuable.

What is Adobe Analytics?

Adobe Analytics is the analytics product within the Adobe Experience Cloud. It is a licensed, enterprise platform built for deep segmentation, custom variables (eVars and props), report suites, and integration with Adobe Target, Audience Manager and the wider Experience Cloud. It is the opposite of a copy-paste free tag — implementing it properly takes a dedicated analytics team and a solution design reference document.

That is exactly why detecting it matters: Adobe Analytics is a reliable proxy for a large, well-funded organisation with serious measurement requirements. You will rarely find it on a small business site; you will very often find it on a bank, an airline, a national retailer or a major publisher.

How Adobe Analytics loads and sends data

In a modern deployment, the page loads Adobe Experience Platform Launch (Adobe's tag manager, the successor to DTM) from assets.adobedtm.com. Launch then injects the AppMeasurement.js library, which creates the global tracking object conventionally named s. A page view is sent with s.t() and a link or custom event with s.tl().

The hit itself is an image beacon: a request to a path like /b/ss/<report-suite-id>/1/..., sent to an Adobe collection domain. That domain is usually *.sc.omtrdc.net (or the legacy *.2o7.net), but large advertisers frequently use a first-party CNAME such as metrics.brand.com or smetrics.brand.com to keep the request first-party. Identity is provided by the Experience Cloud ID service, which sets AMCV_<org>@AdobeOrg cookies. Knowing this indirection — tag manager, then library, then /b/ss/ beacon — is the key to reliable detection.

How to tell if a website uses Adobe Analytics

1. Check the Network tab — the definitive method. Reload with developer tools open and filter for b/ss or omtrdc. Adobe Analytics records hits as requests to a path like /b/ss/<report-suite-id>/1/..., almost always on *.sc.omtrdc.net, the legacy *.2o7.net, or a first-party metrics.<domain> / smetrics.<domain> CNAME. That beacon is conclusive.

2. View the page source. Search for AppMeasurement, s_code, s_gi or omtrdc. You may find AppMeasurement.js loaded directly, but more often you will see Adobe Launch (or the older DTM) loading from assets.adobedtm.com, which then injects AppMeasurement at runtime.

3. Use the console. Type s and press Enter. Adobe's tracking object exposes methods s.t() (page view) and s.tl() (link tracking), plus properties like s.account (the report suite ID). The function s_gi (get instance) is another tell.

4. Inspect cookies. Look for AMCV_<org>@AdobeOrg and AMCVS_ (the Experience Cloud ID service), along with s_cc, s_sq and the older s_vi/s_fid.

What the Adobe Analytics signals look like

A hit in the Network tab:

GET https://example.sc.omtrdc.net/b/ss/exampleprod1/1/JS-2.22.0/s12345?AQB=1&pageName=Home&...

Cookies in the Application panel:

AMCV_1234567890ABCDEF%40AdobeOrg = MCMID|...
s_cc = true

The combination of the /b/ss/ beacon, the s object and the AMCV_ cookie is uniquely Adobe.

Adobe Analytics versus similar tools — avoiding false positives

The biggest gotcha is the indirection: because Adobe Analytics is usually injected by Launch/DTM, the static HTML may show only an assets.adobedtm.com script, and the AppMeasurement library and /b/ss/ beacon appear only after the tag manager runs — so always check the live page. First-party CNAME collection domains (metrics.brand.com) can disguise the omtrdc.net host, so rely on the /b/ss/ path pattern and the s object rather than the hostname alone. And do not confuse Adobe Analytics with Adobe Target (which uses mbox/at.js and tt.omtrdc.net) or Adobe Audience Manager (demdex.net) — they are sibling products in the same suite and frequently appear together, but they are distinct.

Why it is worth knowing a site uses Adobe Analytics

For enterprise sales, Adobe Analytics is one of the most valuable qualifying signals available: it tells you the account has budget, a measurement team and likely the wider Adobe Experience Cloud — Target, AEM, Audience Manager — which you can infer and sell around. For agencies and consultancies, it flags clients who need specialist implementation, tagging or migration help, a high-value service line. For competitive analysis, the report-suite ID in the beacon can even hint at how a company structures and segments its properties. And for recruiters and analysts mapping a market, the presence of Adobe versus Google Analytics 360 is a useful way to segment enterprises by their analytics philosophy.

How reliable is each Adobe Analytics signal?

Because Adobe is almost always tag-manager-injected, signal weighting matters. The /b/ss/<report-suite>/ beacon is definitive wherever it is sent — including to first-party metrics.brand.com CNAMEs — because that path pattern is unique to Adobe Analytics. The AMCV_/AMCVS_ cookies are close behind, set by the Experience Cloud ID service. The s object with s.t()/s.tl() and the s_gi function are strong, though confirm s.account (the report suite) to be sure. An assets.adobedtm.com script alone proves only that Adobe Launch is present — not that Adobe Analytics specifically is running, since Launch can deploy other Adobe products — so always trace through to the /b/ss/ beacon.

What an Adobe Analytics install reveals about an organisation

Adobe Analytics is licensed enterprise software, so its presence is among the strongest "large, well-funded account" signals you can find on the open web. It rarely appears outside enterprise retail, media, finance, travel and large B2B. Crucially, it almost never travels alone: Adobe Analytics is the centre of the Experience Cloud, so finding it should prompt you to check for Adobe Target (mbox/at.js, tt.omtrdc.net), Audience Manager (demdex.net) and Adobe Experience Manager as the CMS. Each additional Adobe product you confirm raises the estimated contract value and the likelihood of a dedicated digital-experience team.

The report-suite ID embedded in the /b/ss/ path is a bonus intelligence asset: multiple suites across a company's properties hint at how it segments brands or regions, while a single global suite suggests centralised governance. For enterprise sellers, an Adobe stack tells you the buying process will involve procurement and a measurement team, and that competing free tools will not be a serious objection. For agencies, it flags specialist implementation and migration work — a high-value, sticky service line.

A quick Adobe Analytics detection checklist

• Filter the Network tab for b/ss or omtrdc; a /b/ss/<suite>/ beacon is conclusive.
• Search the source for AppMeasurement, s_gi, s_code or assets.adobedtm.com.
• Type s in the console; check for s.t(), s.tl() and s.account.
• Check cookies for AMCV_/AMCVS_, plus s_cc and s_sq.
• Look for sibling Adobe products (Target, Audience Manager, AEM) to size the account.
• Don't treat an adobedtm.com script as proof of Adobe Analytics specifically.

Adobe Analytics in a modern enterprise stack

Adobe Analytics is rarely a standalone purchase; it is the measurement core of the Adobe Experience Cloud, so detecting it reframes the whole account. Expect to find it alongside some combination of Adobe Target (testing and personalisation), Audience Manager (the DMP), Adobe Experience Manager (the enterprise CMS), Adobe Launch (the tag manager that injects it), and Real-Time CDP. Each sibling product you confirm raises the estimated contract value and signals a larger digital-experience organisation behind the site.

There is a generational shift worth noting, too. Adobe is steering customers from classic Adobe Analytics toward the Adobe Experience Platform and Customer Journey Analytics, with the Web SDK (alloy.js, sending to an *.edge.adobedc.net endpoint) replacing the classic AppMeasurement /b/ss/ beacon. So on some enterprise sites you will see the Web SDK pattern instead of, or alongside, the classic one — recognising both keeps your detection current. Either way, the implementation is heavyweight and team-owned.

For an auditor, capture the report-suite ID(s) from the /b/ss/ path or the datastream ID from the Web SDK, whether classic AppMeasurement or alloy.js is in use, and which sibling Adobe products appear. Those details size the account and reveal where it sits on Adobe's migration path — exactly the context an enterprise seller or a specialist implementation agency needs before a conversation.

Detecting Adobe Analytics at scale

For one site, the Network-tab check is quick. For a portfolio of enterprise domains, automate it. StackOptic detects Adobe Analytics and the surrounding Experience Cloud tools from a real browser, including tag-manager-injected deployments behind first-party CNAMEs. For more, see how to find out what analytics a website uses and our Adobe Analytics profile.