Find what blocks the buy.
Every funnel shows you where people leave. LogClip is the only one that shows you why — overlaying the errors, rage clicks and slow loads blocking each step.
From the first page to the purchase.
3 stops, each one a real screen from the console.
Type the flow, read the drop
Landing page, product, add to cart, checkout, purchase — typed into the builder as three page paths and two event names, no tagging first. Each bar also carries how long that step took, so a stage that leaks slowly reads differently from one that loses people outright.
What the sessions that dropped ran into
Beside the funnel, the friction those same visitors hit, counted and ranked — the list to work through, in order. Each signal is also a filter on the recordings, so a count is one click from the visits it stands for.
The same builder, pointed somewhere else
A funnel is only as good as the question. These three took about fifteen seconds each, and the last one is the kind most funnel tools cannot ask at all: a step that matches any error, wherever it came from.
Cart to checkout to paid — the single worst drop anywhere in the flow.
Everything under funnels
Watch how many visitors make it from arriving to converting — and exactly which friction signal gets in the way.
Four kinds of step
A page view by path, a custom event by name, any error at all, or either — matched on name or path. Mix them freely in one funnel.
Two to eight steps
Add, remove and reorder as you go. There is nothing to save and nothing to schedule: the funnel recomputes on every change.
Ordered, not merely present
A session counts at a step only if it did the earlier steps first, in sequence — so out-of-order visits never inflate the middle.
Built from what's already captured
Page views and events are recorded on every visit, so a funnel over the last 30 days computes the moment you type it.
Drop at every step
The count, its share of everyone who started, and how many fell out since the step before — as a number and as a percentage.
The time between steps
How long each hop actually took, so you can tell a step people hesitated over from one that stopped them dead.
What's blocking conversion
Errors, network failures, rage clicks, slow loads and dead clicks over the same sessions, ranked by how often they occur.
The headline numbers above it
Sessions, conversion rate, average time on site and every friction signal counted — the four numbers asked for first.
Conversions from a rule or a line of code
Mark the win with LogClip.conversion() or a signal rule; funnels, revenue and insights all read the same mark.
Why it matters.
Drop-off with a reason
Beside every funnel, the friction those same sessions hit: errors, failed requests, slow loads, rage and dead clicks, ranked.
How long each step took
Every step carries the time it typically took to reach it, so a stall reads as a gap and not merely as a shorter bar.
An answer while you type
Steps recompute on every change over the whole 30 days. Ask a question, change your mind, ask a better one.
Minutes, not quarters.
Type the steps
A path for a page view, a name for an event, or Any error for a step you can't name. Two to eight of them.
Read the drop
Each step shows how many made it, how many didn't, and how long it took them. The widest gap is where to look.
Open the blockers
The panel beside it names what those sessions ran into — and errors, rage, dead clicks and slow loads are filters on the recordings list too.