Adobe Customer Journey Analytics (CJA): what it is and how we implement it in Mexico

When Adobe launched Adobe Experience Platform as the unified customer data foundation for its ecosystem, one question went unanswered for years: how do I analyze that data effectively? Adobe Customer Journey Analytics — known as CJA — is the answer. It is not an evolution of Adobe Analytics. It is a different product, built on AEP, that allows you to analyze data from any source in a flexible workspace without the limitations of the traditional hit-based model.

At WolfSellers we implement CJA as part of our enterprise clients' analytical maturity projects. In this post we explain what CJA is, how it differs from classic Adobe Analytics, what its technical components are, and which types of companies in Mexico benefit most from adopting it.

What is Adobe Customer Journey Analytics

Adobe Customer Journey Analytics (CJA) is Adobe's enterprise data analytics tool, natively integrated with Adobe Experience Platform (AEP). It connects data from multiple sources — web, mobile app, CRM, point of sale, call center, offline data — in a single analytics environment, and lets you explore it through a flexible workspace without re-implementing tracking code on each touchpoint.

Three characteristics define CJA against other analytics tools:

1. Any data, not just web data. CJA ingests AEP datasets directly. That means if your CRM, ERP, or loyalty platform already sends data to AEP, CJA can analyze it alongside digital behavior data without any additional integration step.
2. Analysis of people, not sessions. Unlike classic Adobe Analytics — which organizes data by hits and visits — CJA organizes data around identified people (using the AEP unified profile). Cohort analysis, multi-touch attribution, and customer lifetime value are significantly more accurate.
3. Open workspace with no schema limits. CJA's Analysis Workspace lets analysts create calculated metrics, segments, and dimensions at the time of analysis, without modifying the data collection implementation. An analyst can test hypotheses in minutes that in classic Adobe Analytics would require days of implementation work.

CJA vs classic Adobe Analytics: the differences that matter

The most common confusion when evaluating CJA is believing it directly replaces Adobe Analytics. That is not quite right.

Dimension	Adobe Analytics (classic)	Adobe Customer Journey Analytics
Data model	Hits / visits / visitors	AEP datasets (any schema)
Data sources	Primarily web and app	Web, app, CRM, ERP, offline, IoT
Identity	Cookie / ECID (non-persistent)	AEP unified profile (persistent, cross-device)
Attribution analysis	Predefined models (last click, first, linear)	Flexible Attribution IQ + algorithmic models
Metric creation	Requires prior implementation	On-the-fly in the workspace
AI integration	Adobe Sensei (anomaly detection, forecasting)	Generative AI + Sensei + AEP AI Assistant integration
Learning curve	Medium	High (requires understanding AEP)
Cost	Adobe Analytics license	Requires AEP + additional CJA license

When to choose CJA over Adobe Analytics?

• When you already have AEP implemented and want to leverage the datasets already living there
• When you need customer journey analysis that crosses online and offline data (a customer who called the call center and then bought in-store)
• When multi-touch attribution analysis is critical for marketing investment decisions
• When you have analysts who need to explore data freely without depending on the analytics implementation

When to stay with Adobe Analytics?

• When analysis is primarily of web/app behavior and you do not need to cross with offline data
• When the team is comfortable with the rule-based processing model
• When the budget does not justify the additional AEP + CJA layer
• When the organization does not yet have the data maturity to leverage the unified profile

Both tools can coexist. Many enterprise companies use Adobe Analytics for daily operational site analysis (real-time monitoring, alerts, daily performance reports) and CJA for strategic analyses that cross multiple data sources.

The three technical components of CJA

CJA's architecture is structured in three layers that map directly to the analysis process.

1. Connections

A connection in CJA is the configuration that links one or more AEP datasets to the analytics environment. It defines which datasets to include, which field acts as the person identifier (for cross-device identity resolution), and the date range of historical data to analyze.

A single connection can simultaneously include:

• The web events dataset (equivalent to Adobe Analytics AppMeasurement)
• The CRM dataset with purchase history and sales interactions
• The call center dataset with support ticket records
• The loyalty dataset with points and transactions

All that data becomes available for correlated analysis in the same workspace, without manual joins or additional ETL.

2. Data Views

A data view is the analytics configuration layer on top of a connection. It defines how data is presented to the analyst: which dataset fields are exposed as dimensions and metrics, what transformations are applied (value normalization, currency conversion, internal traffic exclusion), and what attribution rules are the default for that analytics context.

A single connection can have multiple data views. This allows the marketing team, product team, and ecommerce team to have their own views configured with the metrics and dimensions relevant to their work, without creating separate datasets.

3. Analysis Workspace projects

Once the connection and data view are configured, analysis happens in CJA's Analysis Workspace — the same familiar Adobe Analytics interface, but with access to all unified data sources. Additional capabilities over the classic Workspace include:

• Cross-channel flow visualizations: see a customer's complete journey from their first digital touchpoint to an offline purchase, including service interactions
• Cohort analysis with retention curves: segment cohorts by any behavior (not just first visit) and measure their retention over time
• Offline and online variable correlation: measure the impact of an email campaign on physical store visits (crossing CRM and point-of-sale data)
• Complex segments with sequential logic: "users who viewed product X, did not buy within 7 days, and then called the call center"

Enterprise CJA use cases in Mexico

Multi-touch attribution in complex B2C journeys

A retail company with physical and digital presence in Mexico faces the classic attribution problem: a customer sees an Instagram ad, visits the physical store, receives an email coupon, and completes the purchase in the app. Classic Adobe Analytics only sees the conversion in the app; the rest of the journey is invisible.

With CJA, data from the CRM (with store visit history), the email platform, and the ecommerce app are joined in a single AEP dataset. The complete journey is visible and attribution reflects the real contribution of each touchpoint.

Churn analysis in industrial B2B

A B2B manufacturing company wants to understand what signals precede the cancellation of a distribution contract. With CJA it can combine:

• Data from the distributor portal (order frequency, catalog queries)
• CRM data (interactions with the sales team, support tickets)
• Loyalty data (use of benefits from the distributor program)

The analysis identifies behavioral patterns that appear 90 days before a cancellation, enabling proactive intervention by the commercial team.

Omnichannel campaign measurement in financial retail

A financial institution launches a mortgage product campaign through email, display, branches, and app. With classic Adobe Analytics, each channel reports its own conversion metrics with no way to deduplicate customers who interacted at multiple touchpoints.

CJA, fed by the bank's AEP datasets, allows viewing the complete journey: from the first contact with the display ad to the credit application at a branch, with attribution distributed across each touchpoint according to its real contribution to conversion.

Technical prerequisites for implementing CJA

CJA is not a tool that gets turned on overnight. It requires a data foundation:

1. Active and configured Adobe Experience Platform. CJA reads directly from AEP datasets. Without AEP, there is no CJA.
2. XDM schemas defined for relevant data sources. Data to be analyzed in CJA must be in AEP with correctly configured Experience Data Model (XDM) schemas.
3. Configured datastreams. If the goal is to analyze web/app behavior, Adobe's Web SDK (Alloy.js) must be sending data to AEP — not to the classic Adobe Analytics collection.
4. CJA license. CJA is an additional Adobe SKU added to the AEP license. Commercial planning with Adobe is part of the adoption process.
5. Analytics team with capacity to work with structured data. CJA exposes more analytical power than Adobe Analytics, but also requires more technical context from analysts to leverage it.

The typical implementation process runs from 8 to 16 weeks, depending on how many datasets and sources are to be connected in the initial phase.

How we integrate CJA with the Adobe ecosystem

CJA does not work in isolation — its value multiplies when integrated with the rest of the Adobe Experience Cloud ecosystem:

• Adobe Real-Time CDP + CJA: audience segments built in RT-CDP can be analyzed in CJA to understand the behavior of those specific audiences. In turn, CJA insights inform the construction of new segments in RT-CDP.
• Adobe Journey Optimizer + CJA: journeys configured in AJO generate execution data (how many people entered, exited, converted at each step). CJA analyzes that data to identify the most effective journeys and abandonment points.
• Adobe Target + CJA: A/B testing experiments in Target generate experience data. CJA allows analyzing those experiments with advanced segmentation that Target alone cannot do.
• Adobe Commerce + CJA: transaction data from Adobe Commerce (carts, purchases, abandonment, catalog behavior) is sent to AEP and analyzed in CJA alongside pre-purchase behavioral data.

This integration makes CJA the "analytical nervous system" of the Adobe ecosystem: the place where you understand what is happening across the complete customer journey.

How we implement CJA at WolfSellers

CJA implementation at WolfSellers follows the same structured process we apply to any enterprise Adobe product:

Weeks 1-3 — Analytical discovery. Before touching any configuration, we understand what business questions need to be answered with CJA. "What is the real ROI of each marketing channel?" is a different question from "What behaviors predict B2B contract renewal?". The business questions define which datasets need to be connected and how the data views should be configured.

Weeks 3-6 — Data architecture. We define the identity strategy (which field identifies the customer in each dataset), the connections map (which datasets enter CJA and with what configuration), and the design of data views by team (marketing, product, ecommerce).

Weeks 6-10 — Implementation and validation. We configure the connections, data views, and first Workspace projects. We validate that the data shows what is expected by comparing against reference sources (classic Adobe Analytics, CRM reports).

Weeks 10-12 — Training and delivery. We train analytics teams in using CJA's Workspace — which is similar to Adobe Analytics' but with additional capabilities that require practice. We deliver analysis playbooks for the priority use cases identified in discovery.

Post-implementation support includes periodic reviews of Workspace projects, configuration updates when AEP schemas change, and support for new analytical use cases as the team matures in using the tool.

Frequently asked questions about Adobe Customer Journey Analytics

Does CJA replace Adobe Analytics?

Not necessarily. CJA and classic Adobe Analytics can coexist. Many enterprise organizations use Adobe Analytics for operational website analysis (real-time monitoring, alerts, daily performance reports) and CJA for strategic analyses that cross multiple data sources. The complete transition to CJA makes sense when the organization already uses AEP extensively and wants to consolidate analysis in a single environment.

How much historical data can be analyzed in CJA?

CJA can analyze as much historical data as is available in AEP datasets. If the CRM has 5 years of purchase history and that dataset is in AEP, CJA can analyze it. There is no technical window limitation — the practical limitation comes from AEP storage costs and the data volumes included in license contracts.

How different is CJA's Analysis Workspace from Adobe Analytics'?

The interface is very similar — anyone already using the Adobe Analytics Workspace can start using CJA's with a short learning curve. The differences are in the additional capabilities: dimensions and metrics created on-the-fly without re-implementation, analysis of people instead of visits, and access to all AEP datasets. The main difference is conceptual: the mental model shifts from "hits from a website" to "events from a person in any channel."

What team is needed to operate CJA?

To implement CJA you need a data architect with AEP experience (for connections and schema design) and a data analyst familiar with the Adobe Analytics Workspace (for data views and projects). To operate it day-to-day, a senior analyst who understands both the business and the data structure is sufficient. CJA does not require a dedicated engineering team for everyday analytical use.

Does CJA have machine learning and AI capabilities?

Yes. CJA includes Adobe Sensei capabilities available in Analysis Workspace (anomaly detection, contribution analysis, forecasting) and integrates with the AEP AI Assistant, which allows asking questions in natural language about the data. Generative AI capabilities are in active expansion on Adobe's roadmap — it is one of the areas where the AEP ecosystem is growing fastest.

Can CJA be implemented without having Adobe Analytics?

Yes. CJA can work exclusively with AEP data without needing Adobe Analytics as a source. In fact, organizations implementing AEP from scratch without legacy Adobe Analytics can connect Adobe's Web SDK directly to AEP and use CJA as their primary analytics tool from the start.

Related services

If this topic is relevant to your business, these services from WolfSellers can help you implement it:

• Adobe Experience Platform
• AI & Automation
• Adobe Commerce