Configure DAP on OS to Identify User ID

User identification is key for delivering personalized content and accurate segmentation. By default, DAP on OS identifies users using a combination, for example; device ID and system username. This is then matched with the primary user ID fetched from integration systems like Google Sheets or Azure Active Directory.

User Identification

• DAP on OS identifies users using a combination of device ID and system username, for example Device223-johndoe.

• DAP on OS fetches user information from external systems like Google Sheets or Azure Active Directory, which may contain user attributes like role, department and more.

• The primary ID from these systems is used to identify and matched with the user ID.

Match IDs

• For smooth content delivery, the user ID created by DAP on OS must match the primary ID fetched from Google Sheets and Azure Active Directory.

• This match ensures that users receive the right content based on their roles or attributes.

Note:

The keys used to identify user and enterprise attributes are case-sensitive. Ensure that the values used in Google Sheets or Azure Active Directory exactly match the keys and values configured in the Whatfix dashboard.

ID Mismatches

ID mismatches occur if the user and integration IDs do not match. This can prevent proper segmentation.

Note:

To help resolve ID mismatches, contact support@whatfix.com. The support team can modify the capture logic and run specific commands in the monitor to capture the correct user ID accurately.

Advanced Customization for User Identification

Advanced customization enables you to add custom rules for user identification directly using the Whatfix user interface. By defining specific criteria and conditions, segment user experiences based on roles, preferences, or other critical parameters, creating a more user-centric environment.

Note:

For further assistance with advanced customization, contact support@whatfix.com.