> 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/product-overview/untitled-id-tag/visitor-dataset-features/plain-text-email-pte-data-points.md).

# Plain Text Email (PTE) Data Points

<table data-full-width="false"><thead><tr><th>Column</th><th>Description</th></tr></thead><tbody><tr><td>HEM</td><td>Hashed email (sha256 lowercase)</td></tr><tr><td>EMAIL_ADDRESS_LC</td><td>Plain Text match of HEM from visit</td></tr><tr><td>ACTIVITY_DATE</td><td>Max date of Tag fire for period processed</td></tr><tr><td>PROCESSED_DATE</td><td>Date stamp of match process</td></tr><tr><td>EVENT_DATE</td><td>Timestamp (Date/Time) of the tag fire to the millisecond in UTC</td></tr><tr><td>IP_ADDRESS</td><td>IP address associated with the tag fire</td></tr><tr><td>PARTNER_ID</td><td>PID provisioned by Agency from the tag (feature is an aggregate of all PIDs associated the the Agency)</td></tr><tr><td>AGENCY_ID</td><td>AID provisioned by Untitled for Agency</td></tr><tr><td>UNIX_TIMESTAMP</td><td>Unix version of EVENT_DATE</td></tr><tr><td>JSON_HEADERS</td><td>JSON Header from the tag fire</td></tr><tr><td>REF_URL</td><td>Reference URL of the tag fire; last page visited</td></tr><tr><td>REFERER_URL</td><td>URL visited prior to the tag fire (when available), URL the visitor came from</td></tr></tbody></table>


---

# 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/product-overview/untitled-id-tag/visitor-dataset-features/plain-text-email-pte-data-points.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.
