What the purchase journey report shows
The report lays out the standard shopping sequence as a set of steps — arriving on the site, viewing a product, adding it to a basket, entering the checkout, and completing the order — and shows how many people reached each one. Between every pair of steps it shows the drop-off, which is where the useful reading happens.
It is built from the ecommerce events your site already sends, so the steps only appear if the matching events exist. A shop that fires purchases but never fires the begin checkout event will see a gap in the middle of the funnel that looks like a catastrophic loss of customers and is really just a missing tag.
Why it matters
A single conversion rate tells you that something is wrong without telling you where. The journey report replaces that with a location. Losing people between the product page and the basket is a merchandising and pricing problem. Losing them between the basket and the checkout is usually delivery cost or a login demand. Losing them inside the checkout is friction, payment or trust. Each has a different owner and a different fix.
It also protects you from spending in the wrong place. Buying more traffic when the leak sits in the checkout means paying to pour water into a bucket with a hole in it, and the report is the cheapest way to see the hole before the budget conversation starts.
Where it misleads
The biggest drop is always at the front, because most visitors were never going to buy anything. Treating that step as a failure sends teams chasing an impossible target instead of the steps further down, where the people who did show intent are being lost.
The sequence is also idealised. Real shoppers compare on other sites, return days later, buy on a different device or start again from a search. The report tidies this into a straight line, so the raw counts understate how many journeys actually completed. Read the shape and the relative drops rather than treating any single figure as exact. Segmenting by device matters especially in Nepal, where mobile traffic dominates and the checkout that works on a laptop is often the one nobody can finish on a phone.
How to act on it
Verify the funnel before you trust it. Walk through a purchase yourself while watching the events fire, and confirm every step in the report corresponds to something real. A missing step is a tracking job, not a conversion problem.
Then pick the single worst drop that sits after a shopper has shown intent, and work only on that. Segment it by device, by traffic source and by new against returning visitors, because the site-wide funnel usually conceals one segment doing badly. Make one change, wait for enough orders to judge it fairly, and look again. Working step by step also gives you something honest to report: not that sales went up, but that a specific stage stopped losing people, which is a claim you can actually defend.
