The product
Events
One recorded thing. This is the line on a timeline, and the unit a plan counts.
What an event is
An event is one recorded thing: a page view, a click, an HTTP request, an error, or a log line. A typical session is 20 to 60 events.
The browser SDK records what happened in the page. The server SDK records the requests that page made. Both use the same project key, which is why they share a timeline. Passwords, tokens, cookies, card numbers, and authorization headers are removed inside your app, before the batch leaves the process. The privacy page lists every rule, and Project, Privacy is where you name extra fields to drop.
What the timeline shows
Open a session. Each row is an event, in order, with the time. A web badge is the browser. An api badge is the server. A failing row is marked. Click a row to open the raw payload.
That timeline is the log. There is not a second log viewer. Search finds the person or the issue. The timeline is where you read what they hit.
What a plan counts
Plans count events per month and keep them for a set number of days. An event with no person still counts. Skipping identify() does not skip the bill. It only means the event is not on a journey.