> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/reporting-and-analytics/analytics-workspace/session-explorer.md). # Session Explorer The **Session Explorer** tab is the drill-down to individual journey sessions — the people behind the aggregate numbers. Use it to investigate why specific sessions failed, stalled, or converted. ## Filtering the list The filter bar narrows the table: * **Search** — match on user, visitor id, or outcome reason. * **Journey**, **Status** (active / completed / abandoned / expired), **Outcome** (pending / success / failure), and **Role** (Customer / Partner / CSR / Anonymous). * **Date range** — last 7, 30, 90, or 365 days. Each row shows the user or visitor, the journey, the step they reached (with position in the journey), status and outcome badges, the session duration, and when it started. The list is paginated; use the arrows to move between pages. ## Inspecting one session Click any row to open the **session timeline** drawer. It summarizes the session's status, outcome (and reason), and variant, then shows the chronological timeline — steps entered and completed, actions run and their results, and any recorded events. For the complete record, **Open full session detail** links to the full session page. As elsewhere in Analytics, internal preview sessions and analytics-excluded sessions are omitted from the list. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.peakcommerce.com/product/reporting-and-analytics/analytics-workspace/session-explorer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.