Customer Journey Analytics: A Guide for Online Stores

A customer rarely buys on the first visit, and most reports still describe visits rather than customers. Customer journey analytics is the discipline of joining those visits into one path per person and measuring what the path led to. This guide explains what it is, what data it needs, which tools do it, and how an online store can start without an enterprise budget.

The short answer: customer journey analytics joins visits to outcomes, and Arktis does it for stores

Customer journey analytics is the practice of connecting every recorded interaction a person has with a business, across sessions and channels, into a single sequence, then analysing those sequences against an outcome such as an order. Journey mapping draws the path you think customers take. Web analytics counts sessions and pages. Customer journey analytics measures the paths people actually took and which of them ended in revenue.

The phrase is also a product name. Adobe Customer Journey Analytics is an enterprise product that runs on Adobe Experience Platform, sold in four packages and priced by quote. If that is what you searched for, the section on Adobe below covers it from Adobe's own pages.

For an online store, Arktis is the clear winner. It captures the ad click identifier and UTM tags on landing, holds them against the visitor across sessions, matches Shopify orders and Stripe customers back to that visitor, and shows how many sessions converting visitors made and the median days from first visit to conversion, next to session recordings, on Growth and above, of visitors who converted, filtered by source. Plans are $49, $149 and $349 a month, with a 7-day free trial on Growth.

Key takeaways

Customer journey analytics needs three things: an identity that persists across sessions, a record of each touchpoint with its source, and an outcome joined to the same identity. Adobe Customer Journey Analytics is a specific enterprise product and is far more than a store needs. Product analytics tools trace paths through an app well and say little about which campaign paid for the customer. A store can start with one outcome, the order, and three numbers: the share of orders that took more than one session, the median days to convert, and the gap between first-touch and last-touch source.

What is customer journey analytics?

A journey is the ordered list of everything one person did before, during and after buying: the ad they clicked, the product pages they opened, the email they came back from, the checkout they finished. Customer journey analytics collects those steps for every visitor, attaches them to one identity, and asks questions of the whole set rather than of single sessions.

The unit of analysis is what makes it different. A session report says 4,000 visits came from Instagram yesterday. A journey report says that of the people who first arrived from Instagram this month, a certain share came back within a week, and those who came back by email converted at a higher rate than those who came back by search. The second statement needs the same person recognised on each visit.

If journeys are new to you, our introduction to understanding the complete customer journey walks through one buyer's path across four touchpoints and two devices.

How it differs from journey mapping

Journey mapping is a design exercise. A team writes down personas, stages, touchpoints and emotional states, and draws the route a customer is expected to take. The output is a diagram, and its value is alignment: everyone agrees what the experience is supposed to be. Our step-by-step guide on how to map your customer journey covers that process.

Customer journey analytics is the measurement that tests the map. It works from recorded behaviour, not workshop notes, and it can contradict the diagram: a stage drawn as linear may loop, and a touchpoint nobody listed may precede many orders. A map without analytics is a hypothesis, and analytics without a map is a pile of paths with no question attached.

How it differs from web analytics

Web analytics is organised around sessions, pages and channels. It answers how much traffic arrived, from where, and what share converted in that visit. That is the right tool for judging a landing page or a traffic spike.

It struggles with anything that spans visits. A purchase that takes three sessions over nine days appears as three sessions, two of which did not convert, and the credit goes to whichever source the tool's attribution rule prefers. Adobe draws the same line between its own products: its pricing guide positions Adobe Analytics for website and mobile app performance, and Customer Journey Analytics for the complete, cross-channel journey over time.

Behaviour tools sit beside both. Heatmaps and session recordings show what happened inside one visit in detail, which is covered in our guide to visitor behaviour analytics. Journey analytics tells you which visits are worth watching.

The data customer journey analytics needs

The first requirement is identity across sessions. Something has to say that Tuesday's visitor is Friday's buyer. On a website that is a first-party identifier kept in the visitor's browser, strengthened by an email address once the person logs in, subscribes or checks out. Enterprise suites go further and join web, app, call centre and in-store records on a shared person ID.

The second is touchpoints with their source. Each visit needs to carry where it came from: an ad click identifier, UTM parameters or a referrer. A journey made of visits with no source is a list of page views. Our guide to customer journey touchpoints covers how to inventory them.

The third is outcomes. The order, with its value, has to land on the same identity as the visits. This is the step most setups miss. A path that ends at a thank-you page view is weaker than a path joined to the order record in Shopify or Stripe, because the order record carries the revenue, the customer and the repeat purchases that follow.

The questions it answers for a store

How many visits does a purchase take? If most orders complete in one session, your ads and landing pages carry the sale. If most take three, the return visit is where money is won or lost, and remarketing and email deserve the attention.

How long does it take? The median days from first visit to order sets the window in which a campaign should be judged. A campaign judged on day two will look worse than it is if your typical buyer returns on day six.

Which first touches produce eventual buyers? Last-touch reports favour brand search and email, the channels people use to come back. Comparing first-touch and last-touch source for the same orders shows which channels introduce customers and which collect them, as explained in what is multi-touch attribution.

Which pages show up on the way to an order? Pages that appear far more often in converting paths than in all paths are candidates for more traffic. That is a correlation to test, not a proven cause.

Where do multi-session journeys stall? A visitor who viewed a product twice and never reached the cart is a different problem from one who reached checkout and left. The fixes for each are in our guide to customer journey optimization.

Adobe Customer Journey Analytics, the product

Adobe describes Customer Journey Analytics as its next-generation analytics solution, one that brings Analysis Workspace, its reporting interface, to data held in Adobe Experience Platform. The point is breadth of data. Adobe's documentation says cross-channel analysis lets you combine and report on multiple datasets from different channels, based on a common identifier it calls the person ID, and its product page describes unifying online and offline data and assigning it to a single profile.

It is licensed, not bought off a page. Adobe's product description, effective 25 September 2026, lists four packages, Foundation, Select, Prime and Ultimate, each licensed per million rows of data. Adobe's pricing guide publishes no figures and directs buyers to a tailored quote. Identity stitching, the feature that rekeys anonymous events to a known person, requires the Select package or higher for field-based stitching and Prime or higher for graph-based stitching, according to Adobe's stitching documentation.

It suits an organisation with data in Experience Platform, several channels to reconcile and analysts to run it. If you were looking for the Adobe product, Adobe's Experience League overview in the sources is the place to start.

Customer journey analytics tools by category

Customer journey analytics software falls into four groups, and they answer different questions.

Enterprise journey suites are built for breadth. Adobe Customer Journey Analytics joins datasets across channels. Contentsquare, which owns Hotjar, describes its Journeys capability as showing how customers progress from entry to exit and what makes them come back, with reverse journeys that start from a completed action and look backwards.

Product analytics tools are built around events inside a product. Amplitude's Journeys chart analyses how users convert, or fail to convert, between key transitions. Mixpanel's Flows report identifies the most frequent paths users take to or from any event. PostHog's user paths follow users through a product to find the biggest drop-offs. All three are strong when the journey happens inside an app after sign-up.

Web analytics offers a lighter version. GA4's path exploration draws user journeys as a tree graph, forwards from a starting point or backwards from an end point, and it costs nothing if you already run GA4.

Store attribution tools start from the order. Arktis sits here. It records the first-touch source on each visitor, holds ad click identifiers and UTM tags across sessions, and joins Shopify orders and Stripe customers to the visitor. Its Paths page splits converting visitors into those with one session and those with several, reports their average session count and the median days to convert, shows what eventual converters saw on their first visit, and ranks pages and page sequences by conversion impact. The Ads Analytics dashboard lists the journeys of visitors who touched more than one channel before converting. On Growth and above you can watch the session recordings of visitors who converted, filtered by source.

How to start small

Pick one outcome. For a store it is the order. Leave newsletter sign-ups and add-to-carts for later, as described in our guide to customer journey stages.

Make every visit carry a source. Tag the links you control, in emails, social posts and ads, so that a returning visit does not arrive as Direct. Our UTM parameters best practices cover naming.

Get identity working before analysis. Check that a visitor who returns two days later is recognised as the same visitor, and that the order lands on that visitor rather than on a new one.

Then read three numbers each month: the share of orders that took more than one session, the median days to convert, and the difference between first-touch and last-touch source for the same orders. Take an example store where 60 percent of orders are multi-session and the median is five days. That store should not judge a campaign on same-day revenue, and it should check what its returning visitors come back through.

Finally, watch a handful of journeys end to end. Numbers show which path is common, and a recording shows why.

Pitfalls

Identity gaps come first. Cleared browser storage, a second device or a private window each start a new visitor, so journeys look shorter than they are. Treat any sessions-to-convert figure as an estimate.

Survivorship is the second. Paths of people who bought say nothing about why others did not. Always compare converting paths with all paths.

Too much detail is the third. Group pages into types, such as product, collection, cart and checkout, before reading path diagrams.

Retention is the fourth. If your tool keeps 30 days of data and your buying cycle is 45, the first touch falls off the end. Check the retention on your plan against how long your customers take.

Consent is the fifth. Joining sessions to a person is processing personal data, and in the EU both the identifier kept in the visitor's browser and session recording generally need the visitor's consent. Build the consent flow before the analysis.

Where Arktis fits, and where it does not

Arktis is ours, so weigh this accordingly. It is built for one site and one question: which source and which visits led to this order, and how each campaign converts. Its identifier lives in the visitor's browser, so a person who browses on a phone and buys on a laptop is recorded as two visitors, and it has no shared person ID across web, app and offline data of the kind an enterprise suite stitches. It does not ingest call centre, in-store or CRM data. Plans list 7, 30 and 90 days of data retention on Starter, Growth and Scale, which is short for a long buying cycle.

Conversions are counted per UTM campaign and per ad platform, and Meta spend syncs per campaign through a direct connection; spend for other platforms is entered manually per platform and period. Arktis has no A/B testing, no surveys and no heatmaps. If the journey you care about happens inside a logged-in app, a product analytics tool is the better fit, and if it spans stores, apps and call centres, that is what Adobe built Customer Journey Analytics for.

To see journeys on your own orders, start the 7-day Growth trial, or compare the tiers on the pricing page. For the funnel view of the same data, see ecommerce funnel analysis, and to see how the answer changes by model, try the free attribution model comparison tool.

Sources

Adobe Experience League: Customer Journey Analytics overview, Adobe's definition and the role of Analysis Workspace and Experience Platform, accessed 1 October 2026

Adobe: Customer Journey Analytics product description, effective 25 September 2026, the four packages and the per million rows of data licence metric, accessed 1 October 2026

Adobe CX Analytics pricing guide, no published prices, tailored quote, and the positioning of Adobe Analytics against Customer Journey Analytics, accessed 1 October 2026

Adobe Customer Journey Analytics product page, unifying online and offline data into a single profile, accessed 1 October 2026

Adobe Experience League: Stitching overview, cross-channel analysis on a person ID and the package requirements for stitching, accessed 1 October 2026

Contentsquare: Journeys, entry to exit progression and reverse journeys, accessed 1 October 2026

Amplitude docs: Journeys, what the Journeys chart analyses, accessed 1 October 2026

Mixpanel docs: Flows, most frequent paths to or from any event, accessed 1 October 2026

PostHog docs: User paths, following users through a product to find drop-offs, accessed 1 October 2026

Google Analytics Help: Path exploration, user journeys in a tree graph, forwards and backwards, accessed 1 October 2026