Follow the real path.
Real journeys are messy. LogClip maps the actual paths visitors take — the loops, the backtracks, the dead ends — so you can design for how people really move, not how you hoped they would.
Where they went, and where they gave up.
3 stops, each one a real screen from the console.
Anchor a page, follow the ribbons
Ribbon thickness is volume and the red bar is the share that left, so a step that bleeds people is visible without reading a number. Pick any page to re-anchor the whole report on it and follow the flow from there instead.
The page that loses the most people is named first
Every exit page, split by how the session ended — converted, frustrated, or simply gone. An exit is not a failure on a page people leave from happy, and the split is what separates the two. Above it, the same sessions grouped by how often they doubled back.
The paths people actually walked, ranked
Not a model of the journey — the ordered first five pages of real sessions, grouped and scored by how often each route converts. The routes that rarely convert here all end on the same product page, which is a lead rather than a statistic.
Everything under journeys
Follow how visitors actually move through your site — from where they land to where they leave — as a living flow.
Built from page views
Every load and every in-app route change is a page view — pushState, popstate, hash routes included. Nothing to tag.
Where sessions end
Every exit page with the sessions that ended there, split into converted, frustrated and quiet — and the biggest leak named at the top.
Path explorer
Anchor any page and see where visitors went next, step by step, with ribbon thickness for volume and the share that left at each branch.
Before this page
Flip the explorer to see how visitors arrived at a page — the routes into checkout, not just out of it.
Backtracking vs conversion
Sessions banded by how often they double back to a page they already saw. Straight-through visits convert; the ones that keep circling barely do.
Routes that convert — and don't
Actual ordered paths, first five pages, ranked by conversion rate with the session count behind each.
Two to ten steps deep
Set how far the tree runs and how many branches each node keeps; the rest roll into “Other” so it stays readable.
Top pages
Views and distinct sessions per page, with the window at 7, 14, 30 or 90 days.
Left frustrated
Sessions that hit a rage click, a dead click or an error somewhere in the visit and never converted, counted as their own share of the traffic.
Why it matters.
Land-to-leave, page by page
Anchor any page and read the steps either side of it — where visitors went next, or how they arrived in the first place.
Spot the loops & dead ends
See where visitors circle back on themselves in confusion, or hit a wall and bounce — and what that costs you.
Branch by outcome
Every exit is split by how it ended, so the pages that lose buyers are told apart from the ones that finish them.
Minutes, not quarters.
Anchor a page
Pick it in the explorer and the report re-anchors: where they came from, where they went.
Follow the thick ribbon
Volume is width, red is exit. The branch that is both wide and red is the one to fix.
Read the leaks
Where sessions end says which page loses people, and whether they left converted, frustrated or quiet.