Interaction Studio user or account-level attributes can be used collect data for use in segmentation, reporting, or in integrated third party systems. For example, if you created a form in Interaction Studio, you can assign each field to an already created attribute. Depending on the configuration of your dataset, this attribute will either collect the data for availability in reporting, or can write it back to the third-party integrated system.
This page details how to modify user, account, or survey level attributes. For information on creating Identity Attributes, please refer to Configure Identity Types and Attributes in this knowledge base.
Create a User, Account, or Survey Attribute
Enter Attribute Information
Enter or select the following information:
Name - name of the attribute which cannot be changed
- Note: the same attribute name cannot be used on both a user and an account attribute
Label - add a descriptive label to an attribute which will appear in places like the Unified Customer Profile
Type - select either String, Integer, Decimal, Date, Boolean, Object, or Multistring
Identity Attributes Types must be String
Classification Override - select either
Sensitive - the attribute will be displayed only to those with Editor with Export or higher permissions and cannot be used in a campaign. Those with lesser permissions will see ******* in place of a value on the Unified Customer Profile and segment list screens. Additionally, email address fields (specifically named "emailAddress") will not be searchable
Personally Identifiable - the attribute can be viewed by anyone, but cannot be used in a campaign
Non-Sensitive - the attribute can be viewed by anyone and used in campaigns
Click
to save or to cancel
Attribute Update Logic
You can use multiple sources to update attributes. Interaction Studio retains values from an authenticated source, such as server-side campaigns, over lower priority sources, such as the web. Attribute updates have the following order of priority that determines which value to retain, based on the trust level of the source:
- The attribute’s source is from the server channel in the Event API.
- The attribute’s source is from an ETL data feed.
- The timestamp of the update determines the priority for all other sources, such as web, mobile, and non-server-side event API updates.
Change or Delete an Attribute