Skip to end of metadata
Go to start of metadata

 Evergage 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 Evergage JavaScript beacon served to the end user’s browser, then encrypted by SSL and transferred to the Evergage servers. Some sensitive data such as credit card numbers and some personably identifiable information is not stored. You will work with Evergage to determine which sensitive data should be collected. Non-personally identifiable and non-sensitive data stored in the Evergage cloud service is used to provide personalized experiences.

This Article Explains

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

Sections in this Article

Everage User Roles

While most Evergage user roles cannot view sensitive information, there are several that can. For more information on user roles and how to Add, Edit, and Delete Users, please refer to the article in this knowledge base. Roles listed below are ordered from least permissions to most permissions.

Roles that can view Sensitive information

  • Editor with Export
  • Administrator

Roles that cannot view Sensitive information

  • Viewer
  • Campaign Author
  • Campaign Editor
  • Editor


Attributes

For more information on attributes and how to Create, Change, or Delete User or Account Level Attributes 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 Evergage Support. Please contact Evergage 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 Evergage 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 Evergage Support to complete this request
  • User IDs marked Sensitive that are contained in URLs or API requests from the Evergage user interface are encrypted
  • Evergage 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 Evergage users with access to these tokens already have export permissions, which qualifies them to view sensitive data