Display content using SSO based User Attributes

Overview

Previously, role-based segmentation relied heavily on window variables to identify user roles, increasing the difficulty in identifying the right window variable for each use case. Extracting variables from a website isn't always accurate; frequent changes to the underlying application can break the process, and integration setups can be tricky and time-consuming.

Your title goes here

The SSO-based User attributes capturing is a Beta feature. To enable this feature, contact support@whatfix.com.

To improve the accuracy and reliability of role-based segmentation, Whatfix enables you to fetch Single Sign-On (SSO) attributes and map them to User attributes. Once fetched and added as a User attribute, you can use them in Cohorts, Visibility Rules and Product Analytics filters.

Use the User Attributes to display content or track analytics for a specific set of users. For example, SSO-based User attributes enable you to display a reward program Pop-up just for the HR team of your organization or create a Cohort of users within the sales department to track sales-specific feature engagement.

Prerequisites before you enable end user SSO attribute capturing:

• You must configure and enable End-user authentication before you capture SSO attributes. For more information, see End-user authentication.

• Capturing of SSO attributes must be allowed by your Identitätsanbieter.

• Advanced Visibility Rules feature must be enabled on your account. To enable this feature, contact support@whatfix.com.

Step 1: Configure SSO Attributes

Use the following steps to enable end-user authentication and map SSO-based attributes with user attributes:

2. Click End-user authentication.
   

3. Click Configure end-user authentication.
   
   
   

4. Enable the End-user authentication toggle.
   
   

   Your title goes here

   Once you enable End-user authentication, ensure you perform a Push to production, and then resume from Step 5.

   
   

5. Click + Add attribute.
   
   

6. In the Add attributes dialog box, enter a User attribute name. For example, Employee_Type.
   
   

   Your title goes here

   To get the full list of all supported SSO-based user attributes, contact your IT team.

   
   

7. Select the SSO attribute you want to map to the User attribute. For example, UserType.
   
   

   Your title goes here

   Click the Add and Remove icons to add map more attributes:
   

8. Click Add attribute.
   
   

   Your title goes here

   Once you’ve added the User attributes and the corresponding SSO attributes, click the Edit or Delete icons to manage the attributes.
   

Step 2: Use the SSO-based User Attributes for Role Segmentation

SSO-based User attributes work similarly to role tags. Use these attributes to display content for a specific set of audience.
Once you have enabled End-user authentication and configured SSO-based user attributes, you can add User attributes as a Visibility Rule.

The following example shows a Pop-up to full-time employees on an application. Use the same steps to map the User attribute as Visibility rules in other widgets as well.

Use the following steps to add the mapped User attribute as a Visibility rule:

1. Go to the Set Visibility Rules section of any widget that you want to edit.

2. In the Visibility rules section for your widget, click Who does the pop-up appear?

   

3. In the Who does it appear to? dropdown, select user attributes.
   
   

4. Select the User attribute that you’ve mapped to the SSO attribute.
   
   

5. Add the Check if Attribute condition and then enter the Value.

   

6. Once you have added all the required Visibility Rules, click Save.

7. Finish creating the widget, and then click Save.

   

   Your title goes here

   Preview the content using Preview mode and push the widget to Production.

SSO-based user attributes in Product Analytics

The user attributes you have mapped on the Whatfix Guidance Dashboard can be used to drill down on the data and create Cohorts to group users having the same characteristics.