Track exactly what matters.
Every site has moments that matter — a booking made, an order placed, a quote requested. Track them with one line and LogClip ties every event back to the session behind it.
The moments you named yourself.
2 stops, each one a real screen from the console.
Four events, and what each one reached
Count sits beside sessions because the ratio is the tell: an event firing far more often than it reaches people is firing twice a visit. Each row carries when it last fired, which is how a broken integration announces itself.
Promote an event to a win
A conversion is just a signal flagged as success — built from an event name, a page, or a custom rule. However you make it, it becomes the conversion rate everywhere, the last step of a funnel, and the value in revenue.
Everything under events
Custom events your site reports with a single LogClip.track() call — counts, reach, conversion and trends, tied back to replay.
One line to report
LogClip.track('add_to_cart', { sku, size }) from anywhere in your code — a name and whatever properties matter.
Count, sessions, reach
How many times each event fired, how many sessions it reached, and events per session for the site as a whole.
Tied to a conversion
Where an event is the conversion — or part of a rule that is — its conversion share sits in the table.
Trend and last seen
A sparkline per event across the window and when it last fired, so a broken integration shows as a flat line.
Events per day
The site's total across the window, for the days that were quiet and the days that weren't.
In every recording
Each event sits on the replay timeline at the moment it fired, with its properties in the inspector.
Filter recordings by event
Any event name is a filter on the recordings list and a condition in a signal or a funnel step.
Clicks, errors and requests come free
You don't need custom events to get value — they're for the business moments only you can name.
identify() alongside
Stitch events to a known user with one call; the visitor card and Accounts read from it.
Why it matters.
One line to instrument
LogClip.track('upgraded', { plan }) is all it takes — counts, reach and trends appear instantly.
Events meet replay
Every event links to the sessions that fired it, so a number becomes a watchable story.
Conversion built in
Mark any event as a win and its conversion rate is tracked across the whole platform.
Minutes, not quarters.
Name the moment
checkout_started, plan_upgraded, video_played — one call where it happens.
Read the table
Count, sessions reached, conversion share, trend and last seen for every event.
Use it everywhere
The same name filters recordings, builds a funnel step and defines a conversion.