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

Adobe launched Adobe Experience Platform as the unified customer data foundation for its ecosystem. But one question went unanswered for years: how do I analyze that data well? 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. It lets you analyze data from any source in a flexible workspace. And it does so without the limits of the traditional hit-based model.

At WolfSellers, we implement CJA as part of our enterprise clients' analytics maturity projects. In this post, we explain what CJA is and how it differs from classic Adobe Analytics. We also cover its technical components. And we show which types of companies in Mexico gain the most from adopting it.

What is Adobe Customer Journey Analytics

Adobe Customer Journey Analytics (CJA) is Adobe's enterprise data analytics tool. It is natively integrated with Adobe Experience Platform (AEP). It brings data from many sources into a single analytics environment: web, mobile app, CRM, point of sale, call center, and offline data. Then it lets you explore that data in a flexible workspace. You do not have to re-implement tracking code on each touchpoint.

Three traits set CJA apart from other analytics tools:

1. Any data, not just web data. CJA ingests AEP datasets directly. Say your CRM, ERP, or loyalty platform already sends data to AEP. Then CJA can analyze it next to digital behavior data, with no extra integration step.
2. Analysis of people, not sessions. Classic Adobe Analytics organizes data by hits and visits. CJA, instead, organizes data around identified people (using the AEP unified profile). That makes cohort analysis, multi-touch attribution, and customer lifetime value much more accurate.
3. Open workspace with no schema limits. CJA's Analysis Workspace lets analysts create calculated metrics, segments, and dimensions while they analyze. They do not have to change the data collection implementation. An analyst can test a hypothesis in minutes. In classic Adobe Analytics, the same test would take days of implementation work.

CJA vs classic Adobe Analytics: the differences that matter

The most common mix-up when people evaluate CJA is to think it simply replaces Adobe Analytics. That is not quite right. If you have already decided to make the move, our guide on migrating from Adobe Analytics to CJA covers the full process.

When to choose CJA over Adobe Analytics?

• When you already have AEP in place and want to use the datasets that already live 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 key to deciding where to invest in marketing
• When your analysts need to explore data freely, without depending on the analytics implementation

When to stay with Adobe Analytics?

• When you mostly analyze web/app behavior and do not need to cross it with offline data
• When the team is comfortable with the rule-based processing model
• When the budget does not justify the extra AEP + CJA layer
• When the organization does not yet have the data maturity to make use of the unified profile

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

The three technical components of CJA

CJA's architecture has three layers. They map directly to the analysis process.

1. Connections

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

A single connection can include all of these at once:

• 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 is then ready for correlated analysis in the same workspace. You need no manual joins or extra ETL.

2. Data Views

A data view is the analytics configuration layer that sits on top of a connection. It defines how data is shown to the analyst. It sets which dataset fields appear as dimensions and metrics. It sets which transformations apply (value normalization, currency conversion, internal traffic exclusion). And it sets the default attribution rules for that analytics context.

A single connection can have many data views. This way, the marketing, product, and ecommerce teams can each have their own view. Each view is set up with the metrics and dimensions that matter for that team's work. No one has to create separate datasets.

3. Analysis Workspace projects

Once the connection and data view are configured, analysis happens in CJA's Analysis Workspace. It is the same familiar Adobe Analytics interface, but with access to all unified data sources. Compared with the classic Workspace, it adds these capabilities:

• Cross-channel flow visualizations: see a customer's full journey, from the 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 how an email campaign affects 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

Do you want to know how to build each analysis in Analysis Workspace? We walk through it step by step in practical Customer Journey Analytics analyses, with examples.

Multi-touch attribution in complex B2C journeys

Take a retail company with physical and digital presence in Mexico. It faces the classic attribution problem. A customer sees an Instagram ad and visits the physical store. Then they get an email coupon and complete 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 full journey becomes visible. And attribution reflects the real contribution of each touchpoint.

Churn analysis in industrial B2B

A B2B manufacturing company wants to know which signals come before a distribution contract is canceled. 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 finds behavior patterns that appear 90 days before a cancellation. That lets the sales team step in early.

Omnichannel campaign measurement in financial retail

A financial institution launches a campaign for a mortgage product through email, display, branches, and app. With classic Adobe Analytics, each channel reports its own conversion metrics. There is no way to deduplicate customers who interacted at more than one touchpoint.

CJA, fed by the bank's AEP datasets, shows the full journey. It goes from the first contact with the display ad to the credit application at a branch. Attribution is spread across each touchpoint based on its real contribution to conversion.

Technical prerequisites for implementing CJA

CJA is not a tool you turn on overnight. It needs 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. The data you want to analyze in CJA must be in AEP, with Experience Data Model (XDM) schemas set up correctly.
3. Configured datastreams. If you want to analyze web/app behavior, Adobe's Web SDK (Alloy.js) must send data to AEP. It must not send it to the classic Adobe Analytics collection.
4. CJA license. CJA is an extra Adobe SKU on top of the AEP license. Planning the purchase with Adobe is part of the adoption process.
5. Analytics team with capacity to work with structured data. CJA gives more analytical power than Adobe Analytics. But analysts also need more technical context to make use of it.

A typical implementation takes 8 to 16 weeks. It depends on how many datasets and sources you connect in the first phase.

How we integrate CJA with the Adobe ecosystem

CJA does not work alone. Its value multiplies when you integrate it with the rest of the Adobe Experience Cloud ecosystem:

• Adobe Real-Time CDP + CJA: you can analyze audience segments built in RT-CDP in CJA to understand how those audiences behave. In turn, CJA insights guide how you build new segments in RT-CDP.
• Adobe Journey Optimizer + CJA: journeys set up in AJO produce execution data (how many people entered, exited, or converted at each step). CJA analyzes that data to find the most effective journeys and the drop-off points.
• Adobe Target + CJA: A/B testing experiments in Target produce experience data. CJA can analyze those experiments with advanced segmentation that Target cannot do on its own.
• Adobe Commerce + CJA: transaction data from Adobe Commerce (carts, purchases, abandonment, catalog behavior) goes to AEP. CJA then analyzes it next to the behavior data from before the purchase.

This integration makes CJA the "analytical nervous system" of the Adobe ecosystem. It is the place where you understand what is going on across the whole customer journey.

How we implement CJA at WolfSellers

At WolfSellers, we implement CJA with the same structured process we use for any enterprise Adobe product:

Weeks 1-3 — Analytical discovery. Before we touch any configuration, we learn which business questions CJA must answer. "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 to connect and how to set up the data views.

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

Weeks 6-10 — Implementation and validation. We set up the connections, data views, and first Workspace projects. Then we check that the data shows what we expect. We compare it against reference sources (classic Adobe Analytics, CRM reports).

Weeks 10-12 — Training and delivery. We train analytics teams to use CJA's Workspace. It is similar to the one in Adobe Analytics, but its extra capabilities take practice. We deliver analysis playbooks for the priority use cases we found in discovery.

Our support after implementation includes regular reviews of Workspace projects. We update the configuration when AEP schemas change. And we support new analytics use cases as the team gains skill with 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). They use CJA for strategic analyses that cross many data sources. A full move to CJA makes sense when the organization already uses AEP widely and wants all its analysis in a single environment.

How much historical data can be analyzed in CJA?

CJA can analyze as much historical data as there is 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 limit on the time window. The practical limit 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 who already uses the Adobe Analytics Workspace can pick up CJA's with a short learning curve. The differences are in the extra capabilities. You get 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 in the concept. 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). You also need a data analyst who knows the Adobe Analytics Workspace (for data views and projects). To run it day-to-day, a senior analyst who understands both the business and the data structure is enough. CJA does not need a dedicated engineering team for everyday analytics work.

Does CJA have machine learning and AI capabilities?

Yes. CJA includes Adobe Sensei capabilities in Analysis Workspace (anomaly detection, contribution analysis, forecasting). It also integrates with the AEP AI Assistant, which lets you ask questions about the data in natural language. Adobe keeps adding generative AI capabilities on its 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 only with AEP data, without Adobe Analytics as a source. In fact, some organizations implement AEP from scratch, with no legacy Adobe Analytics. They can connect Adobe's Web SDK directly to AEP and use CJA as their main 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