LogClip
Platform/Analyze
Revenue

Put a price on friction.

This is the number that gets the fix approved. LogClip puts a dollar figure on the rage clicks, errors and slow loads your site is suffering — so the fix stops being a debate.

/revenue
Revenue in the LogClip console
Inside revenue

What the visits earned, and what the friction cost.

2 stops, each one a real screen from the console.

The figure

What came in, and what nearly did

The banner is the number for the meeting: sessions that struggled and left, priced at your own average order value. Underneath, where the money came from — every dollar attributed to the conversion that fired it and to the page the visit started on.

Revenue, conversions, average order value and conversion rate
At-risk sessions valued at your own AOV, not an industry figure
Revenue by conversion name and by landing page, exact
/revenue
Revenue — What came in, and what nearly did
The window

Seven days, or ninety

One control at the top and every number follows it. Worth watching what does not move: revenue scales with the window, but average order value barely shifts — which is exactly what makes it a sound basis for pricing the sessions you lost.

/revenue
Revenue — Seven days, or ninety — 7 days

The last week — noisy, and the first place a change shows up.

Everything under revenue

Tie every conversion to the money it brings in — and see exactly how much revenue your UX friction is putting at risk.

01

One call to capture value

LogClip.conversion('purchase', { value: 177.54 }) — amount, revenue, total or price all work too, with an optional currency.

02

Revenue at risk

Sessions that raged, died, errored, hit a failed request or scored 50+ on friction — and left without buying.

03

Revenue over time

Day by day, with the total for the window and revenue per session sitting in the corner of the chart.

04

By conversion

Exact revenue split by conversion name — purchase, upgrade, whatever you called it.

05

By landing page

Revenue attributed to the page the visit started on, so campaigns and entry points show what they earned.

06

Conversions from a rule

A conversion is a signal flagged as a win: build it from events, requests or URLs without code, or mark it from code.

07

Same mark everywhere

Converted sessions carry the badge in recordings, funnels, journeys and audience — one definition of a win.

08

Lost conversions, attributed

Insights' cause cards rank failures by the conversions they cost, using the same conversions.

09

7, 14, 30 or 90 days

Every number on the page follows the window.

Revenue

Why it matters.

01

Revenue at risk, quantified

Sessions that struggled and left without converting, valued at your own average order value and summed.

02

Define a win, any way

A page reached, an event fired, a cart over a threshold — mark it as a conversion and it's counted everywhere.

03

Revenue by source

See which conversions and landing pages actually bring in the money, rather than just the traffic.

How it works

Minutes, not quarters.

Step 01

Send the value

One line where the order completes. No value? The conversion still counts, at $0.

Step 02

Read the split

Which conversion and which landing page the money came from.

Step 03

Price the friction

The at-risk figure is sessions that struggled and left, times what a converting session is worth.