At a glance: Collect the Android OAID to attribute installs from third-party Android app stores.
The Open Anonymous Device Identifier (OAID) is a user-resettable unique identifier for Android devices. It was introduced by the Mobile Security Alliance (MSA), China Information and Communication Research Institute, and device manufacturers, as a privacy-preserving alternative to non-resettable device identifiers like IMEI.
The OAID is usually used for ad measurement and install attribution on devices where Google Play Services aren't available (meaning where Google Advertising ID does not exist).
The OAID is readable on all devices using an SDK provided by the MSA, or on Hauwei devices using the Huawei Mobile Service (HMS) Core SDK.
The integration of OAID consists of 3 steps:
- Integrating an SDK to generate and provide the OAID (either the MSA SDK or Huawei HMS SDK).
- Integrating the AppsFlyer OAID plugin module.
- Integrating the AppsFlyer SDK.
- For apps that are intended to be used in China, the MSA SDK must be used.
- For apps that are intended to be used globally on Huawei devices, the Huawei HMS library should be used.
To integrate and use the MSA SDK:
Huawei HMS SDK
To integrate and use the Hauwei HMS SDK:
- Tell your developers to follow their integration instructions.
Opting out of OAID collection
Once the OAID integration is complete, the SDK attempts to collect OAID automatically. If you want to prevent the collection of OAID for certain users, tell the developer to use either the setCollectOAID(false) API or the setDisableAdvertisingIdentifiers(true) API.
Setting OAID manually
If your app already collects OAID, you can skip the AppsFlyer OAID plugin integration and simply set the OAID value into the AppsFlyer SDK manually, using the setOaidData API.