Unified ID Linkage Scenario
Last updated
Last updated
This document explains a hypothetical scenario as an example to help you understand the configuration of user information and terminal connection due to user identification information settings.
To initialize the SDK, users must follow the steps outlined in the integration guide for each platform.
This section shows the process of transitioning from state to
Before recording a login event, EXTERNAL_ID
set the user identification information to a value that distinguishes the user. Through this process, the user is converted from an anonymous user profile to an identified user profile, and a unified ID is generated so that the user can be identified through the unified ID on any platform.
If there is information required for the settings corresponding to the identified user A, it is reflected through the user profile settings.
User profiles can reflect arbitrary key values set by the user in the console.
Logs login events.
This section shows the process of an identified user A logging out.
Logs logout events.
If you do not want actions to be targeted to identified user A after he or she logs out, resetIdentity()
initialize the user identification information by calling the API.
Please be careful when making calls, as initializing user identification information will interrupt any ongoing event flow and disconnect the terminal from the user.
If you still call, please call the event you want to reflect before calling the API to reflect the collected events.
EXTERNAL_ID
Login using existingThis section EXTERNAL_ID
shows how a user who has previously set up unified identity information can log in again using the same values.
If the entered EXTERNAL_ID
value is the same as the existing one, the terminal will be reconnected with the previously created identified user A.
The flow of events continues as before, with the event flow of identified user A continuing.
EXTERNAL_ID
Log in using anotherThis section EXTERNAL_ID
shows how a user who has set up unified identity information can log in using different values.
If the entered EXTERNAL_ID
value is different from the existing one, the SDK determines that the user is a different user and deletes all previously saved integrated ID information and sets a new one, and the terminal is connected to the identified user B.
The user profile is reflected to the identified user B.
The flow of events changes to the flow of events for the newly identified user B.
If you do not set up user identification information, the user will be treated as an anonymous user. For example, this could be a user who visited your website but did not register, or a user who downloaded your mobile app but did not create a profile.
When a user is initially recognized through the SDK, a unique identifier generated by the SDK is issued and an anonymous user profile is created.
If you set a value for one of the identification information types below, EXTERNAL_ID
you will be treated as an identified user in DFINERY, and you will be able to identify the same user profile on multiple devices. You can also set additional information such as user email and phone number for more specific user identification.