Guide
Inspect browser sessions
Use session context and chronology to verify where and when browser behavior was observed.
Last reviewed September 12, 2026
Sessions overview
Sessions preserve a runtime view of what SiteWall observed for one browser context, including environment, resources, timing, API use, network requests, global variables, and event chronology. Use the time range and query controls to narrow the list before opening a session.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Runtime records | Open a representative session and record its page, time, browser context, and observed resources. Use it to establish that the behavior occurred in that captured journey, not that it occurred for every visitor. |
| Context | Review context in the active project, follow the linked source record, and preserve its observation, interpretation, and owner decision context. |
| Filters | Narrow the current project’s records before interpreting totals or opening a detail view. |
Inspect a session
Session Analysis connects environment and performance summaries to a chronological event record. Read session start, response and execution timing, errors, API use, requests, globals, event listeners, and consent decisions in order, then pivot to the linked resource when deeper code or policy context is needed.
Procedure
- 1.
Open the correct project and page
Use the project selector to choose the website you intend to review, then open Sessions in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Define the observation window
Record the page or journey, browser and consent state, test time, and active filters. Note the visible counts before narrowing the view so an empty filtered result is not mistaken for missing collection.
- 3.
Timeline
Compare the first, last, and event timestamps with the investigation or reporting window. These values describe SiteWall observations for the active project and do not establish activity outside the captured period.
- 4.
Resources
Confirm the URL or domain, provider association, first and last observation, and the project in which the entity was recorded. Open the linked detail record; a display name or enrichment label is not proof of ownership or approval.
- 5.
Timing
Compare like-for-like sessions and treat captured timing as context, not a complete causal proof.
- 6.
Environment
Open a representative session and record its page, time, browser context, and observed resources. Use it to establish that the behavior occurred in that captured journey, not that it occurred for every visitor.
- 7.
Relationships
Trace the relationship from the loading resource to the observed destination or capability. Confirm required service endpoints and regional behavior in representative journeys before restricting access.
- 8.
Confirm the record against known traffic
Refresh the view, remove unintended filters, and compare the provider, resource, relationship, or session with the page and journey you exercised. Follow the linked detail record before drawing a conclusion.
- 9.
Record the scoped observation
Preserve the record link, project, page or journey, filters, observation window, reviewer, and the next record to inspect. State untested conditions as coverage gaps.