1. Introduction to User Association Across Universes

Refer to the User Identification-Urban User Association section of the SDK product features for details.

2. API Introduction

This section only introduces the API functions of User Association Across Universes. Refer to   for other tracking interface. Refer to uni-app Sensors Analytics JS Plugin for other tracking interfaces.

Minimum Supported Version of ID-Mapping 3.0

uni-app Sensors Analytics JS Plugin v0.0.8

uni-app Sensors Analytics Native Plugin v0.1.1

The related APIs for User Association Across Universes (bind, unbind, loginWithKey) are not supported on all platforms. For details, refer to uni-app Sensors Analytics JS Plugin.

2.1. User Login

Call when the user logs in. The first parameter is obtained from the detailed preset id key list, and the second parameter is the corresponding user ID.

After calling the interface, the corresponding key and value will be cached locally, and the subsequent collected events will all contain the cached ID information.

 sensors.loginWithKey(String loginIDKey, String loginId);

2.2. Multiple User ID Association

Called when associating multiple user IDs. The first parameter is obtained from the detailed preset id key list, and the second parameter is the associated user ID.

After calling the interface, the corresponding key and value will be cached locally, and the subsequent collected events will all contain the cached ID information.

sensors.bind("$identity_mobile","187****8991")

2.3. Multiple User ID Disassociation

Called when disassociating multiple user IDs. The first parameter is the key to be disassociated, and the second parameter is the corresponding disassociated user ID.

After calling the interface, the relevant unbinding event will be sent, and the corresponding key-value in the local cached ID information will be cleared (if it exists).

sensors.unbind("$identity_mobile","187****8991")