Skip to main content
User Attributes are pieces of information you know about a user. They could be demographics like age or gender, account-specific like plan, or whether a user has seen a particular A/B test variation. User attributes are a customer identity you can reference throughout the customer’s lifetime.

​
Identifying Users

For SDK versions below 13.6.00 refer to this document. Setting identifiers is important to:
  • To tie user behavior across platforms, i.e., iOS, Android, Web, etc.
  • This is to ensure unnecessary or stale users are not created.
  • To identify users across installs/re-installs.

​
Single Identifier

Call the API below to pass the identifier on to the MoEngage SDK. 
MoEAnalyticsHelper.identifyUser(context, "identifier")
Note: This method is a replacement for the deprecated setUniqueId(). If you are using setUniqueId() in your application, consider replacing it with identifyUser()

​
Multiple Identifiers

If your application has multiple identifiers using which you identify a user you can pass all the identifiers to the SDK using the below API 
MoEAnalyticsHelper.identifyUser(
    context,
    mapOf("identifierName1" to "identifierValue1", "identifierName2" to "identifierValue2")
)
Updates to SDK functions for User Identification and Session Management
  • Forced Logout: The MoEngage SDK no longer automatically logs out the previous user when a new user is detected on the device. Logout should now be explicitly called for workspaces enabled with Identity resolution to avoid data corruption.
  • SetUniqueID: identifyUser function supports multiple identifiers, which replaces the need of using SetUniqueID function for user identification. Note that SetUniqueID is marked for removal in the future releases of SDK versions - it is important to use identifyUser instead especially if you are using Identity resolution in your workspace.
  • SetAlias: For workspaces with the Identity resolution feature enabled, MoEngage SDK stores the previous identifier values. When identifyUser function is used to track the new identifier values, MoEngage SDK detects the change in identifier value and reports accordingly.
If you call the identifyUser function without logging out, then the existing logged-in user’s ID is updated.
If you call identifyUser() multiple times with different identifier names, the SDK will append this identifier to the already set identifiers. Refer to our help document to learn more about the feature.

​
Logout

The application needs to notify the MoEngage SDK whenever the user is logged out of the application. Call the API whenever the user is logged out of the application to notify the SDK. 
MoECoreHelper.logoutUser(context)
If the application is registering for a push token, it should pass the new push token to MoEngage SDK after the user logs out. For more information about passing push tokens, refer to Push Configuration for Android SDK.

​
Tracking User Attributes

The SDK provides APIs to track commonly tracked user attributes like First Name, Last Name, Email-Id, etc. Please use the provided methods for tracking these attributes. For more information on supported data types and data tracking policies, please refer to Data Tracking Policies. 
MoEAnalyticsHelper.setFirstName()
MoEAnalyticsHelper.setLastName()
MoEAnalyticsHelper.setUserName()
MoEAnalyticsHelper.setLocation()
MoEAnalyticsHelper.setGender()
MoEAnalyticsHelper.setMobileNumber()
MoEAnalyticsHelper.setBirthDate()
MoEAnalyticsHelper.setEmailId()
For setting other User Attributes, use the generic method setUserAttribute(key, value). Supported types for attribute value are String, int, double, num, bool, List<int>, List<String>, List<double> & List<num>. 
// Tracking a String Attribute
MoEAnalyticsHelper.setUserAttribute(context,"locality", "SF")
// Tracking a Date Attribute
MoEAnalyticsHelper.setUserAttribute(context,"signedUpOn", Date())
// Tracking a location attribute
MoEAnalyticsHelper.setUserAttribute(context,"lastLocation", GeoLocation(40.77, 73.98))
// Tracking Array Attributes
MoEAnalyticsHelper.setUserAttribute(context,"int_array",arrayOf<Int>(1,2,3))
MoEAnalyticsHelper.setUserAttribute(context,"string_array",arrayOf<String>("English","French"))
MoEAnalyticsHelper.setUserAttribute(context,"double_array",arrayOf<Double>(40.0,20.0))
MoEAnalyticsHelper.setUserAttribute(context,"json_array", JSONArray(listOf(1, 2, 3)))      
MoEAnalyticsHelper.setUserAttribute(context,"json_object", JSONObject().put("key", "value"))
For more information about the detailed list of user attributes, refer to the API reference.

​
Reserved keywords for User Attributes

Below is the list of keys that should not be used when tracking user attributes.
  • USER_ATTRIBUTE_UNIQUE_ID
  • USER_ATTRIBUTE_USER_EMAIL
  • USER_ATTRIBUTE_USER_MOBILE
  • USER_ATTRIBUTE_USER_NAME
  • USER_ATTRIBUTE_USER_GENDER
  • USER_ATTRIBUTE_USER_FIRST_NAME
  • USER_ATTRIBUTE_USER_LAST_NAME
  • USER_ATTRIBUTE_USER_BDAY
  • USER_ATTRIBUTE_NOTIFICATION_PREF
  • USER_ATTRIBUTE_OLD_ID
  • MOE_TIME_FORMAT
  • MOE_TIME_TIMEZONE
  • USER_ATTRIBUTE_DND_START_TIME
  • USER_ATTRIBUTE_DND_END_TIME
  • MOE_GAID
  • INSTALL
  • UPDATE
  • MOE_ISLAT
  • status
  • user_id
You cannot use “moe_” as a prefix while naming events, event attributes, or user attributes. It is a system prefix and using it might result in periodic blacklisting without prior communication.