Growth Notes

Adobe Experience Cloud

Tags: web-dev analytics platform

Adobe Experience Cloud

Checked: 2026-08-16

The brand covering Adobe’s enterprise marketing products. Most of them were separate companies Adobe bought, and the hard part isn’t any single product — it’s working out which ones share a foundation, which merely integrate, and which name is the current one.

§0 The one idea

Experience Cloud is a brand. Experience Platform is an architecture. They are not the same thing, and confusing them is the single biggest source of Adobe confusion.

EXPERIENCE CLOUD
  a marketing brand covering ~everything
  Adobe sells to enterprise marketers

EXPERIENCE PLATFORM (AEP)
  an actual shared foundation — one schema,
  one identity graph, one customer profile
  that only SOME of those products sit on

So the products divide in two, and this is the map worth carrying:

BUILT ON THE PLATFORM
  Real-Time CDP
  Journey Optimizer
  Customer Journey Analytics
     ↓ share data · identity · governance
┌──────────────────────────────────┐
│  ADOBE EXPERIENCE PLATFORM       │
│  XDM schemas · Identity Service  │
│  Real-Time Profile               │
│  Data Collection (Tags, Web SDK) │
└──────────────────────────────────┘

INTEGRATE WITH IT, PREDATE IT
  Analytics · Target · Experience Manager
  Commerce · Campaign · Audience Manager
  Marketo · Workfront
     ↑ separate products, separate models,
       connected by integrations

vs a single-vendor suite like Google’s: GA4, Tag Manager and Google Ads were built to fit together. Adobe’s estate was assembled by acquisition over twenty years, and AEP is the retrofitted attempt to give it a common spine. That history is why the terminology never agrees with itself.

The acronym decoder

The single most useful thing on this page.

AEM      Adobe Experience Manager (CMS + DAM)
AEP      Adobe Experience Platform (foundation)
AJO      Adobe Journey Optimizer
AAM      Adobe Audience Manager (the old DMP)
RTCDP    Real-Time Customer Data Platform
CJA      Customer Journey Analytics
XDM      Experience Data Model (the schema
           standard everything on AEP uses)
ECID     Experience Cloud ID (the visitor ID)
A4T      Analytics for Target (reporting bridge)
VEC      Visual Experience Composer (Target)
EDS      Edge Delivery Services (AEM)
HTL      HTML Template Language (AEM)
DTM      Dynamic Tag Management (dead ancestor
           of Tags)

What renamed into what

Adobe renames aggressively, and old names persist in briefs, agency decks and the heads of everyone who learned the product a decade ago. An old name in a brief usually dates when the team last worked hands-on in the product.

You’ll hearIt’s now
Omniture, SiteCatalystAdobe Analytics
Offermatica, Test&TargetAdobe Target
Day CQ, CQ5Adobe Experience Manager
MagentoAdobe Commerce
DTM, then Adobe LaunchTags (in Data Collection)
Adobe Marketing CloudAdobe Experience Cloud
SightlyHTL
at.js, AppMeasurement.jsWeb SDK (alloy.js)

“Omniture” is the tell. Someone saying it is describing a very long-standing implementation, and probably one with a decade of accumulated eVar definitions nobody can account for.

The products, by job

Content and commerce

  • Experience Manager (AEM) — enterprise CMS, plus AEM Assets as a genuine DAM. Currently mid-rebuild around Edge Delivery Services — Adobe Experience Manager
  • Adobe Commerce — Magento, acquired 2018. Enterprise ecommerce, strong in complex B2B: company accounts, catalogue pricing, payment terms
  • Workfront — work and project management. Acquired, adjacent, appears in enterprise stacks

Measurement

  • Adobe Analytics — the long-standing web analytics product. eVars, props, Analysis Workspace. Pre-processed data — Adobe Analytics
  • Customer Journey Analytics (CJA) — the newer analytics product, built on AEP, report-time processing, any data source. See below

Personalisation and orchestration

  • Adobe Target — testing and personalisation. Activities, offers, profiles — Adobe Target
  • Journey Optimizer (AJO) — real-time journey orchestration and messaging, built on AEP
  • Adobe Campaign — the older cross-channel campaign product. Still sold; AJO is the newer equivalent

Data

  • Experience Platform (AEP) — the foundation. XDM schemas, Identity Service, Real-Time Customer Profile
  • Real-Time CDP — audience building and activation on AEP. The newer equivalent of Audience Manager
  • Audience Manager (AAM) — the third-party-cookie-era DMP. Its world largely ended with third-party cookies
  • Data Collection — Tags (the tag manager, formerly Launch) and the Web SDK

B2B

  • Marketo Engage — B2B marketing automation, acquired 2018. Runs on its own model, integrates rather than shares

Data collection, which is where you’ll actually work

The part a CRO or analytics person touches, and it has consolidated hard.

OLD — one library per product
  AppMeasurement.js   Analytics
  at.js               Target
  visitorAPI.js       identity (ECID)
  DIL.js              Audience Manager

NEW — one library for everything
  alloy.js            Web SDK
     ↓ one call to the Edge
  Edge Network fans it out to
  Analytics · Target · AEP · AJO

This is the current live migration across the Adobe estate, and the single most useful thing to know if you join a team mid-transition. The verified constraint that catches people: you cannot mix libraries on a page — Web SDK for Target alongside AppMeasurement for Analytics is unsupported, so all Adobe libraries migrate together.

Tags (formerly Launch, before that DTM) is the tag manager — the direct equivalent of GTM. Rules, data elements, extensions. Server-side Tags exists too — Server-Side Tag Management, Google Tag Manager.

ECID — the Experience Cloud ID — is the shared visitor identifier. It’s what lets Target audiences match Analytics segments match CDP profiles. When cross-product reporting doesn’t line up, ECID is usually where to look — Identity Stitching.

Adobe Analytics versus CJA

The live question, and the one most likely to come up.

Adobe AnalyticsCustomer Journey Analytics
Built onIts own stackAEP
Data scopePrimarily web and appAny data source
ProcessingHeavy pre-processingReport-time
Dimensions75 props, 250 eVarsUnlimited, no cardinality cap
Retroactive changesLargely noYes

The architectural difference is when the maths happens. Adobe Analytics pre-processes at collection, so how a variable persists is baked in when the data arrives. CJA calculates at report run time — which means settings can be applied retroactively, and you can hold several versions of variable persistence at once without changing collection.

In plain terms: in Adobe Analytics, a mistake in how you configured a variable is permanent for all the data already collected. In CJA, you change the setting and the history re-reads correctly.

Terminology changes too, which trips people in meetings:

Adobe Analytics    CJA
───────────────    ───
Visitors      →    People
Visits        →    Sessions
Hits          →    Events

Migration is not a dashboard rebuild. Adobe’s own framing is that it’s an architectural transformation — redefining how data is collected, modelled, governed and analysed. The recommended path is two-pronged: the Adobe Analytics source connector to bring existing data across, plus a fresh Web SDK implementation. Adobe suggests 3–6 months for users to become comfortable with the differences in Analysis Workspace.

The prerequisites are the real work: a strong person-level identifier, variables mapped to XDM schema, and alignment on what a dimension now means — Identity Stitching, Event Taxonomy Design, Warehouse-First Analytics.

[CHECK: Adobe has not published an end-of-life for Adobe Analytics, and I found no sunset date. Treat CJA as the strategic direction rather than assuming Analytics is going away.]

XDM — the thing that makes AEP coherent

Experience Data Model (XDM) is the schema standard everything on AEP uses. Every dataset conforms to a schema built from standard field groups plus your own.

XDM schema
├─ class          Profile, or Experience Event
├─ field groups   reusable blocks —
│                 Commerce, Web, Consent
└─ identity map   which IDs identify this record

Why it matters beyond Adobe: it’s the same discipline as any warehouse-first setup — agree the schema first, conform data to it on the way in, and reporting becomes a query rather than a negotiation. The cost is the same too: schema design is slow, and getting it wrong is expensive to unwind — Event Taxonomy Design, Tracking Plans.

What you’d actually meet in a CRO role

Realistically, four things:

  1. Adobe Analytics or CJA — where the numbers come from, and where you’ll build the report that judges a test
  2. Adobe Target — where the test runs — Adobe Target
  3. Tags — where the tracking is deployed
  4. AEM — where the content variant gets authored, if the Experience Fragment export is wired up

The rest — Journey Optimizer, Marketo, Workfront, Commerce — you need to recognise, not operate.

The question that tells you most about a team: are you on Web SDK, and are you on CJA? Both no means a long-standing implementation with legacy debt. Both yes means they’ve recently rebuilt data collection and know it. One of each means they’re mid-migration, which is where most of the estate currently sits.

Where the suite is strong

  • When you own several pieces, the integrations are genuinely deep — Target inheriting Analytics segments, AEM exporting to Target, RTCDP audiences everywhere
  • Governance and scale. Permissions, data governance labels, and consent handling built for organisations that get audited
  • Analysis Workspace is an excellent analysis tool, and better than most people expect coming from GA4

Where it hurts

  • The naming. Nothing is called what it was called, and documentation spans several eras simultaneously
  • Acquisition seams. Products that predate AEP have their own data models, their own identity concepts and their own admin. Integration is not the same as being one system
  • Time to value. Implementations are measured in quarters. A GA4 install is an afternoon
  • You need specialists, and they’re expensive precisely because the surface is this large
  • Two of everything, mid-transition. Analytics and CJA, Campaign and AJO, Audience Manager and RTCDP, at.js and Web SDK. Knowing which side of each pair a team sits on is the orientation

Graph View

Backlinks