> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/implementation/headless/user-info/standard-keys.md). # Standard Keys These are standard keys that we save in our **main** ID graph table. These are the keys that can be send to `user` function that do not accept any other custom keys. | Key | Format | Example | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------- | | email | lowercase and no leading or trailing spaces | | | phone | in E.164 format | +14154552670 | | firstName | lowercase with no punctuation. If using special characters, the text must be encoded in UTF-8 format | jane | | lastName | lowercase with no punctuation. If using special characters, the text must be encoded in UTF-8 format | doe | | gender | f for female / m for male | f | | dateOfBirth |

Format is YYYYMMDD, without punctuation.
Year: Use the YYYY format from 1900 to current year.
Month: Use the MM format: 01 to 12.
Date: Use the DD format: 01 to 31.

| 19950521 | | city | lowercase with no punctuation. If using special characters, the text must be encoded in UTF-8 format | fremont | | state | [2-character ANSI abbreviation code](https://en.wikipedia.org/wiki/Federal_Information_Processing_Standard_state_code) in lowercase. States outside the U.S. should be in lowercase with no punctuation, no special characters | ca | | zip | lowercase with no spaces and no dash | 94538 | | country | lowercase, 2-letter country code in [ISO 3166-1 Alpha 2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) | us | | ip | IPv4 / IPv6 | 117.182.233.16 | --- # 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.edgetag.io/implementation/headless/user-info/standard-keys.md?ask=&goal= ``` `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.