OAID versus IDFA: what a China Android campaign can send
Operator checklist contrasting MSA/Huawei OAID on China Android (per AppsFlyer) with IDFA on iOS. China OEM-store Android campaigns should plan OAID; IDFA is not a China Android substitute.
Checklist (China Android paid UA)
Use AppsFlyer’s OAID article as the primary measurement reference for this card.
- Confirm store path. If the campaign targets Huawei / Xiaomi / OPPO / vivo / other non-Play stores, assume GAID may be absent.
- Select OAID SDK. China-intended apps: integrate the MSA SDK (AppsFlyer requirement). Huawei-only global builds may use HMS instead.
- Wire MMP plugin. AppsFlyer OAID plugin + AppsFlyer SDK (or equivalent MMP OAID module).
- Do not send IDFA on Android. IDFA is an iOS identifier under Apple’s ATT regime; it is not a drop-in China Android advertising ID.
- Document opt-out. Record whether
setCollectOAID(false)/ equivalent is used for any cohort. - Separate iOS flight. If the same product also runs China mainland iOS, treat IDFA/ATT and NPPA ISBN as a different stack (see iOS ISBN gate card).
| Identifier | Platform in this checklist | Primary evidence |
|---|---|---|
| OAID | China Android OEM stores | AppsFlyer OAID article |
| GAID | Play Services devices | Absent on many China OEM paths (per AppsFlyer framing) |
| IDFA | iOS | Not supplied by the AppsFlyer OAID Android article |
