ūüéČ UserExperior is now part of DevRev ¬†| ¬†Learn more


  • UserExperior supports os versions from Android Lollipop (5.0) API Level 21 to Android 14 API Level 34!
  • We do not recommend testing on Emulators/Simulators, conduct testing on real devices.

Add UserExperior dependency in build.gradle of your app

Note: If UserExperior is already integrated in your project, just re-sync the project with Gradle.

implementation 'com.userexperior:userexperior-android:7.3.2'

Start UserExperior SDK

UserExperior.startRecording(getApplicationContext(), "your-version-key-here");

Call the above method in every activity that is an entry point to your app! Entry activities are usually those which have a custom <intent-filter> element in the AndroidManifest.xml file.

Eg. MainActivity, Deep Linking Activity, etc. </intent-filter>

  • Note

Now the integration is completed, build the apk. Install apk in your android device and use the application. After performing activities minimize the app. UserExperior will upload the data, which could be seen within 2-3 minutes on the UserExperior portal.

  • Proguard Rules

If you are using Proguard in your project, you must add the following lines to your configuration:

-dontwarn com.userexperior.**
-keep class com.userexperior.** { *; }


Customizing UserExperior with Key APIs

1. Set User Identifier & additional properties

a. Set User Identifier

UserExperior SDK by default takes device id as a user identifier. However, you can specify any unique user identifier of your choice (eg. Email Id, Phone Number, etc.) as a custom user identifier. This identifier will show up in the UserExperior portal.





b. Send additional user information


 HashMap<String, Object> userProperties = new HashMap<>();
 userProperties.put("key1", value1);
 userProperties.put("key2", value2);
 userProperties.put("key3", value3);
 userProperties.put("keyN", valueN);


 HashMap<String, Object> userProperties = new HashMap<>();
 userProperties.put("USER_NAME", userName);
 userProperties.put("CITY", city);
 userProperties.put("STATE", state);
 userProperties.put("COUNTRY", country);
 userProperties.put("DOB", dob);

Note: Please send the date property in "YYYY/MM/DD" format only, if any.

2. Log Event

UserExperior SDK lets you log user events based on the scenario. An event is the indication of Progress in the user's session. LogEvent() can be used as follows

a. Log event with name




 UserExperior.logEvent("Registration Successful");

Note: Max eventName limit is 250 chars only

b. Log event with name and properties


 HashMap<String, Object> eventProp = new HashMap<>();
 eventProp.put("key1", val1);
 eventProp.put("key2", val2);
 eventProp.put("key3", val3);
 eventProp.put("keyN", valN);
 UserExperior.logEvent("Your-Event-Name", eventProp);


 HashMap<String, Object> eventProp = new HashMap<>();
 eventProp.put("Mobile_Number", mobileNum);
 eventProp.put("Service_Provider", serviceProvider);
 eventProp.put("Circle", circle);
 eventProp.put("Amount", amount);
 eventProp.put("Date", date);
 UserExperior.logEvent("MOBILE_TOPUP", eventProp);        


  • Max eventName limit is 250 chars only.
  • Send the date property in "YYYY/MM/DD" format only, if any.
  • Send primitive data types only in the property value e.g. String, integer, boolean

3. Mask/ Unmask Sensitive Views

a. Mask

UserExperior SDK by default masks all the Edit Boxes of activities. If you wish to mask any other UI element in your app, you can mask it by:

  • Using Tag- (Use Tag method only when you don't have any other tag already applied to your UI element.)

Code Example: Add the above tag in XML of your UI element


or you can add Tag Programmatically:

anyView = findViewById(R.id.anyView);

Using API

void markSensitiveView(View view)

Code Example

anyView = findViewById(R.id.anyView);

b. Unmask

UserExperior SDK by default masks all the Edit Boxes of activities. If you don't want to mask any EditBox in your app, you can exclude it from being masked by:

Using Tag - (Use Tag method only when you don't have any other tag already applied to your EditBox.)


Code Example: Add the above tag in XML of your EditText


or you can add Tag Programmatically:

editBox = findViewById(R.id.editBox);

Using API

void unmarkSensitiveView(EditText editBox)

Code Example

editBox = findViewById(R.id.editBox);

4. Mask/ Unmask Web-View Element

UserExperior SDK complies with GDPR policy and masks all the user input fields (Eg. name, password, email, etc.)  automatically in the Webview.

a. Manual Mask: 

If you wish to mask any WebView element on a Web page explicitly,  you can mask it by using class 'ue-mask'

<label class="ue-mask">OTP: 12345</label>

b. Manual Unmask:

If you wish to explicitly un-mask any manually masked WebView element, you can un-mask it by using class 'ue-unmask'

<input type="text" placeholder="Enter Username" name="username" required class="ue-unmask">

5. Track Fragments

UserExperior SDK automatically detects Activities and defines them as screens. However, If you have used fragments or anything else to represent your screens, then we recommend using the startScreen API. This API allows you to manually define screens.

void startScreen(String screenName)

Note: Max screenName limit is 250 chars only

Recommendation: Kindly pass hardcoded/fixed values for screen names, do not pass incremental values!

Code Example

try {
   UserExperior.startScreen("Notification Tab");
} catch (Exception e) {

Note: This method should be usually called from the onResume() method.

6. Track Response Time of Methods/API Calls

UserExperior SDK allows you to track the load/response time of the components in your app using APIs called startTimer and endTimer. You can call startTimer API at any event on the app from which you want to track the load/response time and call an endTimer API at the event completion. These APIs will calculate the complete response time. You can also pass timer properties while tracking response time.

Eg: Suppose, you have a ListView on your screen which gets loaded with data you receive from the server. You can call startTimer API when the screen resumes to the user and call endTimer API when data gets successfully shown in the ListView. Now you can know how much time it takes to load data after the screen is visible to the user. Similarly, you can use startTimer at any API call and an endTimer on API response.


a. Start and End Timer with Properties


HashMap<String, String> requestLevelProperties = new HashMap<>();
requestLevelProperties.put("key1", value1);
requestLevelProperties.put("key2", value2);
requestLevelProperties.put("keyN", valueN);
UserExperior.startTimer(String timerName, HashMap<String, String> requestLevelProperties);
HashMap<String, String> responseLevelProperties = new HashMap<>();
responseLevelProperties.put("key1", value1);
responseLevelProperties.put("key2", value2);
responseLevelProperties.put("keyN", valueN);
UserExperior.endTimer(String timerName, HashMap<String, String> responseLevelProperties);


  • Max timerName limit is 250 chars only
  • Max key & value limit is 250 chars only respectively
  • Timer name has to be same for both start and end timer.
  • Send primitive data types only in the property value e.g. String, integer, boolean

We have provision for some predefined property parameters for startTimer and endTimer as follows

startTimer property parameter:

Property parameter Description Example
ue_process Functionality Module e.g. Onboarding, Credit Card etc… Onboarding, Credit Card etc.. are business processes.
ue_sub_process Functionality Sub Module e.g View Card Details, OTP Sent etc… OTP Sent, View Card Details etc… are part of the business functions. Multiple sub functions make up a business process.


endTimer property parameter:

Property parameter Description Example
ue_api_status API status Success or Failure
ue_response_code Response status code for the API response 2XX, 3XX, 4XX, 5XX or any other custom code received as the response to the API
ue_response_code_desc Status code description Description of the status code e.g. Unauthorized request


Code Example for Android Native

// Call this while sending API request
HashMap<String, String> requestLevelProps = new HashMap<>();
requestLevelProps.put("ue_process", "Login Module");
requestLevelProps.put("ue_sub_process", "User Authentication");
requestLevelProps.put("request_url", reqUrl);
try {
  UserExperior.startTimer("User Login API Call", requestLevelProps);
} catch (Exception e) {
// call this when API gives response
HashMap<String, String> responseLevelProps = new HashMap<>();
responseLevelProps.put("ue_api_status", "Success");
responseLevelProps.put("ue_response_code", "200");
responseLevelProps.put("ue_response_code_desc", "valid user");
responseLevelProps.put("response", response);
try {
  UserExperior.endTimer("User Login API Call", responseLevelProps);
} catch (Exception e) {

7. Control Recording

UserExperior SDK has the following APIs which can be used to control the recording. The APIs stopRecording, pauseRecording, resumeRecording are optional and they should be only called when you explicitly want to override the default behavior. Basically, you can use pauseRecording and resumeRecording to bypass any user flow which you don't want UserExperior to capture.

void stopRecording()

By default, recording stops automatically once the app goes to the background. However, you can stop at the desired point by calling this API.

void pauseRecording()

This API pauses the recording, you can use resumeRecording API to resume.

void resumeRecording()

This API resumes the recording if it is paused.

isRecording() method returns the status of the SDK recording whether the SDK is active mode or in-active mode. The boolean value `true` indicates that the SDK is active and `false` indicates that the SDK is in-active.

boolean isRecording()

8. Get Precise User Location

UserExperior SDK lets you track the location of your user. If your app has location permissions enabled and you wish to know the exact city and country of your users, you can use our API setDeviceLocation. You just have to pass us the location parameters latitude and longitude which you get from the GPS location in your app and through this data, we will only present City and Country on our dashboard which can be used for further analytics.

void setDeviceLocation(double latitude, double longitude)

Code Example

try {
   // These are hardcoded lat, long, you can pass actual lat, long if your app uses gps
   UserExperior.setDeviceLocation(19.154023, 72.945204);
} catch (Exception e) {

9. Send Handled Exceptions

UserExperior SDK lets you send handled exceptions and their information to UserExperior Dashboard so that you can know where your app caused the handled exceptions. You must send exceptions in the catch block(s) of the handled exception. The exception object's class name (eg. java.lang.NullPointerException) will appear in the storyline of the sessions of your app on the dashboard.

void sendException(Throwable exceptionObj, String exceptionTag)

Note: Max exceptionTag limit is 250 chars only

Code Example

public void onBack(View view) {
       // this exception is explicitly thrown just for example
       throw new NullPointerException();
   } catch (NullPointerException e){
       UserExperior.sendException(e, "NullPointerException at MainActivity onBack");

10. Opt-out/Opt-in

UserExperior by default opts-in users for session recording. If you want to enable or disable recording, you can use our APIs optIn()/optOut():

void optOut()

This method stops and deletes the current session recording and also disables the session recording by our SDK for this user in the future.

void optIn()

SDK by default opts-in users for session recording on app installs. If the user was disabled for session recording by using the optOut() method, you can use this method to enable recording at runtime.

boolean getOptOutStatus()

This method returns the status of the user whether the user is currently opted-in or opted-out. The boolean value true indicates that the user is opted-out and false indicates that the user is opted-in.

User recording resets to opt-in if the user un-installs and re-installs the app.


When can we see the videos of the user's session?

When the app is minimized to the background then UserExperior SDK processes the session captured and sends the information to the UserExperior server.

How long does it take for the video session to appear on the dashboard?

From the time the app is minimized to the background the session captured will take 5 to 7 minutes to be reflected on the UserExperior dashboard.

Will the session upload if I kill the app?

If the app is killed without minimizing the app to the background, then the session which was killed will not get uploaded. UserExperior will be able to send the data whenever the app is minimized to the background.

What if the user does not have a network on the mobile device? Will the video get captured?

If the user does not have an active internet on their device at the time of the start of the session or during the end while uploading, then UserExperior stores the session locally in the apps secure memory. This stored session is sent to the UserExperior server when the users access the app again with an active internet.

Does UserExperior Track events?

Yes, By default UserExperior tracks native events. But if you want to track events done on custom controls you can track these events by calling a logEvent().

Can I add my own custom event, as we do for other SDK's?

Yes, you can add custom events using logEvent() API.

Can I uniquely identify users session on the dashboard?

Yes, use SetUserIdentifier API.

We use fragments in our app, does UserExperior also detect fragments?

Yes, user StartScreen API for fragments. This will allow UserExperior to recognize fragment as a screen.

Can UserExperior also work on Cordova/Phone gap kind of frameworks?


I am getting a crash which has the following UserExperior entry in the trace com.userexperior.*.dispatchTouchEvent ?

UserExperior intercepts and logs every touch gesture that is occurring within the app, then dispatch it back to the original implementation. The DispatchTouchEvent/ DispatchkeyEvent class is the class that is responsible for this behavior. The reason you see UserExperior in the stack-trace is that the UserExperior SDK was active (had a running thread) during the crash, but it did not cause the app to crash.

You can see the full list of Android methods that could be in the stack-trace here



UserExperior Technologies LLC
2033 Gateway Place, 5th Floor
San Jose, CA 95110
UserExperior has successfully completed a System and Organization Controls (SOC) 2 Type 2 audit, performed by Sensiba San Filippo, LLP (SSF).
Information Security Management System of UserExperior Pvt Ltd has been assessed and found to conform to the requirements of ISO/IEC 27001:2013.

Privacy & Security | Terms & Conditions | GDPR