Example: For attribute “Email” will choose “Raw String” |
| Is Required | Mark this attribute as required for the "Business Object" under consideration. By default, this checkbox is unchecked |
| Auto suggestion | This field is only enabled when the data type of the attribute is string. For other data types that are not supported, this option will be disabled.
By default, this checkbox is unchecked
|
| Enable Data Encryption | Mark the data encoding for this attribute. By default, this checkbox is unchecked |
| Is Identity Attribute | If checked, the generated attribute will be marked with an identifier. Fields that are considered Identity are fields that can contain information such as: phone, email, device ID, ... Only "Business Object" is Customer and Visitor when creating Custom Attribute, there is a checkbox "Is Identity". By default, this checkbox is unchecked |
### 2. Download data example
{% file src="/files/6J91m0NLJ0ZHLWFFwD1w" %}
### 3. Description of fields when creating a Destination - G Suite Email
| Field | Description |
| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Destination Name | Destination names are supported with multi-lang. By default, the language icon will display according to the language configured in Portal setting - Portal language setting, and this value is considered the default value. |
| Description | Description of destination, with multi-lang support |
| Destination Catalog | Channel Email has catalogs like: Amazon SES, Onesignal Email, G Suite Email… → in this example we choose the catalog as G Suite Email |
| Method | Catalogs belonging to App Push, Web Push channels, the default method will be Push. Catalogs belonging to Email, Webhook, and Conversation channels, the default method will be Send. In this example, we will choose Send. |
| Email | Click icon Add Personalization 
Personalization Attribute: List of attributes belonging to the selected Personalization type. In this example we choose “Email”
|
| From Email Name | Sender name |
| Username | Sender email |
| Password | Sender email password |
| Ignore duplicate messages for the scheduled journey | Limit allocation frequency to 1 address in 1 scheduled iteration of a journey |
| Limit frequency for the journey (3 months duration) | Limit allocation frequency to 1 address in 1 journey |
| Limit frequency for destination | Limit allocation frequency to 1 address per unit of time (hour, day, ...) |
---
# 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.antsomi.com/cdp-365-user-guide-en/use-cases/marketing-hub/how-to-send-mail-from-email-upload.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.
