In this blog
Every enterprise has the same blind spot: the customer's journey is continuous, but the data about it is not. Web analytics sees the website. The call-center platform sees calls. The POS sees purchases. Nobody sees the customer who researched online, called twice, then bought in a store — as one story. Customer Journey Analytics exists to close exactly that gap.
What is Customer Journey Analytics?
CJA is Adobe's cross-channel analytics application, built on Adobe Experience Platform. It takes datasets from any source — digital behavior, call logs, transactions, CRM — stitches them together on a common customer identity, and opens the result in Analysis Workspace, the same exploration environment Adobe Analytics users know.
The output is a capability web analytics cannot offer by construction: fallout reports where step one is a web visit, step two is a support call and step three is an in-branch purchase. Attribution that credits digital campaigns for offline conversions. Cohorts defined by cross-channel behavior. One governed place where "the journey" stops being a metaphor and becomes a queryable dataset.
How CJA works
The architecture in four layers
- Datasets on Experience Platform. Every source lands as an AEP dataset conforming to an XDM schema — web events from the Web SDK, batch uploads from the warehouse, streaming events from apps.
- Connections. A CJA connection selects which datasets join an analysis and on which identity fields.
- Data views. Governed lenses over a connection: which fields become dimensions and metrics, session definitions, attribution defaults. Different teams get different views of the same truth.
- Workspace. Analysis happens in the familiar drag-and-drop environment — freeform tables, flows, fallout, cohorts — now spanning every connected channel.
Identity stitching: the make-or-break layer
Joining datasets requires knowing that web visitor X, caller Y and loyalty member Z are the same person. CJA supports field-based stitching (a shared key like a hashed email or customer ID) and graph-based stitching via Experience Platform's identity graph. This is the layer that deserves your best thinking: stitch rates determine what fraction of journeys are actually joined, and design mistakes here are expensive to reverse. In our implementations, identity design gets more architectural attention than any other decision.
No eVars. No props. No limits that matter.
CJA has no variable slots to ration: any XDM schema field can become a dimension or metric, with effectively unlimited cardinality — no "(low traffic)" collapse, no allocation meetings about who gets eVar 47. Schema design replaces variable mapping, which moves the discipline upstream: get the schema right and everything downstream is flexible.
What becomes possible: concrete examples
- A bank joins web applications, call-center outcomes and branch fundings — discovering which digital journeys produce funded accounts versus abandoned calls
- A retailer connects e-commerce behavior with POS transactions, measuring how digital research drives store revenue it previously credited to "walk-ins"
- A telecom overlays app behavior, support calls and churn events, finding the journey signatures that precede cancellation
- An appliance brand like IFB enables CJA on a modern Web SDK foundation, turning fragmented tracking into end-to-end journey visualization
Translating the vocabulary
For teams coming from Adobe Analytics, the fastest way to orient is a straight translation of the concepts:
| Adobe Analytics concept | CJA equivalent | What changes |
|---|---|---|
| Report suite | Connection + datasets | Data joins across sources instead of living in one suite |
| eVar / prop | Schema field as dimension | No slots, no allocation, no expiry mechanics |
| Success event | Schema field as metric | Any numeric or countable field qualifies |
| Visitor (ECID) | Stitched person identity | Spans channels, not just browsers |
| Visit | Session (defined per data view) | You choose what a session means — retroactively |
| Virtual report suite | Data view | Governance layer with session and attribution defaults |
| Processing rules | Schema design + derived fields | Logic moves upstream or to query time |
The skills transfer; the mental model shifts one level up — from configuring a tool to designing data.
CJA and Adobe Analytics: sibling, successor, or both?
CJA runs on the same Workspace muscle memory analysts already have, but the data model underneath is fundamentally different — platform datasets instead of report suites, schema fields instead of variables, stitched identities instead of cookies. Adobe's investment direction is unambiguous: CJA is the future of Adobe analytics. What that means for your timeline — coexistence, transition, or direct adoption — is the subject of our CJA vs Adobe Analytics comparison.
What CJA costs
Licensing is negotiated with Adobe and driven primarily by rows of data ingested and retained, number of connections and data views, and whether CJA comes bundled with a wider Experience Platform commitment. Because the cost model is data-volume-based, dataset curation is a budget lever: land what answers questions, archive what does not. Our pricing guide covers the drivers in detail.
Who should adopt CJA — and when
CJA earns its keep when journeys genuinely cross channels and the organization is ready to act on that knowledge: contact centers, stores, field sales, connected products. If your business is digital-only and single-channel, Adobe Analytics may remain the right tool for now — an honest assessment we give regularly.
Readiness matters as much as need: you will want identity keys that exist across systems, data owners who can deliver clean feeds, and analysts prepared to think in schemas rather than variables. The implementation guide walks through the build in order.
Where to start
Pick the one cross-channel question that would change a real decision this quarter — "which digital journeys produce funded accounts," "does app adoption reduce support calls" — and scope a first release around answering it with two or three datasets. Prove the join, ship the insight, then expand. If you want that first release scoped by people who have done it repeatedly, talk to a consultant.
Frequently asked questions
What does Customer Journey Analytics do?
It ingests datasets from any channel — web, app, call center, POS, CRM — into Adobe Experience Platform, stitches them on a common identity, and lets analysts explore complete cross-channel journeys in Analysis Workspace.
Is CJA replacing Adobe Analytics?
Directionally, yes — CJA is where Adobe’s analytics investment is going, and most Adobe Analytics capabilities now exist in CJA. Practically, enterprises run transitions over quarters; our CJA vs Adobe Analytics comparison covers when to move.
Does CJA require Adobe Experience Platform?
Yes. CJA is an application on AEP: data lands in Experience Platform datasets under XDM schemas, and CJA connections read those datasets. That architecture is what enables cross-channel joins and unlimited cardinality.
What data can I bring into CJA?
Anything you can land in an AEP dataset: web and app behavior via Web/Mobile SDK, call-center logs, transactions, CRM attributes, loyalty events, even historical exports. If it has a timestamp and an identity, it can join the journey.
How long does a CJA implementation take?
A focused first release — two or three datasets, stitched identity, governed data views — typically runs 10–16 weeks. Identity design and data readiness drive the timeline far more than the tool itself.