Traffic
Exit
Also called page exit.
Exit is the last pageview recorded in a session. Every session has exactly one, whether the person was satisfied, interrupted or blocked.
How it is measured
The tool marks the final pageview of each session as an exit. Count exits per URL for a period. The exit does not require any action, so it is observed only after the timeout passes and no later hit arrives.
Tarsier cannot know a tab was the last one until no ping or pageview follows, so today's exits are provisional. The pagehide ping helps, but a closed laptop lid still leaves the last page to be settled by silence.
Worked example
On a conference site, 840 sessions in a week end on /schedule. That looks alarming until the team notes that the schedule is the final page people need before attending. They saw it, took a screenshot and left.
The /register page has only 90 exits but 55 of them occur at the payment form, and there the exits are a real leak.
How it differs
An exit is any last page. A bounce is a single-page session that ends the same way. Exit page is the report that lists where exits occur. Exit rate turns the count into a share of that page's pageviews.
Common errors
Reading every exit as a failure. Treating exits on thank-you pages as problems. Looking at counts without page volume. Ignoring the funnel position. Forgetting that mobile app switching ends sessions.
In practice
Sort exits by pages that sit in the middle of a funnel, not at the end. Treat exits from a confirmation, a receipt or an outbound-heavy page as normal. Read each cluster against the page's purpose.