AppsFlyer documents MSA/Huawei OAID integration for China Android attribution

AppsFlyer’s help centre article Android OAID implementation in the SDK, opened 20 September 2026, states the purpose in one line: collect Android OAID to attribute installs from third-party Android app stores.

Documented facts

• Definition. OAID is a user-resettable unique identifier introduced by the Mobile Security Alliance (MSA), the China Information and Communication Research Institute, and device manufacturers as a privacy-preserving alternative to non-resettable identifiers such as IMEI.
• Where it matters. “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).”
• How to read it. Via the MSA SDK on devices generally, or via Huawei Mobile Services (HMS) Core SDK on Huawei devices.
• China-intended apps. “For apps that are intended to be used in China, the MSA SDK must be used.” Global Huawei-device apps may use the Huawei HMS library.
• Integration steps. (1) integrate MSA or Huawei HMS to generate OAID; (2) integrate the AppsFlyer OAID plugin module; (3) integrate the AppsFlyer SDK. Registration on the MSA site yields a certificate that must be packaged in the app.
• Opt-out / manual set. After integration the SDK attempts automatic OAID collection; setCollectOAID(false) or setDisableAdvertisingIdentifiers can suppress it. setOaidData can inject a value already collected by the app.

Teaching limits

Without OAID, China OEM-store attribution fails wherever GAID/Play Services are absent. This lab card stops at the documented integration contract; it does not invent fill rates.

Download the integration card.

Research checked 20 September 2026. Local draft; human editorial review pending.