> For the complete documentation index, see [llms.txt](https://docs.getuntitled.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getuntitled.ai/custom-connections/schema-overview/sessions-table.md).

# Sessions Table

The Sessions Table captures data on each visitor's session, including session duration. A session concludes when there has been no activity by the user for 30 minutes. See table structure below.

{% hint style="info" %}
\*For users who want to parse results by match type—similar to how they’re displayed in the front-end application—use the `File Type` column values as your delimiters.
{% endhint %}

## Table Structure

| Column                   | Description                                                                                                                  |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| hem                      | Hashed email (SHA256) associated with a tag fire                                                                             |
| tag\_id                  | The ID associated with the tag                                                                                               |
| \***file\_type**         | File type associated with the tag fire (B2B, B2C, PTE)                                                                       |
| session\_id              | The ID associated with a session. The session ends when there has been no activity for 30 minutes                            |
| session\_start           | Timestamp (YYYY-MM-DD HH:MM:SS.sss) of when the session started                                                              |
| session\_end             | Timestamp (YYYY-MM-DD HH:MM:SS.sss) of when the session ended                                                                |
| est\_session\_duration   | The estimated session duration in seconds. This is estimated because we don’t know how long someone was on the last page for |
| entry\_url               | The first URL someone visited in a session                                                                                   |
| exit\_url                | The last URL someone visited in a session                                                                                    |
| total\_pages\_visited    | The total number of pages someone visited in a session                                                                       |
| unique\_pages\_visited   | The unique number of pages someone visited in a session                                                                      |
| un\_processed\_timestamp | Unix timestamp of when the record was processed                                                                              |
| un\_updated\_timestamp   | Unix timestamp of when the record was last updated                                                                           |


---

# 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.getuntitled.ai/custom-connections/schema-overview/sessions-table.md?ask=<question>&goal=<user_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.