User identification

This section covers how to bind each report to the identity of the user reporting the problem for your iOS app. You have the flexibility to add some extra attributes about the device as well as the us

Luciq helps you better identify the bug reports or feedback you get by associating a user's identity to them.

User Email and Name

If you already have a user's name and email, you can pre-fill the email field in the bug, feedback, and question reporting flow. The user will then be identified in all reports (bugs, improvements, questions), crashes, surveys, and feature requests.

An example of a pre-filled email field in the bug reporting form.

Ideally, this API should be called as soon as a user logs into your app.

Swift

Luciq.identifyUser(withID: "2374927027", email: "[email protected]", name: "John Appleseed")

Objective-C

Null Values

If both the email and ID parameters are empty or null, the user will not be identified, and the SDK will through an error.

User Data

You can also add additional data about your users. This API is best used for dumping large amounts of data. Each call to this method overrides the user data to be attached. The maximum length of the string is 1,000 characters.

Swift

let profileDetails = user.allProfileDetails()
let profileDetailsString = "\(profileDetails)"
Luciq.userData = profileDetailsString

Objective-C

Logout

When a user logs out, the following API should be called. Calling logOut will reset the value of the email and name previously set. It will also remove any currently set user attributes, user events, user chats, and user data.

Swift

Luciq.logOut()

Objective-C

Logout only when user is identified

Please note that if the user is currently not identified using the identifyUser API, the logOut method will have no effect.

Isolating sessions per user

If multiple users sign in and out on the same device within a single app session, Luciq can automatically start a new session on logout so that each user's activity is attributed to the correct identity. This behavior is disabled by default — reach out to the customer support team to enable it. It is available starting from iOS SDK v19.8.1.