Interaction Studio Knowledge Base
Space shortcuts

Page tree
Skip to end of metadata
Go to start of metadata

New Name: Marketing Cloud Personalization

Interaction Studio (formerly Evergage) is now known as Marketing Cloud Personalization. The new name reflects our mission and vision for innovation in Salesforce Marketing Cloud. We wish we could snap our fingers to update the name everywhere, but you can expect to see the previous name in various places until we replace it.

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 Article Explains

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.

Sections in this Article

Create a User, Account, or Survey Attribute

  1. Log into Interaction Studio as an administrator
  2. Select Settings > Attributes
  3. You will see the full list of tracked attributes in your dataset

  4. On the User, Account or Survey tab, click New Attribute

    Per Dataset Limit

    The maximum number of user attributes per dataset is capped at 100.

Enter Attribute Information

  1. Enter or select the following information:

    1. Name - name of the attribute which cannot be changed

      1. Note: the same attribute name cannot be used on both a user and an account attribute

    2. Label - add a descriptive label to an attribute which will appear in places like the Unified Customer Profile

    3. Type - select either String, Integer, Decimal, Date, Boolean, Object, or Multistring

      Identity Attributes Types must be String 

    4. Classification Override - select either 

      1. 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

      2. Personally Identifiable - the attribute can be viewed by anyone, but cannot be used in a campaign

      3. Non-Sensitive - the attribute can be viewed by anyone and used in campaigns

  2. Click  to save or  to cancel

Attribute Update Logic

You can use multiple sources to update attributes. Attributes retain values from authenticated sources such as ETL or Channel: Server (/authevent API) over lower priority sources, such as the web.

Attribute updates have the following order of priority to determines which value to retain:

  • Authenticated source: ETL and channel Server in the authenticated Event API (/authevent endpoint) are prioritized over unauthenticated sources such as web, mobile, and non server-side events.  
    • An attribute value sent in via an unauthenticated channel will not overwrite the value set by a trusted channel.  For example, an attribute value from ETL will not be overwritten by an update from the web - even if the web attribute update has a more recent timestamp.
    • Trusted channels can overwrite each other. The timestamp is used to determine which attribute is kept when deciding between two values that are both from authenticated channels. For example, an attribute value set via Channel: Server can get overwritten by an attribute value provided via ETL (if the timestamp is more recent on the ETL attribute update). 
  • Unauthenticated Sources: Unauthenticated sources are prioritized behind authenticated sources and will not update an attribute that has been set by an authenticated source.  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

  1. Clicknext to the attribute you'd like to change

    1. Label - change the descriptive label 

    2. Type - change the type of attribute: String, Integer, Decimal, Date, Boolean, Object, or Multistring

    3. Classification Override - select either Sensitive, Personally Identifiable, Non-Sensitive

  2. Click  to save changes or  to cancel changes

  3. Clickto delete an attribute