Adobe Analytics
Adobe Analytics is an enterprise web and app analytics platform within Adobe Experience Cloud. It models data through report suites, dimensions, and metrics, and supports flexible segmentation, calculated metrics, and analysis workspaces. It is typically deployed in larger organizations with dedicated implementation, and it integrates with the wider Adobe marketing stack.
What this means
Adobe Analytics structures data into report suites containing dimensions and metrics, with custom variables (often called eVars and props historically) and events mapped during implementation. Analysts build segments and calculated metrics and explore data in workspace-style interfaces.
The flexibility is considerable, which is why implementation and a solution design reference are central to getting consistent numbers.
What to weigh
The platform suits organizations that need granular, configurable measurement and integration across the Adobe stack, and that can resource implementation and governance. That power also means more setup and maintenance than a lightweight tool.
- Report suites, dimensions, metrics, custom variables
- Strong segmentation and calculated metrics
- Enterprise-oriented; implementation-heavy
Migration notes
Migrating to or from Adobe Analytics requires mapping its variable model to another tool's events and parameters — they are not interchangeable. Document the report-suite and variable definitions first, since the same label can mean different things across implementations.
How it appears in analytics and logs
Adobe Analytics numbers depend on report-suite configuration and variable mapping; discrepancies versus another tool usually trace to implementation choices rather than the platform under-counting.
Diagnostic use case
Consider Adobe Analytics in enterprise contexts that need deep segmentation, custom variables, and integration with the broader Adobe Experience Cloud.
What WebmasterID can help detect
WebmasterID is a lightweight first-party alternative for the AI-search era; this page describes Adobe Analytics even-handedly so an enterprise comparison or migration is informed.
Common mistakes
- Comparing numbers across report suites with different configurations.
- Assuming variable definitions are standard rather than implementation-specific.
- Underestimating the implementation and governance effort.
Privacy and accuracy notes
Adobe Analytics is a third-party enterprise platform that can collect detailed visitor data; consent, identifiers, and data-transfer questions apply and vary by region and configuration. This is factual, not legal advice.
Related pages
- Google Analytics 4: the event-based model
Google Analytics 4 (GA4) replaced Universal Analytics with a fully event-based model: everything, including pageviews, is an event with parameters. It introduced engagement-based metrics, cross-platform measurement, and a different relationship with sampling and data retention. It is free and widely used, with consent and data-transfer considerations that depend on your region.
- Enterprise vs lightweight analytics
Analytics tools span from heavyweight, highly configurable enterprise platforms to small, focused lightweight tools. Enterprise tools offer deep segmentation, custom variables, and integrations at the cost of implementation and governance effort; lightweight tools offer a clean, small-footprint overview with less depth. The right tier depends on the questions you must answer and the resources you can commit.
- Source / medium: the core traffic-origin dimension
Source/medium is the dimension that records where a visit came from (the source, e.g. google) and how it arrived (the medium, e.g. organic). It is derived from the referrer and UTM parameters, with rules that vary by tool. The big caveat: when neither is available, the visit lands in 'direct / (none)', which is a catch-all, not a channel.
- Compare: Google Analytics
How WebmasterID differs from GA.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.