> 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.md).

# Schema Overview

The database schema is comprised of three tables: Visitors, Sessions and Pages. They are joined via `hem` and `session_id` respectively. 

## Database Tables

* The [Visitors Table](/custom-connections/schema-overview/visitors-table.md) stores comprehensive information about individuals who have visited a website with the Distilled tag installed. B2B, B2C, and PTE records are consolidated in this table view.
* The [Sessions Table](/custom-connections/schema-overview/sessions-table.md) captures data pertaining to each visitor's session, including session duration. A session concludes when there has been no activity for 30 minutes. In the sessions table, you can find the column that provides the match type for a visitor record. This column is titled [file\_type](/custom-connections/schema-overview/sessions-table.md#table-structure) and will indicate whether a visitor is a B2B, B2C, or PTE record.
* The[ Pages Table ](/custom-connections/schema-overview/pages-table.md)records details about the pages viewed by individuals during their session.
* The [Buyer Intent Table](/custom-connections/schema-overview/buyer-intent-table.md) records details about the modeled intent score of resolved website visitors. 

### Entity Relationship Diagram

Referencing the provided Entity-Relationship Diagram (ERD) below, you can visualize how these tables can be joined together to provide a holistic view of user interactions on your website.

<figure><img src="/files/19ZHXQXwuPylVHJ9R2nS" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.getuntitled.ai/custom-connections/schema-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.