Identify unique users in Whatfix Mobile

User Identification

If user information (User ID) is not configured, Whatfix Mobile uses the local device storage (cache) to store analytics data like the number of times the element is shown, the number of times the Flow is completed by a user, etc.

The following are a few issues with using the local device storage approach:

Users using a shared device

If a user views Whatfix Mobile content on a particular device and another user uses the same device, then the in-app experience is not shown to the second user.

Users using the app across multiple devices

If a user views Whatfix Mobile content on a particular device and then logs into another device, the in-app experience is shown again.

User uninstalls the app or clears the cache

If the app is reinstalled or the cache is cleared, a user who has already seen Whatfix Mobile content is considered a new user, and the content is shown again.

User switches from Android to iOS (or vice versa)

If a user switches from Android to iOS (or vice versa), then the in-app experience is shown again on the new OS.

User Identifier method

We recommend using user information like email ID, merchant ID, phone number, etc. to identify users. Usernames and extra information are considered Personally Identifiable Information (PII) and are therefore encrypted throughout, in transit, and at rest. So anything that is passed as user information or user segmentation is secure.

Once you configure the user information, Whatfix Mobile usage and analytics data are sent from the SDK. This data is mapped against the respective User ID and stored in the Whatfix cloud. Whenever the end user logs in to the app or updates their User ID, the SDK fetches the data associated with the particular user from the cloud. This helps sync the data between the local device storage (cache) and the cloud, hence solving the user identification issues. 

User Identification ensures that the end user's usage history is always synced, and they see the guidance content as many times as intended by the content creator, even if they share a device, use multiple devices, uninstall the app, or clear the cache.

Leap.setUniqueUserId("UNIQUE_ID_OF_THE_USER");

Leap.shared.setUniqueUserid("UNIQUE_ID_OF_THE_USER")

[[Leap shared] setUniqueUserId:@"UNIQUE_ID_OF_THE_USER"];

LeapReactNative.setUniqueUserId("UNIQUE_ID_OF_THE_USER");

LeapPlugin.setUniqueUserId({uniqueUserId: "UNIQUE_ID_OF_THE_USER"})

cordova.plugins.LeapAndroid.setUniqueUserId("abc123@gmail.com");

cordova.plugins.LeapiOS.setUniqueUserId("UNIQUE_ID_OF_THE_USER");

Leap.SetUniqueUserId("UNIQUE_ID_OF_THE_USER");

Leap.Shared.SetUniqueUserId("UNIQUE_ID_OF_THE_USER");

Leap.logout();

Leap.shared.logout()

[[Leap shared] logout];

LeapReactNative.logout();

LeapPlugin.logout();

cordova.plugins.LeapAndroid.logout();

cordova.plugins.LeapiOS.logout();

Leap.Logout();

Leaps.Shared.Logout();