How to Build Unique EUID via User Identifiers Across Devices
Based on the EUID generation strategy, businesses can call the relevant interfaces at the following key moments when using MA to construct a unique EUID for their users.
| Scenario | Operation Description |
|---|---|
| First Visit to App/Website | After initializing the SDK, the system automatically generates an EUID based on the device's registration_id. |
| Successful Registration/Login on App/Website | - Client calls the user identification interface to set the user_id.- Server-side is recommended to call the REST API with both user_id and registration_id to obtain the EUID. |
| Logout | No additional client action is required. |
| Account Switching | Consistent with the "registration/login" process: call the user identification interface again to set the new user_id. |
| Web Page Refresh | When detecting that the user is in a logged-in state, call the user identification interface to set the user_id. |
| Backend Data Reporting | Before reporting an event, the EUID must first be obtained: - The backend may call the REST API with only the user_id to obtain the EUID.- To avoid repeated information transfer, it is recommended that the client report the registration_id to the backend, and the backend passes both user_id and registration_id when obtaining the EUID. |
Through the above integration approach, EngageLab CDP can effectively associate the behaviors of the same user across different devices and login states, building an accurate and unified user profile. If you need specific interface call examples for each scenario, we can provide further developer documentation support.
Still Have Questions?
Can't find what you're looking for? Our experts are here to provide personalized assistance. Ask your question now and get a timely response.
