Adobe Analytics

What Is Adobe Analytics?

Adobe Analytics is Adobe's enterprise-grade web and customer analytics platform, used by large organizations to measure how visitors interact with their websites, mobile apps, and other digital channels. It is the analytics component of the broader Adobe Experience Cloud and is built for sophisticated, high-volume measurement: deep segmentation, custom variables, flexible reporting, and integration with the rest of Adobe's marketing suite. Where lighter tools aim to give any small business a quick overview of traffic, Adobe Analytics targets analysts and digital teams who need to model complex customer journeys and answer detailed business questions.

Adobe Analytics traces its lineage to Omniture and the SiteCatalyst product, which is why long-time practitioners still refer to many of its concepts, and its core tracking library, by Omniture-era names. Over the years Adobe folded it into the Experience Cloud and rebuilt the analysis experience around tools like Analysis Workspace, but the underlying data model of events, dimensions, and conversion variables has remained recognizable. That history matters for detection because the tracking code and variable names it uses on a page often still carry the original terminology.

The platform is a server-side data-collection and reporting system fed by client-side tags. A small JavaScript library on each page collects data about page views, clicks, and custom events, then sends "image requests" (tracking beacons) to Adobe's collection servers, where the data is processed into reports. Analysts then explore that data in Adobe's reporting interface, building segments, calculated metrics, and visualizations. It is not a website builder or a plugin in the WordPress sense; it is an instrumentation-and-analysis layer that an organization adds to digital properties it already runs.

A defining characteristic of Adobe Analytics is its flexibility, and with it, its complexity. The platform exposes a rich set of custom variables, traffic variables (often called props), conversion variables (eVars), and events, that analysts configure to match their specific business model. This configurability is what lets a global enterprise model a multi-step purchase funnel, a media company track article engagement, or a bank measure application completion. It also means Adobe Analytics implementations are typically planned and maintained by dedicated analytics teams rather than set up casually, which is part of why detecting it signals an organization with serious measurement needs.

It helps to place Adobe Analytics relative to the most familiar comparison, Google's analytics products. Google Analytics is free, ubiquitous, and approachable, which makes it the default for the vast majority of websites. Adobe Analytics is a paid, enterprise product chosen by organizations that need its depth, governance, and integration with the wider Adobe Experience Cloud. Finding Adobe Analytics on a site therefore tends to indicate a larger, more analytically mature organization than the typical Google Analytics deployment.

How Adobe Analytics Works

Adobe Analytics follows the familiar analytics pattern of client-side collection feeding server-side processing, but with an enterprise data model layered on top. On each page, a JavaScript tracking library, historically the file commonly known as s_code.js and later the AppMeasurement library, builds a tracking object and populates it with data about the current page and visitor. Modern implementations frequently load this library through a tag manager, most often Adobe's own Adobe Launch / Experience Platform Tags or, in many shops, Google Tag Manager.

When a tracked event occurs, a page view, a link click, a video play, the library assembles the configured variables and fires a beacon. Classically this took the form of an "image request" to an Adobe collection domain, an HTTP request for a tiny tracking pixel whose query string carries the data payload. The collection endpoints have historically lived on Adobe-owned domains such as those containing omtrdc.net and 2o7.net, and many enterprises also route collection through a first-party CNAME on their own domain to improve data quality and cookie longevity. The data in those beacons is then ingested, processed, and made available in reports.

The platform's analytical power comes from its data model. Props (traffic variables) capture values for traffic analysis, eVars (conversion variables) persist values to attribute conversions over time, and events record specific actions like purchases or sign-ups. Analysts define dozens of these to mirror their business. On top of the raw data, Analysis Workspace provides a flexible, drag-and-drop analysis canvas for building freeform tables, visualizations, fallout and flow analyses, and cohort reports, while segments and calculated metrics let teams slice the data in almost unlimited ways.

Adobe Analytics also integrates tightly with the rest of Adobe Experience Cloud, sharing audiences with Adobe Target for personalization, feeding data into the Adobe Experience Platform, and connecting with Adobe Audience Manager. This integration is a major reason enterprises standardize on it: the analytics data does not sit in isolation but powers testing, personalization, and audience activation across the marketing stack. Many large implementations also adopt the Experience Cloud ID service, which assigns a shared visitor identifier across Adobe products, another fingerprint that can appear on the page.

Because collection is driven by client-side tags that send beacons to identifiable Adobe domains, Adobe Analytics is detectable through the same network and source inspection used for other analytics tools, even though the heavy lifting of processing and reporting happens on Adobe's servers out of public view.

How to Tell if a Website Uses Adobe Analytics

Adobe Analytics leaves several recognizable fingerprints. StackOptic inspects these from the server side, and you can confirm the same signals manually with browser tools.

Tracking beacons to Adobe collection domains. The strongest signal is network traffic to Adobe Analytics collection endpoints, classically domains containing omtrdc.net (and historically 2o7.net). Watching the Network tab for image requests to these hosts as the page loads is a direct indicator, even when collection is partly proxied through a first-party domain.

The AppMeasurement library. Look for the AppMeasurement.js file (or the older s_code.js) in the page's loaded scripts. These are the canonical Adobe Analytics tracking libraries and are a strong tell when present.

JavaScript globals. Adobe Analytics implementations expose recognizable objects in the browser console, most notably the s object (the tracking object, often window.s) with properties and methods like s.t() and s.tl(), and frequently a s_account value identifying the report suite. The Experience Cloud ID service may expose a Visitor object as well.

Visitor ID and cookies. Implementations using the Experience Cloud ID service set identifiable cookies (such as an AMCV_ prefixed cookie), and legacy setups use an s_vi or s_cc cookie. These appear in the Application/Storage panel.

Method	What to do	What Adobe Analytics reveals
View Source	"View Page Source" and search the markup	References to AppMeasurement.js or s_code.js and inline s. configuration
DevTools Network	Open the Network tab and reload	Image-request beacons to omtrdc.net / 2o7.net collection domains
DevTools Console	Type s or window.s and inspect	The Adobe tracking object, plus a s_account report-suite value
DevTools Application	Inspect cookies	AMCV_ Experience Cloud ID cookies or legacy s_vi/s_cc cookies
Wappalyzer / BuiltWith	Run on the live page	Identifies "Adobe Analytics" under analytics

A fast console check is to type s_account or inspect window.s on a page you suspect uses Adobe Analytics; a returned report-suite ID is strong confirmation. Because Adobe Analytics is so often deployed through a tag manager, our guide on how to check if a website uses Google Tag Manager is a useful companion, as is the broader how to find out what analytics a website uses.

A few realities make Adobe Analytics trickier to detect than a default Google Analytics install. Enterprises frequently route collection through a first-party CNAME on their own domain, so the beacon may be sent to something like metrics.example.com rather than an obvious Adobe host, which masks the destination in the address but not the request pattern. Tag managers add another layer, since the tracking library is injected at runtime rather than hard-coded in the initial HTML, meaning a server-side fetch of the raw page might not show AppMeasurement.js even though the live page loads it. For these reasons, combining signals is essential: the s object and s_account value in the console, the AMCV_ cookie, and the beacon pattern together give a confident verdict even when any single clue is obscured. For the general approach to identifying a site's full toolset, see how to find out what technology a website uses.

Key Features

• Flexible data model. Props, eVars, and events let analysts model almost any business process or customer journey.
• Analysis Workspace. A drag-and-drop analysis canvas for freeform tables, visualizations, fallout, flow, and cohort analysis.
• Advanced segmentation. Build complex, reusable segments and apply them retroactively across reports.
• Calculated metrics. Define custom metrics from existing data without re-instrumenting the site.
• Experience Cloud integration. Shared audiences and IDs with Adobe Target, Audience Manager, and the Experience Platform.
• Real-time and high-volume processing. Designed for enterprise traffic levels and timely reporting.
• Data governance and APIs. Reporting APIs, data feeds, and controls suited to large, regulated organizations.

Pros and Cons

Pros

• Exceptional analytical depth and flexibility for sophisticated measurement.
• Tight integration with the broader Adobe Experience Cloud for testing and personalization.
• Powerful, interactive analysis through Analysis Workspace.
• Built for enterprise scale, governance, and data volume.

Cons

• A steep learning curve that typically requires dedicated analytics expertise.
• Significant cost, positioning it well above free or low-cost tools.
• Implementation and maintenance are more involved than simpler analytics tags.
• Overkill for small sites that do not need its configurability.

Adobe Analytics vs Alternatives

Adobe Analytics competes with both Google's analytics products and other enterprise and product-analytics tools. The table clarifies where it fits.

Tool	Tier	Strength	Best for
Adobe Analytics	Enterprise (paid)	Deep, flexible analysis and Adobe integration	Large analytically mature organizations
Google Analytics 4	Free / paid (360)	Ubiquity and Google ecosystem	The broad majority of websites
Mixpanel	Paid	Event-based product analytics	Product teams measuring in-app behavior
Amplitude	Paid	Behavioral and product analytics	Digital products and growth teams
Matomo	Open source / paid	Data ownership and privacy	Privacy-conscious and self-hosting teams

If you find a site uses something other than Adobe Analytics, the same detection signals identify it. Compare Adobe Analytics with the near-universal Google Analytics or the event-focused Mixpanel to understand the trade-offs in depth, cost, and ease of use.

Use Cases

Adobe Analytics is the default choice for large enterprises whose measurement needs exceed what free tools comfortably handle. Major retailers use it to analyze complex purchase funnels, segment customers, and feed personalization. Media and publishing companies use it to measure content engagement and subscription behavior at scale. Financial-services firms use it to track multi-step application flows under governance requirements.

It also fits organizations already invested in the Adobe Experience Cloud, who gain from shared audiences across analytics, testing, and audience management; global brands needing consistent, governed measurement across many properties; and digital teams with dedicated analysts who can exploit its flexibility. For technology and competitive research, the presence of Adobe Analytics is itself a meaningful signal about an organization's scale and maturity.

Picture a few representative adopters. A multinational retailer might use Analysis Workspace to compare conversion across regions, build segments for high-value customers, and push those audiences to Adobe Target for on-site personalization. A subscription news publisher might instrument article reads, paywall encounters, and sign-ups as Adobe events, then analyze which content drives subscriptions. A bank might track each stage of a loan application as a fallout report to find where applicants drop off. The common thread is complexity: business processes intricate enough that the configurability of Adobe Analytics pays for its overhead.

From a technographic and sales-intelligence perspective, detecting Adobe Analytics is a strong qualifier. It typically indicates a large organization with a serious analytics function and budget, and often signals broader Adobe Experience Cloud adoption. For vendors selling enterprise marketing, analytics, or data tooling, that profile is high-value; for analysts mapping a market, it distinguishes enterprise players from the long tail of sites on free analytics. Our guide on what is technographics and using tech stack data to qualify leads shows how to turn that signal into account prioritization.

Frequently Asked Questions

What is the difference between Adobe Analytics and Google Analytics?

Google Analytics is free, widely adopted, and approachable, making it the default for most websites, while Adobe Analytics is a paid, enterprise platform built for deep, flexible measurement and tight integration with the Adobe Experience Cloud. Adobe Analytics offers more configurable data modeling (props, eVars, events) and powerful analysis tools, at the cost of greater complexity and price. The choice usually comes down to organizational scale and analytical sophistication.

How can I tell if a site uses Adobe Analytics?

Open DevTools and watch the Network tab for tracking beacons to Adobe collection domains containing omtrdc.net (or historically 2o7.net), look for AppMeasurement.js or s_code.js in the loaded scripts, and type s or s_account in the console to inspect the Adobe tracking object and report-suite ID. An AMCV_ cookie from the Experience Cloud ID service is another tell. Wappalyzer, BuiltWith, and StackOptic also identify it automatically.

Why is Adobe Analytics sometimes hard to detect?

Enterprises often route data collection through a first-party CNAME on their own domain, so beacons go to a host like metrics.example.com rather than an obvious Adobe domain. Adobe Analytics is also frequently loaded through a tag manager, so the tracking library is injected at runtime and may not appear in a raw server-side fetch of the HTML. Combining several signals, the console s object, cookies, and the beacon pattern, gives a reliable result despite this obfuscation.

What are props and eVars in Adobe Analytics?

Props (traffic variables) and eVars (conversion variables) are Adobe Analytics' configurable custom dimensions. Props capture values for traffic analysis within the same hit, while eVars persist values over time so conversions can be attributed back to earlier interactions. Combined with custom events, they let analysts model their specific business, which is the source of Adobe Analytics' flexibility and a reason implementations are planned by dedicated teams.

Is Adobe Analytics the same as Omniture?

Adobe Analytics evolved from the Omniture SiteCatalyst product after Adobe acquired Omniture, which is why practitioners still use Omniture-era terminology and why the legacy tracking file was known as s_code.js. Adobe rebuilt the analysis experience around Analysis Workspace and folded the product into the Experience Cloud, but the underlying model of events, props, and eVars remains recognizable, and some collection domains still reflect that heritage.

Curious which analytics, tags, and other tools a given site runs? Analyze any URL with StackOptic at https://stackoptic.com.