1 Android SDK
The default device ID of an Android device is a unique device ID at the application level, which is automatically generated by Quicktracking:
For Android 9 and the following devices: The SDK automatically collects the imei, wifimac, androidid, and serial number to generate device IDs. After the device IDs are generated, the device IDs are stored locally. The device IDs are generated again only after you uninstall the application or delete the application data.
Devices above the Android level 10 level: The SDK automatically generates device IDs based on the values of the oaid, gaid, androidd, and serial number (SN) fields. The generated device IDs are stored locally. The device IDs are generated only after you uninstall or delete an application.
If the C- terminal user of the application agrees to collect IDFAs and OAIDs, the Quick Tracking SDK will collect OAID and OAID. Only QuickTracking app SDK can collect OAID, GAID, Imei, WiFIMAC, AndroIDID, SN, IDFV.
You can use the following methods to obtain the device ID:
QtConfigure.getUMIDString()2 iOS SDK
iOS device's the default device ID is a unique device ID at the application level, by automatic Quicktracking Generation:
For iOS devices, the SDK automatically collects openudid and generates a device ID. After the device ID is generated, the device ID is added to the keychain. The device ID is generated only after you restore factory settings or delete application data.
If the C- terminal user of the application agrees to collect IDFAs and OAIDs, the Quick Tracking SDK will collect OAID and OAID. Only QuickTracking app SDK can collect OAID, GAID, Imei, WiFIMAC, AndroIDID, SN, IDFV.
You can use the following methods to obtain the device ID:
+ (NSString *)umidString;3 mini program SDK
The following code provides an example on how to obtain and upload the device ID of the mini program by using the developer:
The device ID is the unique ID that is generated by the mini program. For example, the OpenID of WeChat.
Assign to "_anony_id":
// If the user ID is collected asynchronously, you must prevent the SDK from being reported and set the BLOCK tracking point.
aplus.aplus_queue.push({
action: 'aplus.setMetaInfo',
arguments: ['_hold', 'BLOCK']
});
// Set_anony_id
aplus.aplus_queue.push({
action: "aplus.setMetaInfo",
arguments: ["_anony_id", "The openid you obtained"]
});
// Because the collection of user IDs is asynchronous, you need to set BLOCK first, and then set START.
// After_hold=START is set, logs that are previously blocked will be sent one by one with user information.
aplus.aplus_queue.push({
action: 'aplus.setMetaInfo',
arguments: ['_hold', 'START']
});If you need to obtain the device ID of QuickTracking on the mini program, you can obtain the_anony_id in the metainfo.
4 Web/H5 SDK
By default, the web device ID is automatically generated by Quicktracking.
You can use one of the following methods to obtain the device ID that is automatically generated by the SDK:
A field named cna is stored in the cookie of the current domain name. You can parse the document.cookie file to obtain the value of the cna field.
You can use the_dev_id method to obtain the ID of the uploaded device as follows:
Developers can use setMetaInfo to set_dev_id to customize the device ID, which can be read aplus.getMetaInfo('_dev_id')