Adobe Customer Journey Analytics: what CJA does that Adobe Analytics can't
Adobe Customer Journey Analytics (CJA) is Adobe's analytics application on Adobe Experience Platform. It runs Analysis Workspace over any dataset you load into the platform, and it ties events to people rather than cookies.
A small example shows why that matters. Your web dashboard says checkout conversion went up last month. Your call center says calls about failed orders went up the same month. Both numbers are true, and in a classic setup they sit in two systems that never meet. In CJA, the checkout events and the call logs can live in one connection, stitched to the same customer ID. You can then check whether the people behind the new orders are the same people calling.
Adobe's product description calls CJA "an Analysis Workspace experience on Adobe Experience Platform infrastructure," one that is "different and distinct" from Adobe Analytics. The CJA overview positions it as Adobe's newer analytics product, built for data beyond the website.
"Customer journey analytics" is also a general term for analyzing customer interactions in sequence, across channels and over time. People who search for "Adobe CJA" or "CJA Adobe" mean the product, and that's what this piece covers.
How Adobe Customer Journey Analytics works
One mental model helps more than any diagram. Adobe Analytics files each piece of paper the moment it arrives, so the labels are fixed at collection. CJA keeps the raw paper and lets you relabel the drawers whenever the question changes. Four pieces make that possible.
Datasets in Experience Platform
Everything CJA reports on has to reach Experience Platform first. That covers web and app data, offline files and existing Adobe Analytics report suites. Ingestion happens in the platform, not in CJA. The data is shaped by the Experience Data Model (XDM), Adobe's standard schema format. For the platform itself, see what Adobe Experience Platform is.
Sitting on the platform also means CJA inherits its governance. Adobe's CJA product page lists usage policies and sensitivity labels on the data, plus role-based permissions on who can see or export it. That starts to matter the day CRM records land next to web events.
Connections and stitching
A connection tells CJA which datasets to combine, for example web events, call center logs and loyalty data. Adobe's overview notes that several report suites can be combined as well, which classic Adobe Analytics can't do.
Stitching is where devices become people. Web and mobile data often lacks a person ID on every event, so CJA uses authenticated and anonymous sessions to find a common one, as Adobe's stitching documentation explains. Field-based stitching pairs unknown events with known ones using the identifier fields in a single dataset. Graph-based stitching uses the Experience Platform Identity Service graph, built from multiple datasets, and only comes with the Prime and Ultimate packages. Either way, the browsing someone did before logging in can count toward the right customer. It's Adobe's version of identity resolution for analytics.
Data views
A data view holds the dimensions, metrics, session rules and attribution settings for a connection. Adobe describes it as the CJA equivalent of a virtual report suite.
The logic in a data view runs at report time. Change a session timeout today and last year's data is recalculated with the new rule. Adobe calls this retroactive data manipulation, and it's what makes flexible ad hoc analysis possible. In practice, it's the difference analysts notice first, because it settles many "we should have defined that differently" arguments without new tagging.
Analysis Workspace
Analysts build projects in Analysis Workspace, the same interface they know from Adobe Analytics. CJA adds visualizations for cross-channel paths, chiefly the Journey canvas, where you lay out the steps customers take and see where they continue or fall out.
Adobe also pitches CJA at business users. Its product FAQ says that once cross-channel data is flowing, the analysis itself doesn't require analyst-level tooling. Adobe says CJA uses AI to surface insights and predict outcomes, though which pieces you get, such as forecasting and anomaly alerts, depends on your package.
Where teams put it to work
Adobe's CX Analytics pricing guide lists the common use cases. They reduce to four jobs.
The first is lifecycle analysis: following customers from acquisition to retention, including the stretches that happen offline. The second is cross-channel attribution across paid, owned and earned channels, with store and call center outcomes in the same view. Third comes friction and churn, meaning the step where customers stall, call support or leave. The fourth is personalization, where you build audiences in Workspace and send them to Real-Time CDP or Journey Optimizer.
The data sources Adobe lists for this are web and mobile analytics, CRM, point of sale, call center logs, loyalty programs and marketing automation. If your CRM already holds a customer ID that shows up in those systems, you have a strong starting point for a connection. If no identifier is shared across channels, settle that before you talk licensing. Stitching can't link records that have nothing in common, and you'd be paying for cross-channel analysis you can't run.
Adobe Analytics vs Customer Journey Analytics
Adobe's product FAQ calls the two products siblings in its Adobe CX Analytics portfolio, introduced at Adobe Summit 2026. Adobe Analytics now carries the "digital analytics" label there. In Adobe's words, Adobe Analytics measures web and mobile behavior on a fixed report-suite schema, while CJA ingests any online or offline source and stitches by person. Adobe adds that "most enterprises run both."
| Adobe Analytics | Adobe Customer Journey Analytics | |
|---|---|---|
| Where data lives | Report suites, with Adobe's own data collection | Adobe Experience Platform datasets, shaped by XDM |
| Main scope | Web and mobile apps | Any channel: web, app, call center, point of sale, CRM |
| Custom variables | Up to 75 props and 250 eVars | No eVars or props; no cardinality limit on a dimension |
| When logic runs | Mostly at collection time | At report time, so changes apply to past data |
| Identity | Cookie- and device-based visitor IDs | Person-level stitching (field-based or graph-based) |
| SQL access | None | SQL through Data Distiller |
| HIPAA | Not HIPAA ready | HIPAA ready |
| Combine report suites | No | Yes |
| Activity Map | Yes | Not supported, and not yet planned |
The cardinality, SQL, HIPAA and Activity Map rows come from Adobe's CJA feature support page, updated October 16, 2026. That page changes as Adobe ships features, so check it again before you sign anything.
The table makes CJA look like a straight upgrade, and for some teams it isn't. If every question your team asks starts and ends on the website, Adobe Analytics still does that job well. Teams that mostly read scheduled reports won't use much of CJA either, since its extra freedom lives in Workspace. CJA earns its place when a question crosses a channel boundary, like the checkout and call center puzzle above.
What the four CJA packages include
Adobe licenses CJA in 4 packages (Foundation, Select, Prime and Ultimate), each priced per million rows of data. The table draws on Adobe's CJA product description, effective October 22, 2026.
| Feature | Foundation | Select | Prime | Ultimate |
|---|---|---|---|---|
| Derived fields | Not included | 100 per connection | 200 per connection | 500 per connection |
| Field-based stitching | Not included | Included | Included | Included |
| Graph-based stitching | Not included | Not included | Included | Included |
| Forecasting | Not included | Included | Included | Included |
| Intelligent alerts | Threshold alerts only | Threshold and anomaly | Threshold and anomaly | Threshold and anomaly |
| Ad hoc SQL query | Not included | 5 users | 5 users | 5 users |
| Refreshing audiences | 75 | 75 | 100 | 150 |
| Real-time reporting | Not included | Not included | Not included | Included |
| Historical data beyond 13 months | Add-on | Add-on | Add-on | 12 months included |
Three terms in the contract deserve more attention than they usually get. Every package covers data with a timestamp under 13 months, and older data needs extra capacity. Backfill through the Adobe Analytics source connector is also capped at 13 months unless you add Extended Data Capacity. Monthly report requests run from 500,000 (Foundation) to 5,000,000 (Ultimate) per organization. Adobe counts requests from Workspace, Report Builder, APIs and MCP-compatible clients, so a busy dashboard or AI client can eat into that number.
How much does Adobe Customer Journey Analytics cost?
Adobe doesn't publish CJA prices, and its pricing guide sends every buyer to a tailored quote. The figure moves mainly with the package, your rows of data and add-ons such as Data Distiller, B2B Edition or Extended Data Capacity.
The license is rarely the whole bill. Schema design, Web SDK tagging, identity rules and user training decide whether anyone gets value from it, so budget for that work alongside the quote.
What's in CJA as of October 2026
Adobe ships CJA updates often, so read this as a snapshot rather than a full list.
| Feature | What it does |
|---|---|
| Journey canvas | Map a path from scratch or open one from Adobe Journey Optimizer, then see drop-off at each step |
| Guided analysis | Templated product analytics such as funnels, retention, engagement and release impact; the number of types depends on your package |
| Experimentation panel | Compare A/B test variations from any platform, including Adobe Target, Journey Optimizer and your own data |
| Derived fields | Build new fields at report time, such as a cleaner marketing channel, without touching source data |
| Audience publishing | Send audiences defined in Workspace to Real-Time CDP and Journey Optimizer |
| Conversation Insights | Turns chatbot transcripts and service conversations into "structured, measurable signals"; licensed in packs of conversation turns |
| B2B Edition | Analyzes accounts and buying groups; licensed per thousand reportable businessperson profiles |
The Data Insights Agent needs its own note. It's a generative AI agent in the AI Assistant that answers plain-language questions by building Workspace charts. Adobe's documentation says limited-time access ran through March 31, 2026, and continued use requires a license for Adobe Experience Platform Agent Orchestrator. Ask your Adobe account team where your contract stands.
Older guides may also list Content Analytics as a CJA add-on. As of February 2026, Adobe sells it only as a standalone product.
Moving from Adobe Analytics to CJA
The upgrade is a data project before it's an analytics project. Adobe's upgrade recommendations, updated October 16, 2026, set the order.
- Design the XDM schema before you tag anything. Your schema decides what you can ask later. Map the events, identities and attributes you need from every channel, not just the website. Enable the profile option if you plan to send audiences to Real-Time CDP.
- Implement the Experience Platform Web SDK. Adobe says a new Web SDK implementation "is the best way" to collect data for CJA, and it doesn't recommend the Analytics source connector alone as a long-term setup. Set up the datastream, implement the SDK through tags, the API or manual code, then confirm data arrives in your dataset.
- Build the connection and data view, then compare. Add other channel datasets, such as call center data, and compare old and new numbers side by side. Expect gaps: Adobe notes that visits are calculated at processing time in Adobe Analytics, while sessions are calculated at report time in CJA.
- Load history through the Analytics source connector. That way trend lines don't start from zero. The 13-month backfill limit in the license applies here.
- Give users 3 to 6 months, and switch Adobe Analytics off last. Adobe suggests that much time for people to learn the Workspace differences. Keep Adobe Analytics running until the Web SDK setup is complete and you trust the new data.
Some things won't carry over cleanly. Adobe's evolution guide says Adobe Analytics segments and calculated metrics aren't compatible as-is, though many can be rebuilt against the new schema. Activity Map isn't supported, with no plan to add it. Data Feeds have no exact replacement, and Adobe points instead to Full Table Export, Platform dataset export and the reporting API. Dimensions set in data views also top out at 90 days of persistence.
None of this works if the data in Experience Platform is thin or messy. Adobe ties CJA's value to connecting real cross-channel data first, and reports are only as good as the data quality behind them.
The first thing our Adobe Analytics services team would check is the identity question: which customer ID appears in your web, CRM and call center data, and how often. The answer shapes the schema, the stitching method and the package. If the site runs on AEM, plan the Web SDK tagging together with any Adobe Experience Manager services work. To start, pick the one business question your teams argue about most and bring it to us.
FAQ
Is Adobe Customer Journey Analytics replacing Adobe Analytics?
Not by force. Adobe calls the two products siblings, says most enterprises run both and describes the move as an evolution, not a forced migration. Adobe Analytics stays the tool for focused web and app analysis, while CJA handles questions that cross channels.
Can you use CJA without Adobe Experience Platform?
No. CJA is built on Experience Platform, and Adobe says there's no standalone version that runs without it. Your web, app, offline or Adobe Analytics data has to reach Experience Platform before CJA can report on it.
How quickly does data show up in CJA?
Adobe's CJA FAQ says live data is processed and ingested within 90 minutes once it's available in Experience Platform. Real-time reporting in Analysis Workspace comes only with the Ultimate package.
