Customer journey analytics combines a company’s interactions across channels (web, apps, email, support, stores and other offline records) to analyse how people move between them. Where the data and identifiers can be connected, a journey extends beyond one site or app; the view is only as complete as the sources collected and the identities that can be reliably joined. In these interviews the phrase nearly always names a product, Adobe Customer Journey Analytics, and most of the companies here reach it by upgrading from Adobe Analytics rather than by shopping a category. Those without it assemble parts of that view from other tools. Either way, the work buyers describe is joining the data.
What is customer journey analytics?
Customer journey analytics is the analysis of how people move across a company’s channels — website and app, email and push, call center, stores and other offline touchpoints — using connected event data: the paths, sequences, conversion points and drop-offs across the whole sequence, not within one channel. Offline records join the journey when they can be tied to a consistent identifier. Analysts compare journeys and apply attribution in reporting, which describes how a model assigns credit; it does not by itself show what caused an outcome.
Two things set it apart. The first is the join itself: records collected under different identifiers (a device, a cookie, a logged-in ID) are connected where a reliable relationship between them exists, which vendors call stitching. Not every anonymous visit can be assigned to a known person; Adobe’s documentation says that where no person ID can be determined, the event keeps its persistent ID. A wrong match is worse, because it merges two people’s activity into one journey. The second is reach beyond digital, so a store purchase, a booking or a support call can sit in the same journey as the visit before it, as far as that data is available and its identifiers match. Installing the product does not settle either.
It is an analysis tool. It reports on journeys; it does not send messages or decide what a customer receives next.
The second half of the question is the one buyers can answer that a definition cannot:
In these interviews the phrase is mostly a product name. More than eight in ten of the companies that say journey analytics in their own words mean Adobe Customer Journey Analytics, which Adobe’s documentation calls its next-generation Analytics solution, built on data held in Adobe Experience Platform. That is how these buyers describe their own software, not a measure of market share: journey analysis is a general capability, and other companies do it with product, web or experience analytics, or with BI on a data warehouse, without calling it journey analytics.
Most of the companies that say how they came to it were upgrading from Adobe Analytics, often without evaluating anything else. And the part buyers describe as hard is not the reports but bringing each channel’s data in and joining it to a person, work the tool leaves to them.
What is the difference between customer journey analytics, web analytics and product analytics?
Web analytics measures a site or app, product analytics measures behaviour inside a product, and customer journey analytics follows a person across every channel a company can connect, offline included. The edges overlap: all three report paths and funnels, and the difference is how much of the customer’s journey the data reaches.
Against web analytics, the difference is the data. Adobe Analytics, like Google Analytics 4, measures what tags on a site or app collect. A health insurer’s digital leader explains what changed a month and a half into using both: “Think of Adobe Analytics as telling me everything I want to know about the metrics on my site.” Customer Journey Analytics, the same buyer says, “gives me everything I have in Adobe Analytics, but it also gives me all the other channels: call center, direct mail, and others.” Adobe’s documentation, updated November 6, 2026, adds technical differences: dimensions and metrics with no stated limit in place of Analytics’ eVars, props and events, and historical data that can be removed or corrected.
Against product analytics, the difference is the audience. A financial services company runs Amplitude beside Customer Journey Analytics, and its marketing-technology lead splits them by job: “I think Amplitude has a more product angle to it. I think product teams really enjoy it more, and Adobe CJA is more for marketers.”
Buyers also keep it apart from the tools on either side of it in a stack. A quick-service restaurant chain separates it from its customer data platform: “we more so use Adobe's Real-time CDP for segmentation. CJA is really just for analysis.” What it wants from the analysis is the offline link, whether an offer led to transactions “even if those transactions perhaps occurred in a brick-and-mortar restaurant as opposed to a digital channel.” A specialty retailer’s marketing-technology lead adds that the identity work is separate too: “CJA has a different kind of graph based stitching. So that is differently handled than the RTCDP identity stitching.”
Journey orchestration
Runs the journey: decides and sends the next email, push or text. Customer journey analytics measures how those journeys performed. See what customer journey orchestration is.
Customer data platform
Unifies profiles to build and send audiences. Journey analytics may read the same data, but buyers use it to analyse, not to activate. See what a CDP is.
Experience analytics
Shows what happens on a page: heatmaps, replays, errors, the path between pages. Contentsquare and Quantum Metric do this; it covers the digital part of a journey only. See what session replay software is.
Who buys customer journey analytics?
Very large companies, in businesses where customers also call, visit or book offline. About two in three of the companies that rate Adobe Customer Journey Analytics have more than ten billion dollars in revenue. Among companies rating Adobe Analytics the share is two in five, for Contentsquare under a quarter, and for Google Analytics 4 and Amplitude about one in eight.
The industries explain why. They are banks, insurers and wealth managers, airlines, cruise lines and hotel groups, large retailers, a restaurant chain, a hospital system and a university: businesses where a customer also calls, visits a branch or store, or books through an agent. The buyers are digital-analytics, marketing-technology and personalization leaders, and the product is usually one piece of a larger Adobe estate. Existing Adobe Analytics customers can add it to a Select, Prime or Ultimate contract, and Adobe also sells it as a standalone product. Either way it runs on Adobe Experience Platform: the datasets it reports on have to be in Experience Platform, and it depends on Experience Platform’s ingestion and schemas as well as its own connections and data views. The package sets what the contract includes, from the stitching method to how many rows a report export can carry.
Smaller companies use the phrase too, for something else. An ecommerce brand planning its next year wants to stand up “customer journey analytics, some type of platform similar to FullStory”, meaning behaviour on its own site.
How do companies come to customer journey analytics?
Three routes lead into Adobe’s product, and the first is the one that shapes everything about the purchase. Companies without it take a fourth approach, which is an alternative to the product rather than a way into it.
- Upgrading from Adobe Analytics
- Buying it alongside other Adobe Experience Platform products
- Selecting it in an evaluation against other tools
- The alternative: analysing journeys with tools the company already runs
Among the companies that describe how they came to Adobe’s product, about two in three name the upgrade from Adobe Analytics as the main route, and the other two routes make up the rest. Companies without it are a separate group. These are routes in these interviews, not market shares or adoption rates.
Upgrade from Adobe Analytics
The company already runs Adobe Analytics and begins adopting Customer Journey Analytics, Adobe’s newer analytics product built on Experience Platform, and several say they evaluated nothing else. That is a migration decision, not evidence that Adobe Analytics is ending or that every customer must replace it. By their latest interviews, several describe the move as finished, with Customer Journey Analytics now their main analytics tool; about half are part way, with both tools running; and the rest are planning or piloting it. Adobe’s upgrade guidance, updated November 6, 2026, recommends a new Experience Platform Web SDK implementation, the Analytics source connector to keep historical data and compare reports, a schema, datasets, a connection and a data view, a period with Adobe Analytics running in parallel while the new data is validated, and three to six months for users to learn the differences. It treats switching Adobe Analytics off as a decision for after that validation, with no deadline. How long these moves take is covered in analytics migration timelines.
A university’s marketing-analytics director describes the decision: “No, we didn't evaluate any others. We moved from Adobe Analytics to Customer Journey Analytics.” A restaurant chain’s marketing-technology lead says the same, choosing it “Strictly based on reputation. We didn't do any kind of real evaluation.”
With Experience Platform, Real-Time CDP and Journey Optimizer
The company buys Adobe’s data platform and its applications together, and Customer Journey Analytics comes with them as the reporting layer, reading the same datasets. Airlines, hotel groups, banks and retailers describe it this way, and several put it last in line, after the customer data platform.
A specialty retailer’s marketing-technology engineer explains the dependency: “if you are using Customer Journey Analytics or Journey Optimizer, both of the tools uses the data sets which are created in RTCDP.”
Chosen in an evaluation
A company with no Adobe Analytics compares it against other tools for a cross-channel need. A hospital system that switched off Google Analytics for privacy reasons weighed it against Freshpaint, a cheaper tool for compliant event collection, and paid more for the cross-channel depth. A business-technology company began moving its dashboards from Looker Studio to it, keeping Looker Studio for email reporting, because, its campaign-marketing director says, it can give report access to anyone on the team.
The hospital system’s digital-marketing director is candid about the trade: “Freshpaint was simpler and faster, and we might have gotten further with that program compared to how we're not implementing CJA to its best advantage yet.”
Assembled from tools already in place
Companies without Adobe’s product analyse parts of the journey with tools they already run: Amplitude or Mixpanel for behaviour inside a product, Contentsquare, Quantum Metric or FullStory for the digital experience on a site, path exploration in Google Analytics 4 for web and app paths, and BI on a data warehouse to combine more of the business’s data. None of these necessarily gives person-level, cross-channel analysis without data engineering. Using software already in place avoids buying a new platform, but connecting identities and building and maintaining the combined view is still an internal cost, and it is where this approach stalls.
One software company’s marketing director does it by hand: “Sometimes we actually merge the data and create our own CJA.” A health-benefits company’s former digital leader tried the same in Tableau: “When we tried to make it a journey analytics tool and connect a lot more data sources to it, it broke.”
The routes are not one-way. A technology hardware company paid for a year of Customer Journey Analytics and did not renew it in 2024, saying its biggest issue was that “there is no way to export the CJA journey data” without Adobe’s customer data platform, which it did not use. That reflects its requirements at the time, not necessarily what the product does now. Adobe’s documentation, updated November 6, 2026, describes full-table export of Workspace tables to cloud destinations including Amazon S3 and Snowflake, limited to ten dimensions and ten metrics per table and to a row count set by the licence. Exporting a report table is not the same as exporting the event-level journey data or the identity links behind it. If you need those, our suggestion is to ask Adobe to show which datasets, at what granularity and to which destinations your contract allows. The restaurant chain above, which finished its upgrade, said in October 2026 that it is considering another product-analytics tool to replace or supplement it. Those are two cases, not a churn rate.
Which customer journey analytics tools do buyers use?
Adobe Customer Journey Analytics is the product buyers name for it, rated 7.8/10. Among the tools companies use for parts of the job, Amplitude rates 7.5/10, Contentsquare 7.4/10 and Google Analytics 4 6.6/10. Those are ratings for each tool’s own job, not for journey analytics, and a company rating one is not necessarily using it to follow journeys.
Built for cross-channel journey analysis
Adobe Customer Journey Analytics
Used for part of the job
Amplitude · Mixpanel · Heap (journeys inside a product) · Contentsquare · Quantum Metric · FullStory · Glassbox (paths and replays on a site) · Google Analytics 4 (path exploration) · Tableau · Power BI (on Snowflake, Redshift or Databricks)
Adobe Analytics rates 7.2/10, below Adobe’s newer product, but the two figures come from different groups of buyers, not from the same companies before and after a move. Companies also combine the routes: a hotel group marries the stay records it keeps in Redshift with Customer Journey Analytics to form a complete picture of digital behaviour and stay revenue.
The praise for Customer Journey Analytics is flexibility and self-service. A wealth-management firm values letting marketers pull their own campaign analytics, “being less reliant on leveraging a data team to do so”, and a digital media company that retired Adobe Analytics for it says “I love the flexibility, I love the UI.” The complaints are setup and skills: the hospital system says “It's not easy to set up CJA, and you kind of need somebody who is deeply understanding of the bells and whistles and the platform.” The hotel group said in July 2026 that its team had evaluated Adobe’s AI analysis, found it was not answering its questions correctly, and built its own. Adobe documents a generative AI Data Insights Agent in the product, in a page updated October 12, 2026, that ties continued access to licensing Adobe Experience Platform Agent Orchestrator.
What does customer journey analytics cost, and what gets in the way?
The licence is the visible cost; the buyers here describe data integration, identity work and specialist staff as the larger ones. Adobe counts Customer Journey Analytics usage in different units from Adobe Analytics, so an Adobe Analytics budget is not a reliable estimate; how that played out for one company that hit overages is on the Adobe Experience Cloud stack page, and what buyers say about its price against Adobe Analytics is on what analytics buyers actually pay. The total effort depends on how many datasets are brought in, how identifiers are matched, which stitching method the contract permits, and who maintains the reports.
The work buyers describe is joining the data. A telecom company’s engineering director rates it below Adobe Analytics for that reason: “that bringing that data in and also managing that identity is all left on us.” A specialty retailer found the product could not map its online traffic to offline sales on its own, and wrote custom queries in Experience Platform to merge the two before loading them back.
Stitching has limits that, in our view, a demonstration should show. Some events connect through an authenticated ID while others stay tied to a device or browser; where no match is available the journey is incomplete, and where a match is wrong it merges two people’s activity. The join also needs permissions and data governance in place. Adobe’s documentation, updated September 28, 2026, puts the two stitching methods in different packages: field-based stitching needs Select or higher, graph-based stitching Prime or higher. Licensing a method does not mean a company’s data can be matched with it.
The second constraint is people. Buyers describe a niche skill set, implementation partners, and analysts they have to hire before the product earns its price; the hospital system above put the gap down to not having an analyst.
Want a review of your own stack?
Get my review →Should you buy customer journey analytics?
Buy it for a question that needs the cross-channel join — offline sales, call-center contacts, campaigns across several channels — and only once you know how those sources will be joined to a person. If the question is about one site or app, web or product analytics already answers it.
Our recommendation, not a practice buyers describe as a method: start from a business question that needs several channels, such as whether a campaign exposure led to a visit, a support call and then a store purchase. Before the first demo, list the sources and the identifier that links each one, what will stay anonymous, and what consent and governance the join needs. Then ask the vendor to stitch a known set of your own customers, including some with incomplete or conflicting IDs, across web, app and one offline source, and reconcile the result against your source records: how much stays unmatched, how late events arrive, whether the journeys are plausible, and which stitching package the result needed. If you are upgrading from Adobe Analytics, treat it as a new data and reporting implementation rather than a version change: ingestion, schemas, connections, data views, training and a period of parallel reporting, and decide in your own environment which reports must exist before Adobe Analytics is switched off.
Price the whole arrangement: the licence and its data-volume allowance as the new product counts it, the Experience Platform capabilities and ingestion it depends on, the package that carries the stitching method you need, engineering and partners, ongoing data quality, report migration and training. Test the export you would need if you changed tools later. What the interviews do not show is that the companies that bought it learn more than those assembling the same view from other tools; they show that both routes stall at the same place, joining the data.
Last, a cross-channel report is not proof of incremental impact. Where the question is causal, such as whether a campaign produced the sales that followed it, our suggestion is to pair attribution reporting with experiments or another incrementality method; see what incrementality testing is.
For the analytics tools around it, see Adobe Analytics alternatives, Adobe Analytics vs. GA4 and what product analytics buyers wish they’d known; for the Adobe products it reads from, the Adobe Experience Cloud stack.
Common questions
What is customer journey analytics?
Customer journey analytics is the analysis of how people move across a company’s channels — website, app, email and push, call center, stores and other offline touchpoints — using event data connected to the same person where the identifiers allow, so a team can follow paths, segment and attribute outcomes across the sequence rather than one site or app at a time. The view is only as complete as the data collected and the identities that can be reliably matched, and attribution reporting assigns credit without by itself showing cause. It reports on journeys; it does not send messages. In buyer interviews the phrase usually names one product, Adobe Customer Journey Analytics.
What is Adobe Customer Journey Analytics (CJA)?
Adobe Customer Journey Analytics, or CJA, is the analytics product Adobe documents as its next-generation analytics solution. It runs Adobe’s Analysis Workspace on data held in Adobe Experience Platform, and joins datasets such as web and app events, call-center records and point-of-sale data through a connection, with stitching that connects events to a person where an identifier allows. The datasets it reports on must be in Experience Platform. Existing Adobe Analytics customers can add it to a Select, Prime or Ultimate contract, Adobe also sells it as a standalone product, and the package sets features such as which stitching methods are available. Buyers here rate Adobe Customer Journey Analytics 7.8/10.
What is the difference between Adobe Analytics and Customer Journey Analytics?
Adobe Analytics measures a website or app from the tags on it. Customer Journey Analytics reads datasets in Adobe Experience Platform, so it can join digital behaviour with call-center, CRM, store and other offline data around one person. Adobe’s documentation also lists technical differences: dimensions and metrics with no stated limit in place of Analytics’ eVars, props and events, and historical data that can be corrected. Its upgrade guidance describes a new data-collection implementation rather than a version change, and buyers part way through describe months of work.
Is Adobe Analytics being replaced by Customer Journey Analytics?
Not on any announced date. Adobe treats Customer Journey Analytics as the upgrade path from Adobe Analytics and still documents and updates Adobe Analytics. Its upgrade guidance, updated November 6, 2026, recommends keeping Adobe Analytics running in parallel while the new data is validated, and its documentation, as of November 2026, gives no end-of-life date and describes switching it off as a choice made once a team trusts its new data. Several buyers here nonetheless describe the move as one Adobe is steering them toward, and upgrading from Adobe Analytics is how most companies in these interviews came to the product. That is a migration decision, not evidence that every Adobe Analytics customer must replace it.
What is the difference between customer journey analytics and journey orchestration?
Customer journey analytics measures journeys; journey orchestration runs them. Orchestration tools such as Adobe Journey Optimizer decide and send the next message, while journey analytics reports on what customers did across channels, including how those journeys performed. Buyers keep the two apart: one describes using its customer data platform for segmentation and its journey analytics tool only for analysis.
Which tools do buyers use for customer journey analytics?
Adobe Customer Journey Analytics, rated 7.8/10, is the product buyers name for it. Companies without it cover parts of the job with other tools: Amplitude, Mixpanel and Heap for journeys inside a product, Contentsquare, Quantum Metric and FullStory for paths and replays on a site, path exploration in Google Analytics 4, and Tableau or Power BI on a data warehouse to join offline data. Those tools are rated for their own jobs, not as journey analytics.
How hard is customer journey analytics to implement?
Harder than the licence suggests. The work buyers describe is bringing in each channel’s data and joining it to one person, which the tool leaves to them, plus finding analysts who know the product. Stitching connects only the records whose identifiers can be matched, and the method available depends on the package. Adobe’s own upgrade guidance from Adobe Analytics recommends a new Web SDK implementation, the Analytics source connector to keep historical data, a schema and a data view, a period of running both tools side by side and three to six months for users to learn the differences.
A tech stack review, powered by the buyers who've been there
What matters most to you, a shortlist for your stack, and the next steps to take — built from hundreds of verified buyer interviews.
Get my stack reviewFree · no password · your answers are anonymized before they inform research like this.