> For the complete documentation index, see [llms.txt](https://documentation.freshpaint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.freshpaint.io/readme/setting-up-identify/designated-identify-properties.md).

# Designated Identify Properties

Some destinations treat certain identify properties specially. As an example, some destinations treat the `email` property as the email to use when sending an email to a user. This page lists the destinations that accept designated properties and the properties they accept.

## Customer.io

| Property | Description                                                   |
| -------- | ------------------------------------------------------------- |
| `email`  | This is the email customer.io will use when sending an email. |

## Fullstory

| Property      | Description                                         |
| ------------- | --------------------------------------------------- |
| `displayName` | This is the name to show for the user in FullStory. |
| `email`       | This will show up as the user's email in FullStory. |

[See the FullStory docs on identifying users in FullStory for more information.](https://help.fullstory.com/hc/en-us/articles/360020828113)

## HubSpot

| Property | Description                                                                                                        |
| -------- | ------------------------------------------------------------------------------------------------------------------ |
| `email`  | HubSpot requires you send the `email` property. The value of this property will be used as the email for the user. |

## Iterable

| Property | Description                                                                                           |
| -------- | ----------------------------------------------------------------------------------------------------- |
| `email`  | In order to email a user in Iterable, you must first send an identify call with the `email` property. |

## Vero

| Property | Description                                                                                       |
| -------- | ------------------------------------------------------------------------------------------------- |
| `email`  | In order to email a user in Vero, you must first send an identify call with the `email` property. |

## Gainsight

<table data-header-hidden><thead><tr><th>Property</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>Property</td><td>Description</td><td></td></tr><tr><td><code>Email</code></td><td>Gainsight requires an email field for each identify call.</td><td></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 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://documentation.freshpaint.io/readme/setting-up-identify/designated-identify-properties.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.