Identify your users, eliminate impersonation, send custom data and more
name
and email
from userscollectUserData
to true
will prompt the user to input a name
and email
before proceeding to chat.
Since any user can input any email, the user is considered non-verified
and only has access to previous chats that were created on their device.
non-verified
because malicious users can intercept outgoing requests and impersonate someone else.
Any customData
sent in this method will be saved as non_verified_custom_data
so that it can be used with caution.
Similar to other non-verified
methods, the user only has access to previous chats that were created on their device.
verified
method, the user has access to all previous chats regardless of which device they were created on, as long as they were created through this verified
method.
For more details on what also can be passed when authenticating a user, see the API reference.
externalId
.
This works regardless of the authentication method you use (verified
or non-verified
).