A session record is a sequence, not a summary. Each entry carries a timestamp, a path and the fields the tracker could observe at that moment. The order matters before any total does.
What the record holds
Page and route, referrer, viewport and device class, the events the page sent, and the errors it raised. The record is written on the server, no cookie is set, and the tracker does not ask the visitor for a name or an email.
Order is the first fact
Read the sequence before the totals. A funnel step that looks healthy in aggregate can hide an exit one page earlier. A page with a long dwell time can be a page nobody understood.
Every number has a timeline behind it, or it is only a number.
Code and data
The snippet exposes one call for route changes and one for custom events. A post that ships code carries the smallest version that runs, so the example below is the whole call, not an excerpt.
js, after the tracker loads
frioda.track("checkout_start", {
plan: "pro",
path: location.pathname
});
Corrections
A correction is appended to the post with a date. The original sentence stays visible, because a silently edited post teaches nothing.