> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zeotap.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand the Advance Fields

| **FIELD NAME**      | **ALLOWED VALUES**                                                                                                                                                                                  | **DESCRIPTION**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| :------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Group Name          | Default value is the same as the Catalogue Field name. If this field has to be grouped with existing attribute group, then choose from the list or create a new group name as per your requirement. | A group allows you to update a set of fields as a set. For example, Email Raw, Email Sha256 Lowercase or Email Sha256 uppercase are all defined under group Email.<ul><li>Example 1 – Assume that a record is received for a user, where one of these values is updated, say email raw value [xyz@gmail.com](mailto:xyz@gmail.com) is now updated to [abc@gmail.com](mailto:abc@gmail.com). Then the system updates the other connected fields under that same group as it all represents the same value but as hash. This ensures that there is no data inconsistency among the same group of fields.</li><li>Example 2 – Say we have multiple fields Address line 1, Address line 2, Address line 3 and so on under a group Address, wherein one of the fields is updated. We ensure that others are updated as a group.<br /></li></ul> <Note> **Note** <br />  Group Name is available for all Categories except Consent Purpose and Marketing Preference. </Note>                                            |
| TTL                 | Default value is **Forever**. <br /> Allowed values can be 1 to 3650                                                                                                                                | Time to Live (TTL) defines the number of days the consent or ID will be active from the day it was last updated. Post that we drop the value from the Zeotap system. <br /><br /> Example – If the cookie was set for 90 days, then after 90 days (from last updated timestamp) the cookie value is dropped from the Zeotap system.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| No. of ID           | Default value is **1** per user. <br /> Allowed values can be 1 to 10.                                                                                                                              | The number specified here determines the number of value to be stored against this **Id** attribute for a user.<br />  <Note> **Note** <br /> No. of ID is only available for ID category. </Note>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| Restrict onChannels | All the Channels and Destinations available for the account.                                                                                                                                        | Use **Restrict on Channels** to control where a catalogue field **can not** be activated. This helps ensure sensitive or regulated data is only used on approved marketing channels and destinations. <br /> <br /> **What this setting does:** <br /> <br /><ul><li>Allows you to limit the activation of a catalogue field to specific channels (for example, Paid Media, CRM, Owned Media).</li><li>You can optionally restrict specific destinations within a selected channel.</li><li>If no destinations are selected, the restriction applies to all destinations under that channel.</li><li>Selected channels or destinations will <strong>not be available</strong> during audience activation when this field is used.</li><li>Existing running audiences are <strong>not impacted</strong>.</li><li>If an audience is edited later, you may be prompted to <strong>remove restricted destinations, remove restricted catalogue from audience definition or mappings</strong> before saving.</li></ul> |