Customer Journey Mapping From Visits to a Purchase

What Should a Customer Journey Map Show?

A useful map shows the customer’s task, the steps you can substantiate, the questions that remain and the action your team will take. A page sequence is one layer of that map. It does not reveal someone’s thoughts, satisfaction or reason for buying.

Nielsen Norman Group’s journey-mapping guidance combines the person, scenario, phases, actions, thoughts and opportunities for improvement. Apply that distinction when using analytics: clicks describe recorded behavior; interviews and other customer research help explain the experience.

For a marketing team, the first question might be whether an article helps readers reach a purchase. For an agency, it might be where visitors from one campaign stop being recorded. Choose that question before collecting screenshots. My recommendation is to map one buying task well before building a wall-sized map of the entire business.

1. Choose One Audience and One Outcome

Choose a specific task, such as a new visitor comparing your product and completing a first purchase. Keep a lead submission, a first payment and a renewal as separate outcomes. Their routes and timeframes can be different.

Write down the audience, website, reporting dates and outcome. Use the reporting date controls to keep the website’s time zone consistent, especially when comparing Today with another tool’s calendar. A short period helps inspect recent behavior; a longer one can reveal less common routes.

1. Name the audience without assuming identity, for example visitors arriving from paid search.
2. Choose the observable outcome, such as a recorded new purchase or a tracked lead goal.
3. Write the question you want the map to answer, such as which pages appear before that outcome.
4. Keep the scope fixed when comparing paths with and without that outcome.

Shopify’s customer journey guide separates the wider experience across touchpoints from the analytics used to inspect it. Keep offline conversations and post-purchase support in a broader map when they matter, rather than expecting a website report to contain them automatically.

2. Find the Recorded Pattern in Attriboo

Open Journeys & Funnels → Journeys. Start with Flow diagram, then choose Channel, Source, Starting page or Outcome to investigate the group you defined. These controls narrow Journeys; do not assume every dashboard card has switched to that same group.

Read the coverage line above the flow before interpreting its largest connection. Top paths limits what is drawn, while the totals can include more matching visits. Increase Steps to see more of the displayed routes. More steps recorded means the route continues beyond the visible depth.

A wide connection means many visits followed that transition. It does not establish that the page persuaded those visitors or caused their purchases. Focus or tap a connection to inspect its counts, then use Recorded paths when you need a complete sequence rather than shared nodes.

The Journeys guide explains the counting rules: a visit ends after 30 minutes without recorded activity, and the report includes visits with a page view inside the selected dates. Source and channel describe each visit’s first recorded entry; changing the attribution model does not rewrite those labels.

3. Read a Buying Route Without Double-Counting It

Switch to Recorded paths and select With a new purchase under Outcome. Read one row from left to right. Keep its Visits, Visitors, New purchases and Linked value together: they describe different quantities, even when their numbers happen to match.

In the highlighted example, /pricing → /signup → /checkout → Purchase appears in two visits, with two visitors and two new purchases totaling $698 in linked value. That is one grouped route containing two purchases. It is not four separate revenue totals because the route has four steps.

Linked purchase value is before refunds and fees, excludes renewals and is not multi-touch source credit. Attriboo links an eligible new purchase once to the same visitor’s latest visit with preceding activity within 30 minutes. Read the revenue report for refund-adjusted totals; do not substitute the journey value into a refund-adjusted total.

The same purchase can appear in the statistics for several nodes or connections along its route. Do not add those step values. Use the route row or the appropriate report total for aggregation. For credit allocation across sources, compare attribution models separately from the sequence.

4. Mark Observations, Assumptions and Missing Steps

Label each map entry by its evidence. An observed pricing visit, a customer saying they asked a colleague and your team assuming they compared prices are three different statements. Keeping them separate makes the map useful when another person challenges the conclusion.

Use the worksheet for a small review, then put one owner beside the first unresolved check. Its counts describe the steps you entered, not the percentage of customers you tracked. A spreadsheet works just as well for a larger map if you preserve the evidence labels and sources.

No next step recorded means there is no later recorded step in that visit. It does not prove the person left in frustration. They may have paused, used another device or reached an untracked page. First check the relevant page and tracking handoff, then ask a research question the evidence can support.

5. Check Checkout and External-Link Handoffs

Check the boundary where the website sends someone elsewhere. A checkout link click and a confirmed payment are separate records. Install website tracking and connect the supported payment provider, then verify the matching flow used by your checkout.

For an affiliate site, an outbound step can show that a visitor clicked an external link, including a link opened in a new tab. The destination is recorded as its host and path without query parameters or fragments. It does not confirm a sale or commission at Amazon or another merchant, and an internal redirect link is not automatically resolved to its final destination.

If an outbound click appears before Purchase in a recorded route, read those as separate observations: an external click occurred, and an eligible payment was linked under the report’s rules. Do not attribute the payment to the external merchant just because the two steps are adjacent.

Older payments do not recreate earlier visits, and missing page history cannot be recovered by drawing a line between two known events. For traffic without an observed purchase, use the no-sales diagnostic to separate a collection problem from a page or offer problem.

6. Turn the Map Into One Useful Test

Finish with a change you can test and a result you can review. If readers repeatedly move between a product page and pricing, check whether the price or plan distinction is clear. The pattern suggests a question; it does not supply the answer.

Compare a similar audience and period after the change. Note other changes that could affect behavior, such as a promotion or a different traffic mix. A larger purchase count after an edit is an observation, not proof that the edit caused the increase.

Use a funnel when you have a defined set of steps or a conversion question to monitor. Use Journeys to discover the recorded routes people actually took. Keep the definitions in the funnel guide beside the report so the team does not treat differently defined counts as interchangeable.

A useful client update can be short: “We saw this route, this part is still unknown, and this is the check we’ll run next.” You do not need to draw every possible path before improving one confusing handoff.

For products where trials convert weeks later, the SaaS marketing attribution guide explains how to check the trial account, billing reference and later first payment before comparing source credit.

Common questions