Adobe’s latest CX Enterprise updates - what they are and what they mean
Adobe has released a significant group of updates across Customer Journey Analytics, Adobe Experience Platform, Journey Optimizer, and CX Enterprise Coworker. Individually, many look like feature releases. Together, they reveal a much clearer direction for Adobe’s martech stack.
Customer Journey Analytics is increasingly becoming the center of Adobe’s analytics strategy. Web SDK and Experience Platform are becoming the expected foundation for data collection. Adobe is building AI into implementation, administration, analysis, and troubleshooting workflows. At the same time, identity, governance, and data quality are becoming even more important as those processes become more automated.
Seven recent developments stand out:
Adobe is making the migration path from Adobe Analytics to CJA much more explicit - Jump to section
Adobe is adding AI-assisted CJA implementation and migration - Jump to section
CX Enterprise Coworker can perform AEP data management and data-quality analysis - Jump to section
CJA can now be queried from ChatGPT and other AI clients - Jump to section
CJA is adding Conversation Insights for AI interactions - Jump to section
Total Population Reporting will expand CJA beyond event-based analysis, although its release has been delayed - Jump to section
Journey Optimizer is tightening identity requirements for Audience Composition - Jump to section
Before looking at those announcements individually, it is worth considering where Adobe customers actually are in this transition.
The Adobe Analytics-to-CJA migration still has a long way to go
Adswerve's August 2026 Customer Journey Analytics Evolution Report examined Adobe implementations among Fortune 500 companies and found that modernization is underway, but far from complete. Web SDK was present in just over half of the Adobe implementations Adswerve identified. However, 79% were still using only the traditional Adobe Analytics props-and-eVars payload structure, while only 21% had adopted a semantic schema. Just 9% were collecting exclusively with a semantic schema, which Adswerve considers the group that has effectively completed the transition to CJA and sunset Adobe Analytics.
Read Adswerve's 2026 Adobe Customer Journey Analytics Evolution Report
There are limitations to that analysis. Server-side implementations and authenticated experiences can escape client-side detection, and Adswerve acknowledges that its methodology will miss some CJA deployments. Even accounting for those blind spots, Adswerve estimates that the share of organizations that have moved fully beyond Adobe Analytics is probably not much more than 10%.
That context makes Adobe's recent announcements particularly interesting.
Adobe is not introducing migration tools and formalizing its recommended CJA architecture after most customers have already migrated. It is doing so while a very large installed base still has substantial migration work ahead of it.
The announcements below increasingly look like Adobe building the infrastructure, tooling, and incentives needed to move that installed base toward AEP, Web SDK, semantic schemas, and CJA.
1. Adobe Is Making the Path from Adobe Analytics to CJA Much More Explicit
What it is
Adobe substantially updated its guidance for organizations moving from Adobe Analytics to Customer Journey Analytics.
Its recommended architecture is now clear:
Experience Platform Web SDK → Adobe Experience Platform → Customer Journey Analytics
Adobe recommends implementing Web SDK as the long-term collection architecture while using the Adobe Analytics Source Connector temporarily to bring historical Adobe Analytics data into Experience Platform and support side-by-side validation.
After enough Web SDK history has accumulated and the organization has completed its CJA transition, Adobe says the Analytics Source Connector can be turned off. Adobe also recommends ultimately transitioning fully from Adobe Analytics to CJA rather than maintaining both environments indefinitely.
Adobe has also introduced an in-product Customer Journey Analytics Upgrade Guide that generates migration steps based on an organization's current implementation and requirements.
Adobe documentation: Upgrade from Adobe Analytics to Customer Journey Analytics
Why it is important
This is stronger guidance than simply positioning CJA as Adobe's newer analytics product.
Adobe is documenting an architecture in which Adobe Analytics can become a transitional component rather than the permanent collection and reporting layer. Organizations making major new investments in Adobe Analytics should factor that direction into their roadmaps.
This is not an Adobe Analytics end-of-life announcement. Adobe has announced no shutdown date. But it does mean organizations should treat CJA migration as an architectural planning issue rather than waiting for an eventual EOL notice.
Adobe's recommendation to implement Web SDK and a semantic Experience Platform schema is equally significant. Simply pumping an existing props-and-eVars implementation through the Analytics Source Connector may get Adobe Analytics data into CJA, but Adobe explicitly does not recommend that as the long-term architecture.
Availability and cost
The updated migration guidance and CJA Upgrade Guide are available now. They are not separate add-on products.
CJA itself remains separately licensed, so organizations should evaluate their existing Adobe agreements when planning the transition.
How HDC can help you with this
HDC can assess what a CJA migration would actually involve before an organization commits to it.
That includes auditing the current Adobe Analytics implementation, determining which business rules should survive the migration, identifying legacy implementation debt that should not, designing the Experience Platform schema and Web SDK implementation, translating reporting requirements into CJA, and developing a phased validation and cutover plan.
A migration should not simply recreate Adobe Analytics inside CJA. It is an opportunity to redesign the analytics architecture around what CJA and Experience Platform can do today.
2. Adobe Is Adding AI-Assisted CJA Implementation and Migration
What it is
Adobe has released new CJA implementation and upgrade capabilities through CX Enterprise Coworker.
These include Implementation Guide skills that create tailored implementation or upgrade recommendations, intelligent implementation checklists for managing the resulting work, and Data Validation skills that can help determine whether implementations are configured correctly.
Adobe has also documented a Coworker workflow specifically for comparing Adobe Analytics and CJA data during migration.
Why it is important
Migration validation is one of the most time-consuming parts of moving from Adobe Analytics to CJA.
Differences can result from schema mappings, identity configuration, session definitions, attribution, filters, data-view settings, implementation changes, or legitimate differences in how the two platforms process data.
AI-assisted validation could substantially reduce the manual work involved in investigating those differences.
It does not eliminate the need for analytics expertise. An AI system may determine that two metrics disagree. Someone still needs to determine which definition is correct, whether an old Analytics rule should be reproduced, and whether the difference exposes an implementation problem.
Availability and cost
Adobe lists the new CJA implementation and upgrade skills as available beginning September 30, 2026.
They require CX Enterprise Coworker access, rather than being functionality automatically included for every CJA customer. Adobe uses AI-credit entitlements for Coworker activity, with trial access available to some eligible customers.
How HDC can help you with this
HDC can establish migration baselines, identify the dimensions and metrics requiring reconciliation, investigate discrepancies, review schema and identity design, and determine which legacy behaviors should be reproduced versus redesigned.
AI can accelerate validation. It should not become the authority on what your organization's data is supposed to mean.
3. CX Enterprise Coworker Can Now Perform AEP Data Management and Data Quality Analysis
What it is
Adobe's September Experience Platform release expanded Coworker with AEP-focused capabilities.
Coworker can use conversational data-management skills to examine dataset configuration and storage consumption and evaluate retention changes. A Data Validation skill can analyze AEP datasets and fields, identify potential data-quality problems, and summarize the findings conversationally.
The validation functionality is read-only and does not change schemas, mappings, or underlying data.
Why it is important
AEP implementations can become complex quickly, with many schemas, datasets, identities, mappings, retention settings, and data sources.
Finding an incorrect mapping, unexpectedly empty field, or inconsistent value traditionally requires navigating several interfaces, writing queries, or manually inspecting datasets.
Conversational validation makes routine auditing potentially much easier.
For CJA customers, this is especially relevant because reporting quality ultimately depends on the AEP data feeding CJA. No Workspace visualization can compensate for incorrect schema mappings, missing identities, or poorly designed datasets.
Availability and cost
Adobe released the new AEP data-management and validation skills on September 22, 2026.
They require access to CX Enterprise Coworker, which has its own entitlement and AI-credit model.
How HDC can help you with this
HDC can help establish an ongoing AEP data-quality process, including auditing schemas and datasets, identifying critical fields and identities, investigating fields that are not being populated, and determining whether issues should be fixed at collection, within AEP, or through CJA data-view configuration.
4. Customer Journey Analytics Can Now Be Queried from ChatGPT and Other AI Clients
What it is
Adobe made its Customer Journey Analytics MCP server plugins for ChatGPT and Claude generally available on September 1.
MCP, or Model Context Protocol, enables an AI client to connect to CJA and invoke Adobe-provided tools. Users can explore data views, run reports, retrieve analytics data, and investigate business questions using natural-language prompts rather than manually constructing every query in Analysis Workspace.
Adobe authentication and CJA permissions still apply, including a dedicated MCP Access permission.
Why it is important
This could materially change how business users interact with analytics.
Instead of beginning with:
Which dimensions, metrics, segments, and panels do I need?
a user can begin with:
Why did appointment conversions decline last week?
That lowers the barrier to analytics, but it also makes governance more important.
Natural-language analytics works best when dimensions are clearly named, metrics have consistent definitions, derived fields are reliable, and obsolete or misleading components have been removed.
AI makes good analytics architecture easier to use. It also makes bad analytics architecture easier to query.
Availability and cost
The CJA MCP capability has been Generally Available since September 1, 2026.
Adobe does not identify MCP access as a separate CJA SKU. Users need appropriate CJA access and permissions, while the external AI client may have its own subscription requirements.
How HDC can help you with this
HDC can prepare a CJA environment for natural-language analytics by cleaning up data views, establishing intuitive naming standards, validating calculated metrics and derived fields, removing duplicate components, documenting business definitions, and developing tested prompt patterns for common analytical questions.
5. CJA Is Preparing to Analyze AI Conversations as Part of the Customer Journey
What it is
Adobe's new Conversation Insights capability brings conversational-agent data into Customer Journey Analytics.
Organizations can collect prompts, responses, and agent metadata from LLM-powered experiences through Web SDK, then analyze those interactions alongside other customer behavior.
That potentially allows organizations to answer questions such as:
Did customers who used the AI assistant convert at a higher rate?
Which conversation intents are associated with abandonment?
Which responses lead customers further into a journey?
Are customers expressing frustration before contacting a call center?
Why it is important
Customer-facing AI is becoming another digital interaction channel.
If chatbot and AI-assistant interactions are analyzed separately from web, app, campaign, CRM, and conversion activity, organizations recreate the same channel silos that customer journey analytics is intended to eliminate.
The real value is not simply counting chatbot sessions. It is connecting the meaning of a conversation with what the customer subsequently does.
Availability and cost
Adobe originally planned Conversation Insights for September 22. The current release schedule lists October 8, 2026.
Adobe's documentation does not currently identify Conversation Insights as a separately priced SKU, although organizations obviously need the appropriate CJA environment and an implementation capable of collecting the conversational data.
How HDC can help you with this
HDC can help define the conversation events and metadata worth collecting, design the appropriate XDM structure, implement collection through Web SDK, connect conversational activity to existing identities and journeys, and build CJA reporting around business outcomes rather than chatbot activity counts.
6. Total Population Reporting Will Expand CJA Beyond Event-Based Analysis, but It Has Been Delayed
What it is
Most digital analytics reporting begins with events: what happened?
Adobe's planned Total Population Reporting capability would expand CJA analysis to entities in profile and lookup datasets, including people or entities that did not generate an event during the reporting period.
That opens the door to questions such as:
What percentage of all eligible customers completed an action?
How many known customers belong to a category even if they did not visit the website this month?
How does an active audience compare with the total addressable population?
Why it is important
This pushes CJA even further beyond the traditional web-analytics model.
The denominator no longer has to be people who produced digital events. CJA can become more useful for customer, account, membership, patient, product, and other entity-based analysis where the total population matters.
Availability and cost
Adobe originally planned Total Population Reporting for September 22, 2026. Adobe now lists the feature as postponed, with a new release date TBD.
Organizations should therefore avoid creating near-term project dependencies around it until Adobe publishes a new date.
Adobe has not announced a separate SKU for the capability.
How HDC can help you with this
HDC can identify reporting use cases that would benefit from population-based analysis, evaluate whether they can be addressed with today's AEP and CJA capabilities, and prepare identity, profile, lookup, and data-view architecture to take advantage of Total Population Reporting when it becomes available.
7. Adobe Journey Optimizer Is Tightening Identity Requirements for Audience Composition
What it is
Adobe has announced an important upcoming enforcement change in Journey Optimizer.
Beginning with the end-of-October release, AJO will stop journeys and campaigns that use an Audience Composition audience when the source dataset does not contain a primary identity descriptor.
Only Audience Composition audiences built from appropriately configured datasets will be supported for AJO journeys and campaigns.
Why it is important
This is not merely a recommended best practice. It is an enforcement change capable of stopping production journeys and campaigns.
It also illustrates a broader trend across Adobe's platform.
As AEP, CJA, Journey Optimizer, and AI-powered capabilities become more interconnected, identity configuration is becoming foundational infrastructure. Poor identity design can affect profile stitching, audience qualification, personalization, reporting, activation, and now whether some AJO journeys will run at all.
Availability and cost
Enforcement is scheduled for the end-of-October 2026 Journey Optimizer release.
There is no new SKU associated with the change. It affects existing Journey Optimizer implementations using the relevant Audience Composition configuration.
How HDC can help you with this
HDC can audit the schemas, datasets, identity settings, and Audience Composition configurations feeding Journey Optimizer and identify implementations potentially affected by the change.
More broadly, HDC can help design an identity strategy across AEP, CJA, and AJO, including ECID, authenticated identifiers, CRM IDs, identity namespaces, primary identities, and stitching.
Identity should be designed as part of the overall data architecture, not one journey at a time.
What These Announcements Say About Adobe's Direction
The individual features are useful, but the pattern behind them is more important.
Adobe is increasingly converging around an architecture in which:
Experience Platform is the data foundation.
Web SDK is the preferred digital collection layer.
Customer Journey Analytics is the analytics environment.
Semantic XDM schemas replace the legacy props-and-eVars model.
AI becomes an interface and automation layer across the stack.
The Adswerve adoption data shows why Adobe still has substantial work to do to get its customer base there. More than half of the Fortune 500 Adobe implementations Adswerve observed have begun adopting Web SDK, but only a small minority appear to have completed the deeper architectural transition away from Adobe Analytics and its legacy data model.
Adobe's recent product moves address several of the obstacles standing between those two points: migration planning, implementation effort, validation, data quality, identity management, and accessibility of the resulting analytics environment.
For organizations still running Adobe Analytics, the message is not that Adobe Analytics suddenly needs to be ripped out. There is no announced end-of-life date.
The message is that the direction of travel is becoming increasingly difficult to miss.
Organizations should understand what moving toward Web SDK, AEP, semantic schemas, and CJA would require before contractual deadlines or future product decisions force the issue.
And organizations already using CJA should make sure they have actually modernized their architecture rather than simply transporting an Adobe Analytics implementation into a newer reporting platform.
Heavey Digital Consulting helps organizations design, audit, migrate, and optimize Adobe Experience Platform and Customer Journey Analytics implementations, from Web SDK and XDM architecture through CJA data views, derived fields, identity strategy, reporting, governance, and migration planning. If your organization is evaluating CJA, cleaning up an inherited implementation, or determining how Adobe's evolving roadmap fits into your analytics strategy, HDC can help turn that roadmap into a practical implementation plan.
