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.

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

Luciq.identifyUser("e-mail", "username", "id");

//Example:
Luciq.identifyUser("[email protected]", "John Appleseed", "2374927027");

❗️

IMPORTANT: The userID Must Be Unique

The userID you provide is the primary identifier for a user within the Luciq. You must ensure that this ID is unique for each of your users.

Providing a generic, non-unique ID (e.g., "guest" or "unknown_user") for multiple users will cause their data to be incorrectly merged. This will lead to critical data integrity and privacy issues, such as different users being able to see and reply to each other's private chat conversations.

If a user is anonymous, do not call the identifyUser API. The SDK will automatically handle a unique anonymous identity for you.

🚧

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.

Luciq.setUserData("User data sample");

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.

Luciq.logOut();

🚧

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.