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 collects behavioral information on visitors to your digital properties and provides personalized experiences to those users based on that behavior. Data is collected by the Interaction Studio JavaScript beacon served to the end user’s browser, then encrypted by SSL and transferred to the Interaction Studio servers. Some sensitive data such as credit card numbers and some personably identifiable information is not stored. You will work with Interaction Studio to determine which sensitive data should be collected. Non-personally identifiable and non-sensitive data stored in the Interaction Studio cloud service is used to provide personalized experiences.

This Article Explains

This article details how you can manage sensitive information in Interaction Studio including Interaction Studio user roles that can view and are restricted from viewing sensitive visitor, customer, and prospect data.

Sections in this Article

Interaction Studio User Roles

Roles are custom and granular in Interaction Studio. You can create roles with the combination of permissions, granted by dataset, that meet the needs of your company and security team. For customers with a legacy account that existed prior to August 1, 2020, there are two built in roles that can view sensitive information:

  • Editor with Export
  • Administrator

For customers with accounts created after August 1, 2020, you will need to create specific roles to assign to users. Each role will include permissions to different aspects of the Interaction Studio system. While administrators will always be able to view sensitive information, only roles with the Audiences > User/Account Profile > View Sensitive permissions will have access to sensitive information for non-administrative users.

For more information about creating user roles and accounts, please see Add, Edit, and Delete Users and Roles in this knowledge base.


Attributes

For more information on attributes and how to Modify Attributes at the User or Account Level please refer to the article in this knowledge base.

  • User attributes can be marked as Sensitive so users with roles that cannot view Sensitive information will see ******* in place of a value on the Unified Customer Profile and segment list screens
  • The UserID attribute can only be marked Sensitive by Interaction Studio Support. Please contact Interaction Studio Support for assistance
  • Users with roles that can view Sensitive information cannot edit values of attributes marked as Sensitive on the Attributes section of a Unified Customer Profile

Only attributes marked as Sensitive are hidden. Attributes marked as Personally Identifiable are not hidden.

  • If the user ID attribute for your dataset is set as emailAddress and marked as Sensitive
    • All email addresses in your dataset are considered sensitive
    • Those with roles that cannot view sensitive information cannot search for users by email address. Consider giving email campaign testers Editor with Export or higher permissions so that they can preview which email content will display to specific recipients (dynamic content, recs, promotions). Lesser permissions may hinder the tester's ability to simulate email content.
  • If the user ID attribute for your dataset is set as displayName and marked as Sensitive
    • All user names in your dataset will be considered sensitive
    • Those with roles that cannot view sensitive information cannot search for users by email address. Consider giving email campaign testers Editor with Export or higher permissions so that they can preview which email content will display to specific recipients (dynamic content, recs, promotions). Lesser permissions may hinder the tester's ability to simulate email content.

UserID

  • If you want to restrict restrict Interaction Studio users with roles that cannot view sensitive information from viewing userIDs because the attribute your dataset is set as emailAddress or another sensitive attribute, you must contact Interaction Studio Support to complete this request
  • User IDs marked Sensitive that are contained in URLs or API requests from the Interaction Studio user interface are encrypted
  • Interaction Studio users with roles that cannot view sensitive information will see ***** or encrypted user IDs in fields or locations where user IDs are displayed and will not be able to search for users by user ID
  • API tokens are not affected by sensitive attribute restrictions because Interaction Studio users with access to these tokens already have export permissions, which qualifies them to view sensitive data