Categories for adding Catalogue fields

The following table provides information about the different categories available in Catalogue:

CATEGORY	DESCRIPTION	BEHAVIOUR
Consent	This field stores the user’s consent information as per the privacy policy. To know the various options related to this category, refer to Add a Consent Category.	This category creates an attribute of type `Consent`. It stores only one value per attribute. Hence, a new value always overrides the existing value after ID resolution.
Campaign	This field stores campaign information at a user level. To know the various options related to this category, refer to Add a Campaign Category.	This category creates an attribute of type `Event`. It stores time series information. Hence, information is only appended against a user profile after ID resolution.
Product	This field stores product transaction information at a user level. To know the various options related to this category, refer to Add a Product Category.	This category creates an attribute of the type `Profile`. Currently, it stores only one value per attribute. Hence, a new value always overrides the existing value after ID resolution.
Marketing Preference	This field stores the user’s marketing preference. To know the various options related to this category, refer to Add a Marketing Preference.	This category creates an attribute of the type `Marketing Preference`. It stores only one value per attribute. Hence, a new value always overrides the existing value after ID resolution.
Event	This field stores user action information. To know the various options related to this category, refer to Add an Event Category.	This category creates an attribute of the type `Event`. It stores time series information. Hence, information is only appended against a user profile after ID resolution.
ID Metadata	This field stores any metadata information about an ID like ID status or ID hierarchy and so on. For this to work, ensure to link it to the corresponding ID’s group name. To know the various options related to this category, refer to Add an ID Metadata Category.	This category creates an attribute of the type `ID Metadata`. It stores only one value per ID. Hence, a new value always overrides the existing value after ID resolution.
ID Consent	This field stores any consent information about an ID like Email ID Consent. For this to work, ensure to link it to the corresponding ID’s group name. To know the various options related to this category, refer to Add an ID Consent Category.	This category creates an attribute of the type `ID Consent`. It stores only one value per ID. Hence, a new value always overrides the existing value after ID resolution.
ID	This field stores the user’s attribute like user id, account id and so on. To know the various options related to this category, refer to Add an ID Category.	This category creates an attribute of the type ID. It stores only one value per ID. Hence, a new value always overrides the existing value after ID resolution. However, there is an exception in the case of the No. of IDs feature where more than one value is maintained.
User Trait	This field stores profile information of your user. For example, age, gender and so on. To know the various options related to this category, refer to Add a User Trait Category.	This category creates an attribute of the type `Profile`. Currently, it stores only one value per attribute. Hence, a new value always overrides the existing value after ID resolution.
Non-Customer Entity	This field is not directly linked to a specific individual but to an attribute associated with the user. The most common forms of Non-Customer Entity Data are product catalogues, order data, feed data, campaign data, account data and so on. To know the various options related to this category, refer to Add a Non-Customer Entity Category.	This category of data creates attributes of the type `Non-Customer Entity`. Each attribute can only store one value at a time, and if a new value is added, it will replace the existing value after ID resolution.